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. Hardware
  4. Hilfe beim Zigbee Controller mit Sonoff Zigbee 3.0

NEWS

  • UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?
    apollon77A
    apollon77
    48
    3
    8.8k

  • Monatsrückblick – September 2025
    BluefoxB
    Bluefox
    13
    1
    2.2k

  • Neues Video "KI im Smart Home" - ioBroker plus n8n
    BluefoxB
    Bluefox
    16
    1
    3.2k

Hilfe beim Zigbee Controller mit Sonoff Zigbee 3.0

Geplant Angeheftet Gesperrt Verschoben Hardware
31 Beiträge 4 Kommentatoren 2.8k 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.
  • Jan LangeJ Jan Lange

    @homoran
    hier vorab die summary. darunter findest du die langfassung.

    @Thomas-Braun deine Anweisungen bin ich soweit auch schon durchgegangen

    ======================= SUMMARY =======================
                            v.2024-05-22
    
    
       Static hostname: raspberry4
             Icon name: computer
      Operating System: Debian GNU/Linux 11 (bullseye)
                Kernel: Linux 6.1.21-v8+
          Architecture: arm64
    
    Installation:           native
    Kernel:                 aarch64
    Userland:               64 bit
    Timezone:               Europe/Berlin (CEST, +0200)
    User-ID:                1000
    Display-Server:         true
    Boot Target:            graphical.target
    
    Pending OS-Updates:     0
    Pending iob updates:    0
    
    Nodejs-Installation:
    /usr/bin/nodejs         v20.14.0
    /usr/bin/node           v20.14.0
    /usr/bin/npm            10.7.0
    /usr/bin/npx            10.7.0
    /usr/bin/corepack       0.28.1
    
    Recommended versions are nodejs 18.20.3 and npm 10.7.0
    Your nodejs installation is correct
    
    MEMORY:
                   total        used        free      shared  buff/cache   available
    Mem:            3.8G        527M        2.5G         35M        757M        3.2G
    Swap:            99M          0B         99M
    Total:          3.9G        527M        2.6G
    
    Active iob-Instances:   2
    Active repo(s): stable
    
    ioBroker Core:          js-controller           5.0.19
                            admin                   6.13.16
    
    ioBroker Status:        iobroker is running on this host.
    
    
    Objects type: jsonl
    States  type: jsonl
    
    Status admin and web instance:
    + system.adapter.admin.0                  : admin                 : raspberry4                               -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
      system.adapter.web.0                    : web                   : raspberry4                               - disabled, port: 8082, bind: 0.0.0.0, run as: admin
    
    Objects:                7755
    States:                 5786
    
    Size of iob-Database:
    
    14M     /opt/iobroker/iobroker-data/objects.jsonl
    1.3M    /opt/iobroker/iobroker-data/states.jsonl
    
    
    
    =================== END OF SUMMARY ====================
    
    === Mark text until here for copying ===
    
    

    Langversion

    Skript v.2024-05-22
    
    *** BASE SYSTEM ***
       Static hostname: raspberry4
             Icon name: computer
      Operating System: Debian GNU/Linux 11 (bullseye)
                Kernel: Linux 6.1.21-v8+
          Architecture: arm64
    
    Model           : Raspberry Pi 4 Model B Rev 1.1
    Docker          : false
    Virtualization  : none
    Kernel          : aarch64
    Userland        : 64 bit
    
    Systemuptime and Load:
     12:40:43 up 11 min,  3 users,  load average: 1.40, 1.23, 0.70
    CPU threads: 4
    
    
    *** RASPBERRY THROTTLING ***
    Current issues:
    No throttling issues detected.
    
    Previously detected issues:
    No throttling issues detected.
    
    *** Time and Time Zones ***
                   Local time: Fri 2024-05-31 12:40:43 CEST
               Universal time: Fri 2024-05-31 10:40:43 UTC
                     RTC time: n/a
                    Time zone: Europe/Berlin (CEST, +0200)
    System clock synchronized: yes
                  NTP service: active
              RTC in local TZ: no
    
    *** Users and Groups ***
    User that called 'iob diag':
    iobroker
    HOME=/home/iobroker
    GROUPS=iobroker adm tty dialout cdrom sudo audio video plugdev games users input render netdev bluetooth lpadmin gpio i2c spi
    
    User that is running 'js-controller':
    iobroker
    HOME=/home/iobroker
    GROUPS=iobroker adm tty dialout cdrom sudo audio video plugdev games users input render netdev bluetooth lpadmin gpio i2c spi
    
    *** Display-Server-Setup ***
    Display-Server: true
    Desktop:
    Terminal:       tty
    Boot Target:    graphical.target
    
    *** MEMORY ***
                   total        used        free      shared  buff/cache   available
    Mem:            3.8G        475M        2.6G         35M        758M        3.2G
    Swap:            99M          0B         99M
    Total:          3.9G        475M        2.7G
    
    Active iob-Instances:   2
    
             3794 M total memory
              475 M used memory
              664 M active memory
              384 M inactive memory
             2560 M free memory
               85 M buffer memory
              673 M swap cache
               99 M total swap
                0 M used swap
               99 M free swap
    
    *** top - Table Of Processes  ***
    top - 12:40:43 up 11 min,  3 users,  load average: 1.40, 1.23, 0.70
    Tasks: 187 total,   1 running, 186 sleeping,   0 stopped,   0 zombie
    %Cpu(s):  0.0 us,  1.5 sy,  0.0 ni, 98.5 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
    MiB Mem :   3794.3 total,   2560.4 free,    475.9 used,    758.1 buff/cache
    MiB Swap:    100.0 total,    100.0 free,      0.0 used.   3207.8 avail Mem
    
    *** FAILED SERVICES ***
    
      UNIT LOAD ACTIVE SUB DESCRIPTION
    0 loaded units listed.
    
    *** FILESYSTEM ***
    Filesystem     Type      Size  Used Avail Use% Mounted on
    /dev/root      ext4      118G  9.6G  103G   9% /
    devtmpfs       devtmpfs  1.7G     0  1.7G   0% /dev
    tmpfs          tmpfs     1.9G     0  1.9G   0% /dev/shm
    tmpfs          tmpfs     759M  1.2M  758M   1% /run
    tmpfs          tmpfs     5.0M  4.0K  5.0M   1% /run/lock
    /dev/mmcblk0p1 vfat      255M   31M  225M  13% /boot
    tmpfs          tmpfs     380M   20K  380M   1% /run/user/1000
    
    Messages concerning ext4 filesystem in dmesg:
    [Fri May 31 12:28:52 2024] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0  smsc95xx.macaddr=DC:A6:32:29:7C:EB vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000  console=ttyS0,115200 console=tty1 root=PARTUUID=d8d28d06-02 rootfstype=ext4 fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles
    [Fri May 31 12:28:53 2024] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Quota mode: none.
    [Fri May 31 12:28:53 2024] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
    [Fri May 31 12:28:55 2024] EXT4-fs (mmcblk0p2): re-mounted. Quota mode: none.
    
    Show mounted filesystems:
    TARGET                       SOURCE         FSTYPE          OPTIONS
    /                            /dev/mmcblk0p2 ext4            rw,noatime
    |-/dev                       devtmpfs       devtmpfs        rw,relatime,size=1678472k,nr_inodes=419618,mode=755
    | |-/dev/shm                 tmpfs          tmpfs           rw,nosuid,nodev
    | |-/dev/pts                 devpts         devpts          rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000
    | `-/dev/mqueue              mqueue         mqueue          rw,nosuid,nodev,noexec,relatime
    |-/proc                      proc           proc            rw,relatime
    | `-/proc/sys/fs/binfmt_misc systemd-1      autofs          rw,relatime,fd=29,pgrp=1,timeout=0,minproto=5,maxproto=5,direct
    |-/sys                       sysfs          sysfs           rw,nosuid,nodev,noexec,relatime
    | |-/sys/kernel/security     securityfs     securityfs      rw,nosuid,nodev,noexec,relatime
    | |-/sys/fs/cgroup           cgroup2        cgroup2         rw,nosuid,nodev,noexec,relatime,nsdelegate,memory_recursiveprot
    | |-/sys/fs/pstore           pstore         pstore          rw,nosuid,nodev,noexec,relatime
    | |-/sys/fs/bpf              bpf            bpf             rw,nosuid,nodev,noexec,relatime,mode=700
    | |-/sys/kernel/debug        debugfs        debugfs         rw,nosuid,nodev,noexec,relatime
    | |-/sys/kernel/tracing      tracefs        tracefs         rw,nosuid,nodev,noexec,relatime
    | |-/sys/fs/fuse/connections fusectl        fusectl         rw,nosuid,nodev,noexec,relatime
    | `-/sys/kernel/config       configfs       configfs        rw,nosuid,nodev,noexec,relatime
    |-/run                       tmpfs          tmpfs           rw,nosuid,nodev,size=777080k,nr_inodes=819200,mode=755
    | |-/run/lock                tmpfs          tmpfs           rw,nosuid,nodev,noexec,relatime,size=5120k
    | |-/run/rpc_pipefs          sunrpc         rpc_pipefs      rw,relatime
    | `-/run/user/1000           tmpfs          tmpfs           rw,nosuid,nodev,relatime,size=388536k,nr_inodes=97134,mode=700,uid=1000,gid=1000
    |   `-/run/user/1000/gvfs    gvfsd-fuse     fuse.gvfsd-fuse rw,nosuid,nodev,relatime,user_id=1000,group_id=1000
    `-/boot                      /dev/mmcblk0p1 vfat            rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro
    
    Files in neuralgic directories:
    
    /var:
    1.7G    /var/
    984M    /var/cache
    972M    /var/cache/apt
    872M    /var/cache/apt/archives
    436M    /var/log
    
    Archived and active journals take up 432.1M in the file system.
    
    /opt/iobroker/backups:
    869M    /opt/iobroker/backups/
    
    /opt/iobroker/iobroker-data:
    431M    /opt/iobroker/iobroker-data/
    267M    /opt/iobroker/iobroker-data/files
    138M    /opt/iobroker/iobroker-data/files/javascript.admin
    118M    /opt/iobroker/iobroker-data/files/javascript.admin/static
    117M    /opt/iobroker/iobroker-data/files/javascript.admin/static/js
    
    The five largest files in iobroker-data are:
    38M     /opt/iobroker/iobroker-data/files/iot.admin/static/js/main.3d563dc9.js.map
    24M     /opt/iobroker/iobroker-data/files/web.admin/static/js/main.135279a0.js.map
    14M     /opt/iobroker/iobroker-data/objects.jsonl
    8.8M    /opt/iobroker/iobroker-data/files/iot.admin/static/js/main.3d563dc9.js
    8.5M    /opt/iobroker/iobroker-data/files/web.admin/static/js/main.135279a0.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-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20240124092219-if00
    
    
    
    
    *** NodeJS-Installation ***
    
    /usr/bin/nodejs         v20.14.0
    /usr/bin/node           v20.14.0
    /usr/bin/npm            10.7.0
    /usr/bin/npx            10.7.0
    /usr/bin/corepack       0.28.1
    
    
    nodejs:
      Installed: 20.14.0-1nodesource1
      Candidate: 20.14.0-1nodesource1
      Version table:
     *** 20.14.0-1nodesource1 600
            500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
            100 /var/lib/dpkg/status
         20.13.1-1nodesource1 600
            500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
         20.13.0-1nodesource1 600
            500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
         20.12.2-1nodesource1 600
            500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
         20.12.1-1nodesource1 600
            500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
         20.12.0-1nodesource1 600
            500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
         20.11.1-1nodesource1 600
            500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
         20.11.0-1nodesource1 600
            500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
         20.10.0-1nodesource1 600
            500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
         20.9.0-1nodesource1 600
            500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
         20.8.1-1nodesource1 600
            500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
         20.8.0-1nodesource1 600
            500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
         20.7.0-1nodesource1 600
            500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
         20.6.1-1nodesource1 600
            500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
         20.6.0-1nodesource1 600
            500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
         20.5.1-1nodesource1 600
            500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
         20.5.0-1nodesource1 600
            500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
         20.4.0-1nodesource1 600
            500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
         20.3.1-1nodesource1 600
            500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
         20.3.0-1nodesource1 600
            500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
         20.2.0-1nodesource1 600
            500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
         20.1.0-1nodesource1 600
            500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
         20.0.0-1nodesource1 600
            500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
         12.22.12~dfsg-1~deb11u4 500
            500 http://deb.debian.org/debian bullseye/main arm64 Packages
            500 http://security.debian.org/debian-security bullseye-security/main arm64 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.13.16
    javascript:     8.3.1
    
    nodejs modules from github:     1
    | `-- node-botvac@0.4.2-schedule-write (git+ssh://git@github.com/PeterVoronov/node-botvac.git#04674af96bca09ac0db3f2f590209080474521fe)
    
    Adapter State
    + system.adapter.admin.0                  : admin                 : raspberry4                               -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
      system.adapter.alexa2.0                 : alexa2                : raspberry4                               - disabled
      system.adapter.backitup.0               : backitup              : raspberry4                               - disabled
      system.adapter.botvac.0                 : botvac                : raspberry4                               - disabled
      system.adapter.discovery.0              : discovery             : raspberry4                               - disabled
      system.adapter.hue.0                    : hue                   : raspberry4                               - disabled, port: 443
      system.adapter.ical.0                   : ical                  : raspberry4                               - disabled
      system.adapter.iot.0                    : iot                   : raspberry4                               - disabled
      system.adapter.javascript.0             : javascript            : raspberry4                               - disabled
      system.adapter.lgtv.0                   : lgtv                  : raspberry4                               - disabled
      system.adapter.node-red.0               : node-red              : raspberry4                               - disabled, port: 1880, bind: 0.0.0.0
      system.adapter.philips-air.0            : philips-air           : raspberry4                               - disabled
      system.adapter.telegram.0               : telegram              : raspberry4                               - disabled, port: 8443, bind: 0.0.0.0
      system.adapter.tradfri.0                : tradfri               : raspberry4                               - disabled
      system.adapter.web.0                    : web                   : raspberry4                               - disabled, port: 8082, bind: 0.0.0.0, run as: admin
      system.adapter.yamaha.0                 : yamaha                : raspberry4                               - disabled
      system.adapter.zigbee.0                 : zigbee                : raspberry4                               -  enabled
    
    + instance is alive
    
    Enabled adapters with bindings
    + system.adapter.admin.0                  : admin                 : raspberry4                               -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
    
    ioBroker-Repositories
    stable        : http://download.iobroker.net/sources-dist.json
    beta          : http://download.iobroker.net/sources-dist-latest.json
    
    Active repo(s): stable
    
    Installed ioBroker-Instances
    Used repository: stable
    Cannot read or parse /opt/iobroker/node_modules/@iobroker/js-controller-common/build/lib/common/../node_modules/iobroker.zigbee/io-package.json: /opt/iobroker/node_modules/iobroker.zigbee/package.json: Unexpected end of JSON input
    Cannot read or parse /opt/iobroker/node_modules/@iobroker/js-controller-common/build/lib/common/../node_modules/iobroker.zigbee/io-package.json: /opt/iobroker/node_modules/iobroker.zigbee/package.json: Unexpected end of JSON input
    Adapter    "admin"        : 6.13.16  , installed 6.13.16
    Adapter    "alexa2"       : 3.26.5   , installed 3.26.5
    Adapter    "backitup"     : 2.11.0   , installed 2.11.0
    Adapter    "botvac"       : 2.2.0    , installed 2.2.0
    Adapter    "deconz"       : 1.4.1    , installed 1.4.1
    Adapter    "discovery"    : 4.4.0    , installed 4.4.0
    Adapter    "hue"          : 3.11.0   , installed 3.11.0
    Adapter    "ical"         : 1.15.0   , installed 1.15.0
    Adapter    "iot"          : 3.2.2    , installed 3.2.2
    Adapter    "javascript"   : 8.3.1    , installed 8.3.1
    Controller "js-controller": 5.0.19   , installed 5.0.19
    Adapter    "lgtv"         : 2.2.0    , installed 2.2.0
    Adapter    "mqtt"         : 5.2.0    , installed 5.2.0
    Adapter    "node-red"     : 5.2.1    , installed 5.2.1
    Adapter    "parser"       : 2.1.0    , installed 2.1.0
    Adapter    "philips-air"  : 1.1.0    , installed 1.1.0
    Adapter    "rpi2"         : 1.3.2    , installed 1.3.2
    Adapter    "simple-api"   : 2.8.0    , installed 2.8.0
    Adapter    "socketio"     : 6.7.0    , installed 6.7.0
    Adapter    "telegram"     : 3.2.1    , installed 3.2.1
    Adapter    "tradfri"      : 3.1.3    , installed 3.1.3
    Adapter    "web"          : 6.2.5    , installed 6.2.5
    Adapter    "whatsapp-cmb" : 0.2.3    , installed 0.2.3
    Adapter    "ws"           : 2.6.1    , installed 2.6.1
    Adapter    "yamaha"       : 0.5.3    , installed 0.5.3
    Adapter    "zigbee2mqtt"  : 2.13.6   , installed 2.13.6
    
    Objects and States
    Please stand by - This may take a while
    Objects:        7755
    States:         5786
    
    *** OS-Repositories and Updates ***
    Hit:1 http://security.debian.org/debian-security bullseye-security InRelease
    Hit:2 http://deb.debian.org/debian bullseye InRelease
    Hit:3 http://deb.debian.org/debian bullseye-updates InRelease
    Hit:4 http://archive.raspberrypi.org/debian bullseye InRelease
    Hit:5 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.1:631           0.0.0.0:*               LISTEN      0          13605      534/cupsd
    tcp        0      0 127.0.0.1:9001          0.0.0.0:*               LISTEN      1000       17412      538/iobroker.js-con
    tcp        0      0 127.0.0.1:9000          0.0.0.0:*               LISTEN      1000       14080      538/iobroker.js-con
    tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      0          13589      577/sshd: /usr/sbin
    tcp6       0      0 :::8081                 :::*                    LISTEN      1000       17784      1214/io.admin.0
    tcp6       0      0 ::1:631                 :::*                    LISTEN      0          13604      534/cupsd
    tcp6       0      0 :::22                   :::*                    LISTEN      0          13591      577/sshd: /usr/sbin
    udp        0      0 0.0.0.0:68              0.0.0.0:*                           0          13631      478/dhcpcd
    udp        0      0 0.0.0.0:631             0.0.0.0:*                           0          15346      601/cups-browsed
    udp        0      0 0.0.0.0:5353            0.0.0.0:*                           108        13529      400/avahi-daemon: r
    udp        0      0 0.0.0.0:46655           0.0.0.0:*                           108        13531      400/avahi-daemon: r
    udp6       0      0 :::546                  :::*                                0          15496      478/dhcpcd
    udp6       0      0 :::5353                 :::*                                108        13530      400/avahi-daemon: r
    udp6       0      0 :::46740                :::*                                108        13532      400/avahi-daemon: r
    
    *** Log File - Last 25 Lines ***
    
    2024-05-31 12:40:49.892  - error: host.raspberry4 Caught by controller[0]:     at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:161:24)
    2024-05-31 12:40:49.892  - error: host.raspberry4 Caught by controller[0]:     at node:internal/main/run_main_module:28:49 {
    2024-05-31 12:40:49.893  - error: host.raspberry4 Caught by controller[0]:   path: '/opt/iobroker/node_modules/iobroker.zigbee/package.json'
    2024-05-31 12:40:49.893  - error: host.raspberry4 Caught by controller[0]: }
    2024-05-31 12:40:49.893  - error: host.raspberry4 Caught by controller[0]: Node.js v20.14.0
    2024-05-31 12:40:49.893  - error: host.raspberry4 instance system.adapter.zigbee.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
    2024-05-31 12:40:49.894  - info: host.raspberry4 Restart adapter system.adapter.zigbee.0 because enabled
    2024-05-31 12:41:19.943  - error: host.raspberry4 startInstance zigbee.0: Cannot read and parse "/opt/iobroker/node_modules/iobroker.zigbee/package.json"
    2024-05-31 12:41:19.960  - info: host.raspberry4 instance system.adapter.zigbee.0 started with pid 5067
    2024-05-31 12:41:20.120  - error: host.raspberry4 Caught by controller[0]: node:internal/modules/package_json_reader:93
    2024-05-31 12:41:20.121  - error: host.raspberry4 Caught by controller[0]:         throw error;
    2024-05-31 12:41:20.121  - error: host.raspberry4 Caught by controller[0]:         ^
    2024-05-31 12:41:20.121  - error: host.raspberry4 Caught by controller[0]: SyntaxError: Error parsing /opt/iobroker/node_modules/iobroker.zigbee/package.json: Unexpected end of JSON input
    2024-05-31 12:41:20.121  - error: host.raspberry4 Caught by controller[0]:     at parse (<anonymous>)
    2024-05-31 12:41:20.121  - error: host.raspberry4 Caught by controller[0]:     at read (node:internal/modules/package_json_reader:80:16)
    2024-05-31 12:41:20.122  - error: host.raspberry4 Caught by controller[0]:     at readPackage (node:internal/modules/package_json_reader:141:10)
    2024-05-31 12:41:20.122  - error: host.raspberry4 Caught by controller[0]:     at readPackageScope (node:internal/modules/package_json_reader:164:19)
    2024-05-31 12:41:20.122  - error: host.raspberry4 Caught by controller[0]:     at shouldUseESMLoader (node:internal/modules/run_main:81:15)
    2024-05-31 12:41:20.122  - error: host.raspberry4 Caught by controller[0]:     at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:161:24)
    2024-05-31 12:41:20.122  - error: host.raspberry4 Caught by controller[0]:     at node:internal/main/run_main_module:28:49 {
    2024-05-31 12:41:20.122  - error: host.raspberry4 Caught by controller[0]:   path: '/opt/iobroker/node_modules/iobroker.zigbee/package.json'
    2024-05-31 12:41:20.122  - error: host.raspberry4 Caught by controller[0]: }
    2024-05-31 12:41:20.123  - error: host.raspberry4 Caught by controller[0]: Node.js v20.14.0
    2024-05-31 12:41:20.123  - error: host.raspberry4 instance system.adapter.zigbee.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
    2024-05-31 12:41:20.123  - info: host.raspberry4 Restart adapter system.adapter.zigbee.0 because enabled
    
    
    Thomas BraunT Online
    Thomas BraunT Online
    Thomas Braun
    Most Active
    schrieb am zuletzt editiert von Thomas Braun
    #10

    @jan-lange sagte in Hilfe beim Zigbee Controller mit Sonoff Zigbee 3.0:

    Sind wieder mal so grundlegende Dinge falsch.

    Leg dir einen user an und spring mit dem durch das System. Der user iobroker ist eigentlich als Systemuser vorgesehen.

    Display-Server: true

    Im Serverbetrieb falsch. Schalt das aus.
    Bzw. installier das System von vorneherein ohne Desktop. Dann läuft auch sowas wie cupsd da nicht mit.

    sudo systemctl set-default multi-user.target
    

    Mit dem zigbee-Adapter stimmt auch was nicht.

    Cannot read or parse /opt/iobroker/node_modules/@iobroker/js-controller-common/build/lib/common/../node_modules/iobroker.zigbee/io-package.json: /opt/iobroker/node_modules/iobroker.zigbee/package.json: Unexpected end of JSON input
    Cannot read or parse /opt/iobroker/node_modules/@iobroker/js-controller-common/build/lib/common/../node_modules/iobroker.zigbee/io-package.json: /opt/iobroker/node_modules/iobroker.zigbee/package.json: Unexpected end of JSON input

    Installier den nochmal neu.

    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

    Jan LangeJ 1 Antwort Letzte Antwort
    0
    • Thomas BraunT Thomas Braun

      @jan-lange sagte in Hilfe beim Zigbee Controller mit Sonoff Zigbee 3.0:

      Sind wieder mal so grundlegende Dinge falsch.

      Leg dir einen user an und spring mit dem durch das System. Der user iobroker ist eigentlich als Systemuser vorgesehen.

      Display-Server: true

      Im Serverbetrieb falsch. Schalt das aus.
      Bzw. installier das System von vorneherein ohne Desktop. Dann läuft auch sowas wie cupsd da nicht mit.

      sudo systemctl set-default multi-user.target
      

      Mit dem zigbee-Adapter stimmt auch was nicht.

      Cannot read or parse /opt/iobroker/node_modules/@iobroker/js-controller-common/build/lib/common/../node_modules/iobroker.zigbee/io-package.json: /opt/iobroker/node_modules/iobroker.zigbee/package.json: Unexpected end of JSON input
      Cannot read or parse /opt/iobroker/node_modules/@iobroker/js-controller-common/build/lib/common/../node_modules/iobroker.zigbee/io-package.json: /opt/iobroker/node_modules/iobroker.zigbee/package.json: Unexpected end of JSON input

      Installier den nochmal neu.

      Jan LangeJ Offline
      Jan LangeJ Offline
      Jan Lange
      schrieb am zuletzt editiert von
      #11

      @thomas-braun said in Hilfe beim Zigbee Controller mit Sonoff Zigbee 3.0:

      Display-Server: true

      Danke dir.

      Wie schalte ich den Display-Server aus?

      Dachte eigentlich auch hätte ne Version ohne Desktop...

      Den Zigbee habe ich schon mehrfach versucht neu zu installieren. Nichts hilft.

      Thomas BraunT 1 Antwort Letzte Antwort
      0
      • Jan LangeJ Jan Lange

        @thomas-braun said in Hilfe beim Zigbee Controller mit Sonoff Zigbee 3.0:

        Display-Server: true

        Danke dir.

        Wie schalte ich den Display-Server aus?

        Dachte eigentlich auch hätte ne Version ohne Desktop...

        Den Zigbee habe ich schon mehrfach versucht neu zu installieren. Nichts hilft.

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

        @jan-lange sagte in Hilfe beim Zigbee Controller mit Sonoff Zigbee 3.0:

        Wie schalte ich den Display-Server aus?

        Hatte ich doch dazu geschrieben...

        sudo systemctl set-default multi-user.target
        sudo reboot
        

        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

        Jan LangeJ 1 Antwort Letzte Antwort
        0
        • Thomas BraunT Thomas Braun

          @jan-lange sagte in Hilfe beim Zigbee Controller mit Sonoff Zigbee 3.0:

          Wie schalte ich den Display-Server aus?

          Hatte ich doch dazu geschrieben...

          sudo systemctl set-default multi-user.target
          sudo reboot
          
          Jan LangeJ Offline
          Jan LangeJ Offline
          Jan Lange
          schrieb am zuletzt editiert von Jan Lange
          #13

          @thomas-braun

          Ah sorry hatte ich auch gemacht, dacht nur dass sich der Befehlt noch auf etwas anderes bezieht. Danke dir.

          Leider bleibt das Problem bestehen, dass der Adapter nun garnicht mehr funktioniert.

          Liegt es vielleicht an dem node.js Update. Vorher ging zumindest der Adapter noch auch wenn er sich nicht mit dem Zigbee verbinden konnte.

          Thomas BraunT 1 Antwort Letzte Antwort
          0
          • Jan LangeJ Jan Lange

            @thomas-braun

            Ah sorry hatte ich auch gemacht, dacht nur dass sich der Befehlt noch auf etwas anderes bezieht. Danke dir.

            Leider bleibt das Problem bestehen, dass der Adapter nun garnicht mehr funktioniert.

            Liegt es vielleicht an dem node.js Update. Vorher ging zumindest der Adapter noch auch wenn er sich nicht mit dem Zigbee verbinden konnte.

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

            @jan-lange sagte in Hilfe beim Zigbee Controller mit Sonoff Zigbee 3.0:

            Liegt es vielleicht an dem node.js Update.

            Nein. Es liegt (vermutlich) an der zerbröselten package.json

            iob update
            iob upgrade zigbee@1.10.3
            

            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

            Jan LangeJ 1 Antwort Letzte Antwort
            0
            • Thomas BraunT Thomas Braun

              @jan-lange sagte in Hilfe beim Zigbee Controller mit Sonoff Zigbee 3.0:

              Liegt es vielleicht an dem node.js Update.

              Nein. Es liegt (vermutlich) an der zerbröselten package.json

              iob update
              iob upgrade zigbee@1.10.3
              
              Jan LangeJ Offline
              Jan LangeJ Offline
              Jan Lange
              schrieb am zuletzt editiert von
              #15

              @thomas-braun said in Hilfe beim Zigbee Controller mit Sonoff Zigbee 3.0:

              iob upgrade zigbee@1.10.3

              Okay krass. Adaprer läuft, bleibt nur noch das Problem dass er sich sich nicht verbinden kann.

              HomoranH Thomas BraunT 2 Antworten Letzte Antwort
              0
              • Jan LangeJ Jan Lange

                @thomas-braun said in Hilfe beim Zigbee Controller mit Sonoff Zigbee 3.0:

                iob upgrade zigbee@1.10.3

                Okay krass. Adaprer läuft, bleibt nur noch das Problem dass er sich sich nicht verbinden kann.

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

                @jan-lange sagte in Hilfe beim Zigbee Controller mit Sonoff Zigbee 3.0:

                dass er sich sich nicht verbinden kann.

                /dev/serial/by-id hast du ja korrekt (?) drin!
                was sagt jetzt das debug-log beim Start der Instanz?

                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
                • Jan LangeJ Jan Lange

                  @thomas-braun said in Hilfe beim Zigbee Controller mit Sonoff Zigbee 3.0:

                  iob upgrade zigbee@1.10.3

                  Okay krass. Adaprer läuft, bleibt nur noch das Problem dass er sich sich nicht verbinden kann.

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

                  @jan-lange

                  Und mit welchen Meldungen tut der Adapter das nun?

                  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

                  Jan LangeJ 1 Antwort Letzte Antwort
                  0
                  • Thomas BraunT Thomas Braun

                    @jan-lange

                    Und mit welchen Meldungen tut der Adapter das nun?

                    Jan LangeJ Offline
                    Jan LangeJ Offline
                    Jan Lange
                    schrieb am zuletzt editiert von Jan Lange
                    #18

                    @thomas-braun

                    als COM Id habe ich hinterlegt "/dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20240124092219-if00"

                    
                    total 0
                    drwxr-xr-x 2 root root 60 May 31 13:08 .
                    drwxr-xr-x 4 root root 80 May 31 13:08 ..
                    lrwxrwxrwx 1 root root 13 May 31 13:08 usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20240124092219-if00 -> ../../ttyACM0
                    
                    

                    Hier der Log aus der Console

                    2024-05-31 14:36:03.302  - info: host.raspberry4 instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                    2024-05-31 14:36:03.340  - info: admin.0 (2912) <== Disconnect system.user.admin from ::ffff:192.168.0.23
                    2024-05-31 14:36:02.563  - info: host.raspberry4 stopInstance system.adapter.zigbee.0 (force=false, process=true)
                    2024-05-31 14:36:02.571  - info: zigbee.0 (3717) Got terminate signal TERMINATE_YOURSELF
                    2024-05-31 14:36:02.602  - info: host.raspberry4 stopInstance system.adapter.zigbee.0 send kill signal
                    2024-05-31 14:36:02.575  - info: zigbee.0 (3717) cleaned everything up...
                    2024-05-31 14:36:02.582  - info: zigbee.0 (3717) Zigbee: disabling joining new devices.
                    2024-05-31 14:36:02.634  - warn: zigbee.0 (3717) Failed to stop zigbee during startup
                    2024-05-31 14:36:02.635  - info: zigbee.0 (3717) terminating
                    2024-05-31 14:36:02.636  - info: zigbee.0 (3717) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                    2024-05-31 14:36:03.076  - info: zigbee.0 (3717) terminating
                    2024-05-31 14:36:03.302  - info: host.raspberry4 instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                    2024-05-31 14:36:03.340  - info: admin.0 (2912) <== Disconnect system.user.admin from ::ffff:192.168.0.23
                    2024-05-31 14:36:05.672  - info: host.raspberry4 instance system.adapter.zigbee.0 started with pid 3768
                    2024-05-31 14:36:10.832  - info: zigbee.0 (3768) starting. Version 1.10.3 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.14.0, js-controller: 5.0.19
                    2024-05-31 14:36:10.939  - info: zigbee.0 (3768) delete old Backup files. keep only last 10
                    2024-05-31 14:36:10.942  - info: zigbee.0 (3768) Starting Zigbee  npm ...
                    2024-05-31 14:36:11.303  - info: zigbee.0 (3768) Installed Version: iobroker.zigbee@1.10.3
                    2024-05-31 14:36:10.832  - info: zigbee.0 (3768) starting. Version 1.10.3 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.14.0, js-controller: 5.0.19
                    2024-05-31 14:36:10.939  - info: zigbee.0 (3768) delete old Backup files. keep only last 10
                    2024-05-31 14:36:10.942  - info: zigbee.0 (3768) Starting Zigbee  npm ...
                    2024-05-31 14:36:11.303  - info: zigbee.0 (3768) Installed Version: iobroker.zigbee@1.10.3
                    2024-05-31 14:36:15.301  - error: zigbee.0 (3768) Starting zigbee-herdsman problem : "startup failed - configuration-adapter mismatch - see logs above for more information"
                    2024-05-31 14:36:15.302  - error: zigbee.0 (3768) Failed to start Zigbee
                    2024-05-31 14:36:15.303  - error: zigbee.0 (3768) Error herdsman start
                    2024-05-31 14:36:15.301  - error: zigbee.0 (3768) Starting zigbee-herdsman problem : "startup failed - configuration-adapter mismatch - see logs above for more information"
                    2024-05-31 14:36:15.302  - error: zigbee.0 (3768) Failed to start Zigbee
                    2024-05-31 14:36:15.303  - error: zigbee.0 (3768) Error herdsman start
                    
                    
                    Thomas BraunT HomoranH crunchipC 4 Antworten Letzte Antwort
                    0
                    • Jan LangeJ Jan Lange

                      @thomas-braun

                      als COM Id habe ich hinterlegt "/dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20240124092219-if00"

                      
                      total 0
                      drwxr-xr-x 2 root root 60 May 31 13:08 .
                      drwxr-xr-x 4 root root 80 May 31 13:08 ..
                      lrwxrwxrwx 1 root root 13 May 31 13:08 usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20240124092219-if00 -> ../../ttyACM0
                      
                      

                      Hier der Log aus der Console

                      2024-05-31 14:36:03.302  - info: host.raspberry4 instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                      2024-05-31 14:36:03.340  - info: admin.0 (2912) <== Disconnect system.user.admin from ::ffff:192.168.0.23
                      2024-05-31 14:36:02.563  - info: host.raspberry4 stopInstance system.adapter.zigbee.0 (force=false, process=true)
                      2024-05-31 14:36:02.571  - info: zigbee.0 (3717) Got terminate signal TERMINATE_YOURSELF
                      2024-05-31 14:36:02.602  - info: host.raspberry4 stopInstance system.adapter.zigbee.0 send kill signal
                      2024-05-31 14:36:02.575  - info: zigbee.0 (3717) cleaned everything up...
                      2024-05-31 14:36:02.582  - info: zigbee.0 (3717) Zigbee: disabling joining new devices.
                      2024-05-31 14:36:02.634  - warn: zigbee.0 (3717) Failed to stop zigbee during startup
                      2024-05-31 14:36:02.635  - info: zigbee.0 (3717) terminating
                      2024-05-31 14:36:02.636  - info: zigbee.0 (3717) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                      2024-05-31 14:36:03.076  - info: zigbee.0 (3717) terminating
                      2024-05-31 14:36:03.302  - info: host.raspberry4 instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                      2024-05-31 14:36:03.340  - info: admin.0 (2912) <== Disconnect system.user.admin from ::ffff:192.168.0.23
                      2024-05-31 14:36:05.672  - info: host.raspberry4 instance system.adapter.zigbee.0 started with pid 3768
                      2024-05-31 14:36:10.832  - info: zigbee.0 (3768) starting. Version 1.10.3 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.14.0, js-controller: 5.0.19
                      2024-05-31 14:36:10.939  - info: zigbee.0 (3768) delete old Backup files. keep only last 10
                      2024-05-31 14:36:10.942  - info: zigbee.0 (3768) Starting Zigbee  npm ...
                      2024-05-31 14:36:11.303  - info: zigbee.0 (3768) Installed Version: iobroker.zigbee@1.10.3
                      2024-05-31 14:36:10.832  - info: zigbee.0 (3768) starting. Version 1.10.3 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.14.0, js-controller: 5.0.19
                      2024-05-31 14:36:10.939  - info: zigbee.0 (3768) delete old Backup files. keep only last 10
                      2024-05-31 14:36:10.942  - info: zigbee.0 (3768) Starting Zigbee  npm ...
                      2024-05-31 14:36:11.303  - info: zigbee.0 (3768) Installed Version: iobroker.zigbee@1.10.3
                      2024-05-31 14:36:15.301  - error: zigbee.0 (3768) Starting zigbee-herdsman problem : "startup failed - configuration-adapter mismatch - see logs above for more information"
                      2024-05-31 14:36:15.302  - error: zigbee.0 (3768) Failed to start Zigbee
                      2024-05-31 14:36:15.303  - error: zigbee.0 (3768) Error herdsman start
                      2024-05-31 14:36:15.301  - error: zigbee.0 (3768) Starting zigbee-herdsman problem : "startup failed - configuration-adapter mismatch - see logs above for more information"
                      2024-05-31 14:36:15.302  - error: zigbee.0 (3768) Failed to start Zigbee
                      2024-05-31 14:36:15.303  - error: zigbee.0 (3768) Error herdsman start
                      
                      
                      Thomas BraunT Online
                      Thomas BraunT Online
                      Thomas Braun
                      Most Active
                      schrieb am zuletzt editiert von
                      #19

                      @jan-lange

                      Keine Bildchen des Logs posten.

                      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
                      • Jan LangeJ Jan Lange

                        @thomas-braun

                        als COM Id habe ich hinterlegt "/dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20240124092219-if00"

                        
                        total 0
                        drwxr-xr-x 2 root root 60 May 31 13:08 .
                        drwxr-xr-x 4 root root 80 May 31 13:08 ..
                        lrwxrwxrwx 1 root root 13 May 31 13:08 usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20240124092219-if00 -> ../../ttyACM0
                        
                        

                        Hier der Log aus der Console

                        2024-05-31 14:36:03.302  - info: host.raspberry4 instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                        2024-05-31 14:36:03.340  - info: admin.0 (2912) <== Disconnect system.user.admin from ::ffff:192.168.0.23
                        2024-05-31 14:36:02.563  - info: host.raspberry4 stopInstance system.adapter.zigbee.0 (force=false, process=true)
                        2024-05-31 14:36:02.571  - info: zigbee.0 (3717) Got terminate signal TERMINATE_YOURSELF
                        2024-05-31 14:36:02.602  - info: host.raspberry4 stopInstance system.adapter.zigbee.0 send kill signal
                        2024-05-31 14:36:02.575  - info: zigbee.0 (3717) cleaned everything up...
                        2024-05-31 14:36:02.582  - info: zigbee.0 (3717) Zigbee: disabling joining new devices.
                        2024-05-31 14:36:02.634  - warn: zigbee.0 (3717) Failed to stop zigbee during startup
                        2024-05-31 14:36:02.635  - info: zigbee.0 (3717) terminating
                        2024-05-31 14:36:02.636  - info: zigbee.0 (3717) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                        2024-05-31 14:36:03.076  - info: zigbee.0 (3717) terminating
                        2024-05-31 14:36:03.302  - info: host.raspberry4 instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                        2024-05-31 14:36:03.340  - info: admin.0 (2912) <== Disconnect system.user.admin from ::ffff:192.168.0.23
                        2024-05-31 14:36:05.672  - info: host.raspberry4 instance system.adapter.zigbee.0 started with pid 3768
                        2024-05-31 14:36:10.832  - info: zigbee.0 (3768) starting. Version 1.10.3 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.14.0, js-controller: 5.0.19
                        2024-05-31 14:36:10.939  - info: zigbee.0 (3768) delete old Backup files. keep only last 10
                        2024-05-31 14:36:10.942  - info: zigbee.0 (3768) Starting Zigbee  npm ...
                        2024-05-31 14:36:11.303  - info: zigbee.0 (3768) Installed Version: iobroker.zigbee@1.10.3
                        2024-05-31 14:36:10.832  - info: zigbee.0 (3768) starting. Version 1.10.3 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.14.0, js-controller: 5.0.19
                        2024-05-31 14:36:10.939  - info: zigbee.0 (3768) delete old Backup files. keep only last 10
                        2024-05-31 14:36:10.942  - info: zigbee.0 (3768) Starting Zigbee  npm ...
                        2024-05-31 14:36:11.303  - info: zigbee.0 (3768) Installed Version: iobroker.zigbee@1.10.3
                        2024-05-31 14:36:15.301  - error: zigbee.0 (3768) Starting zigbee-herdsman problem : "startup failed - configuration-adapter mismatch - see logs above for more information"
                        2024-05-31 14:36:15.302  - error: zigbee.0 (3768) Failed to start Zigbee
                        2024-05-31 14:36:15.303  - error: zigbee.0 (3768) Error herdsman start
                        2024-05-31 14:36:15.301  - error: zigbee.0 (3768) Starting zigbee-herdsman problem : "startup failed - configuration-adapter mismatch - see logs above for more information"
                        2024-05-31 14:36:15.302  - error: zigbee.0 (3768) Failed to start Zigbee
                        2024-05-31 14:36:15.303  - error: zigbee.0 (3768) Error herdsman start
                        
                        
                        HomoranH Nicht stören
                        HomoranH Nicht stören
                        Homoran
                        Global Moderator Administrators
                        schrieb am zuletzt editiert von
                        #20

                        @jan-lange kaum zu entziffern, bitte als text in code-tags posten.
                        und vorher die Logstufe der Instanz auf debug stellen

                        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
                        • Jan LangeJ Jan Lange

                          @thomas-braun

                          als COM Id habe ich hinterlegt "/dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20240124092219-if00"

                          
                          total 0
                          drwxr-xr-x 2 root root 60 May 31 13:08 .
                          drwxr-xr-x 4 root root 80 May 31 13:08 ..
                          lrwxrwxrwx 1 root root 13 May 31 13:08 usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20240124092219-if00 -> ../../ttyACM0
                          
                          

                          Hier der Log aus der Console

                          2024-05-31 14:36:03.302  - info: host.raspberry4 instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                          2024-05-31 14:36:03.340  - info: admin.0 (2912) <== Disconnect system.user.admin from ::ffff:192.168.0.23
                          2024-05-31 14:36:02.563  - info: host.raspberry4 stopInstance system.adapter.zigbee.0 (force=false, process=true)
                          2024-05-31 14:36:02.571  - info: zigbee.0 (3717) Got terminate signal TERMINATE_YOURSELF
                          2024-05-31 14:36:02.602  - info: host.raspberry4 stopInstance system.adapter.zigbee.0 send kill signal
                          2024-05-31 14:36:02.575  - info: zigbee.0 (3717) cleaned everything up...
                          2024-05-31 14:36:02.582  - info: zigbee.0 (3717) Zigbee: disabling joining new devices.
                          2024-05-31 14:36:02.634  - warn: zigbee.0 (3717) Failed to stop zigbee during startup
                          2024-05-31 14:36:02.635  - info: zigbee.0 (3717) terminating
                          2024-05-31 14:36:02.636  - info: zigbee.0 (3717) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                          2024-05-31 14:36:03.076  - info: zigbee.0 (3717) terminating
                          2024-05-31 14:36:03.302  - info: host.raspberry4 instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                          2024-05-31 14:36:03.340  - info: admin.0 (2912) <== Disconnect system.user.admin from ::ffff:192.168.0.23
                          2024-05-31 14:36:05.672  - info: host.raspberry4 instance system.adapter.zigbee.0 started with pid 3768
                          2024-05-31 14:36:10.832  - info: zigbee.0 (3768) starting. Version 1.10.3 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.14.0, js-controller: 5.0.19
                          2024-05-31 14:36:10.939  - info: zigbee.0 (3768) delete old Backup files. keep only last 10
                          2024-05-31 14:36:10.942  - info: zigbee.0 (3768) Starting Zigbee  npm ...
                          2024-05-31 14:36:11.303  - info: zigbee.0 (3768) Installed Version: iobroker.zigbee@1.10.3
                          2024-05-31 14:36:10.832  - info: zigbee.0 (3768) starting. Version 1.10.3 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.14.0, js-controller: 5.0.19
                          2024-05-31 14:36:10.939  - info: zigbee.0 (3768) delete old Backup files. keep only last 10
                          2024-05-31 14:36:10.942  - info: zigbee.0 (3768) Starting Zigbee  npm ...
                          2024-05-31 14:36:11.303  - info: zigbee.0 (3768) Installed Version: iobroker.zigbee@1.10.3
                          2024-05-31 14:36:15.301  - error: zigbee.0 (3768) Starting zigbee-herdsman problem : "startup failed - configuration-adapter mismatch - see logs above for more information"
                          2024-05-31 14:36:15.302  - error: zigbee.0 (3768) Failed to start Zigbee
                          2024-05-31 14:36:15.303  - error: zigbee.0 (3768) Error herdsman start
                          2024-05-31 14:36:15.301  - error: zigbee.0 (3768) Starting zigbee-herdsman problem : "startup failed - configuration-adapter mismatch - see logs above for more information"
                          2024-05-31 14:36:15.302  - error: zigbee.0 (3768) Failed to start Zigbee
                          2024-05-31 14:36:15.303  - error: zigbee.0 (3768) Error herdsman start
                          
                          
                          Thomas BraunT Online
                          Thomas BraunT Online
                          Thomas Braun
                          Most Active
                          schrieb am zuletzt editiert von
                          #21

                          @jan-lange sagte in Hilfe beim Zigbee Controller mit Sonoff Zigbee 3.0:

                          2024-05-31 14:36:15.301 - error: zigbee.0 (3768) Starting zigbee-herdsman problem : "startup failed - configuration-adapter mismatch - see logs above for more information"

                          Da ist die PanID, die extended PanID oder der Transportschlüssel falsch. Früher standen die Abweichungen mal im Log. Ist wohl irgendwann unter den Tisch gefallen.

                          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

                          Jan LangeJ 2 Antworten Letzte Antwort
                          0
                          • Thomas BraunT Thomas Braun

                            @jan-lange sagte in Hilfe beim Zigbee Controller mit Sonoff Zigbee 3.0:

                            2024-05-31 14:36:15.301 - error: zigbee.0 (3768) Starting zigbee-herdsman problem : "startup failed - configuration-adapter mismatch - see logs above for more information"

                            Da ist die PanID, die extended PanID oder der Transportschlüssel falsch. Früher standen die Abweichungen mal im Log. Ist wohl irgendwann unter den Tisch gefallen.

                            Jan LangeJ Offline
                            Jan LangeJ Offline
                            Jan Lange
                            schrieb am zuletzt editiert von
                            #22

                            @thomas-braun

                            Hier noch mal der Log mit debug Info:

                            
                            2024-05-31 14:39:51.043  - info: host.raspberry4 stopInstance system.adapter.zigbee.0 (force=false, process=true)
                            2024-05-31 14:39:51.056  - info: zigbee.0 (3869) Got terminate signal TERMINATE_YOURSELF
                            2024-05-31 14:39:51.061  - info: zigbee.0 (3869) cleaned everything up...
                            2024-05-31 14:39:51.079  - info: zigbee.0 (3869) Zigbee: disabling joining new devices.
                            2024-05-31 14:39:51.134  - warn: zigbee.0 (3869) Failed to stop zigbee during startup
                            2024-05-31 14:39:51.134  - info: zigbee.0 (3869) terminating
                            2024-05-31 14:39:51.136  - debug: zigbee.0 (3869) Plugin sentry destroyed
                            2024-05-31 14:39:51.136  - info: zigbee.0 (3869) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                            2024-05-31 14:39:51.160  - info: host.raspberry4 stopInstance system.adapter.zigbee.0 send kill signal
                            2024-05-31 14:39:51.563  - info: zigbee.0 (3869) terminating
                            2024-05-31 14:39:51.736  - info: host.raspberry4 instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                            2024-05-31 14:39:54.222  - info: host.raspberry4 instance system.adapter.zigbee.0 started with pid 3897
                            2024-05-31 14:39:58.744  - debug: zigbee.0 (3897) Redis Objects: Use Redis connection: 127.0.0.1:9001
                            2024-05-31 14:39:58.800  - debug: zigbee.0 (3897) Objects client ready ... initialize now
                            2024-05-31 14:39:58.804  - debug: zigbee.0 (3897) Objects create System PubSub Client
                            2024-05-31 14:39:58.806  - debug: zigbee.0 (3897) Objects create User PubSub Client
                            2024-05-31 14:39:58.887  - debug: zigbee.0 (3897) Objects client initialize lua scripts
                            2024-05-31 14:39:58.900  - debug: zigbee.0 (3897) Objects connected to redis: 127.0.0.1:9001
                            2024-05-31 14:39:58.949  - debug: zigbee.0 (3897) Redis States: Use Redis connection: 127.0.0.1:9000
                            2024-05-31 14:39:58.972  - debug: zigbee.0 (3897) States create System PubSub Client
                            2024-05-31 14:39:58.974  - debug: zigbee.0 (3897) States create User PubSub Client
                            2024-05-31 14:39:59.056  - debug: zigbee.0 (3897) States connected to redis: 127.0.0.1:9000
                            2024-05-31 14:39:59.107  - debug: zigbee.0 (3897) Plugin sentry Initialize Plugin (enabled=true)
                            2024-05-31 14:39:59.625  - info: zigbee.0 (3897) starting. Version 1.10.3 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.14.0, js-controller: 5.0.19
                            2024-05-31 14:39:59.659  - debug: zigbee.0 (3897) Using zigbee-herdsman with settings: {"network":{"panID":6754,"channelList":[11],"networkKey":[1,3,5,7,9,11,13,15,0,2,4,6,8,10,12,13],"extenedPanID":[208,221,220,221,221,210,222,173]},"databasePath":"/opt/iobroker/iobroker-data/zigbee_0/shepherd.db","backupPath":"/opt/iobroker/iobroker-data/zigbee_0/nvbackup.json","serialPort":{"baudRate":115200,"rtscts":false,"path":"/dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20240124092219-if00","adapter":"ezsp"},"adapter":{"forceStartWithInconsistentAdapterConfiguration":false},"legacy":false}
                            2024-05-31 14:39:59.722  - info: zigbee.0 (3897) delete old Backup files. keep only last 10
                            2024-05-31 14:39:59.724  - info: zigbee.0 (3897) Starting Zigbee  npm ...
                            2024-05-31 14:39:59.778  - debug: zigbee.0 (3897) Starting zigbee-herdsman...
                            2024-05-31 14:40:00.089  - info: zigbee.0 (3897) Installed Version: iobroker.zigbee@1.10.3
                            2024-05-31 14:40:00.488  - debug: zigbee.0 (3897) Backup /opt/iobroker/iobroker-data/zigbee_0/backup_2024_05_31-14_39_59.tar.gz success
                            2024-05-31 14:39:58.744  - debug: zigbee.0 (3897) Redis Objects: Use Redis connection: 127.0.0.1:9001
                            2024-05-31 14:39:58.800  - debug: zigbee.0 (3897) Objects client ready ... initialize now
                            2024-05-31 14:39:58.804  - debug: zigbee.0 (3897) Objects create System PubSub Client
                            2024-05-31 14:39:58.806  - debug: zigbee.0 (3897) Objects create User PubSub Client
                            2024-05-31 14:39:58.887  - debug: zigbee.0 (3897) Objects client initialize lua scripts
                            2024-05-31 14:39:58.900  - debug: zigbee.0 (3897) Objects connected to redis: 127.0.0.1:9001
                            2024-05-31 14:39:58.949  - debug: zigbee.0 (3897) Redis States: Use Redis connection: 127.0.0.1:9000
                            2024-05-31 14:39:58.972  - debug: zigbee.0 (3897) States create System PubSub Client
                            2024-05-31 14:39:58.974  - debug: zigbee.0 (3897) States create User PubSub Client
                            2024-05-31 14:39:59.056  - debug: zigbee.0 (3897) States connected to redis: 127.0.0.1:9000
                            2024-05-31 14:39:59.107  - debug: zigbee.0 (3897) Plugin sentry Initialize Plugin (enabled=true)
                            2024-05-31 14:39:59.625  - info: zigbee.0 (3897) starting. Version 1.10.3 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.14.0, js-controller: 5.0.19
                            2024-05-31 14:39:59.659  - debug: zigbee.0 (3897) Using zigbee-herdsman with settings: {"network":{"panID":6754,"channelList":[11],"networkKey":[1,3,5,7,9,11,13,15,0,2,4,6,8,10,12,13],"extenedPanID":[208,221,220,221,221,210,222,173]},"databasePath":"/opt/iobroker/iobroker-data/zigbee_0/shepherd.db","backupPath":"/opt/iobroker/iobroker-data/zigbee_0/nvbackup.json","serialPort":{"baudRate":115200,"rtscts":false,"path":"/dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20240124092219-if00","adapter":"ezsp"},"adapter":{"forceStartWithInconsistentAdapterConfiguration":false},"legacy":false}
                            2024-05-31 14:39:59.722  - info: zigbee.0 (3897) delete old Backup files. keep only last 10
                            2024-05-31 14:39:59.724  - info: zigbee.0 (3897) Starting Zigbee  npm ...
                            2024-05-31 14:39:59.778  - debug: zigbee.0 (3897) Starting zigbee-herdsman...
                            2024-05-31 14:40:00.089  - info: zigbee.0 (3897) Installed Version: iobroker.zigbee@1.10.3
                            2024-05-31 14:40:00.488  - debug: zigbee.0 (3897) Backup /opt/iobroker/iobroker-data/zigbee_0/backup_2024_05_31-14_39_59.tar.gz success
                            2024-05-31 14:40:04.040  - error: zigbee.0 (3897) Starting zigbee-herdsman problem : "startup failed - configuration-adapter mismatch - see logs above for more information"
                            2024-05-31 14:40:04.042  - error: zigbee.0 (3897) Failed to start Zigbee
                            2024-05-31 14:40:04.043  - error: zigbee.0 (3897) Error herdsman start
                            2024-05-31 14:40:04.040  - error: zigbee.0 (3897) Starting zigbee-herdsman problem : "startup failed - configuration-adapter mismatch - see logs above for more information"
                            2024-05-31 14:40:04.042  - error: zigbee.0 (3897) Failed to start Zigbee
                            2024-05-31 14:40:04.043  - error: zigbee.0 (3897) Error herdsman start
                            
                            
                            1 Antwort Letzte Antwort
                            0
                            • Thomas BraunT Thomas Braun

                              @jan-lange sagte in Hilfe beim Zigbee Controller mit Sonoff Zigbee 3.0:

                              2024-05-31 14:36:15.301 - error: zigbee.0 (3768) Starting zigbee-herdsman problem : "startup failed - configuration-adapter mismatch - see logs above for more information"

                              Da ist die PanID, die extended PanID oder der Transportschlüssel falsch. Früher standen die Abweichungen mal im Log. Ist wohl irgendwann unter den Tisch gefallen.

                              Jan LangeJ Offline
                              Jan LangeJ Offline
                              Jan Lange
                              schrieb am zuletzt editiert von
                              #23

                              @thomas-braun

                              das hatte ich ja auch vermutet. Nur wie finde ich raus welche die Richtigen sind?

                              Thomas BraunT 1 Antwort Letzte Antwort
                              0
                              • Jan LangeJ Jan Lange

                                @thomas-braun

                                das hatte ich ja auch vermutet. Nur wie finde ich raus welche die Richtigen sind?

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

                                @jan-lange sagte in Hilfe beim Zigbee Controller mit Sonoff Zigbee 3.0:

                                Nur wie finde ich raus welche die Richtigen sind?

                                Keine Ahnung. Wie gesagt, früher stands mal im Log drin.

                                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
                                • Jan LangeJ Jan Lange

                                  @thomas-braun

                                  als COM Id habe ich hinterlegt "/dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20240124092219-if00"

                                  
                                  total 0
                                  drwxr-xr-x 2 root root 60 May 31 13:08 .
                                  drwxr-xr-x 4 root root 80 May 31 13:08 ..
                                  lrwxrwxrwx 1 root root 13 May 31 13:08 usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20240124092219-if00 -> ../../ttyACM0
                                  
                                  

                                  Hier der Log aus der Console

                                  2024-05-31 14:36:03.302  - info: host.raspberry4 instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                                  2024-05-31 14:36:03.340  - info: admin.0 (2912) <== Disconnect system.user.admin from ::ffff:192.168.0.23
                                  2024-05-31 14:36:02.563  - info: host.raspberry4 stopInstance system.adapter.zigbee.0 (force=false, process=true)
                                  2024-05-31 14:36:02.571  - info: zigbee.0 (3717) Got terminate signal TERMINATE_YOURSELF
                                  2024-05-31 14:36:02.602  - info: host.raspberry4 stopInstance system.adapter.zigbee.0 send kill signal
                                  2024-05-31 14:36:02.575  - info: zigbee.0 (3717) cleaned everything up...
                                  2024-05-31 14:36:02.582  - info: zigbee.0 (3717) Zigbee: disabling joining new devices.
                                  2024-05-31 14:36:02.634  - warn: zigbee.0 (3717) Failed to stop zigbee during startup
                                  2024-05-31 14:36:02.635  - info: zigbee.0 (3717) terminating
                                  2024-05-31 14:36:02.636  - info: zigbee.0 (3717) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                                  2024-05-31 14:36:03.076  - info: zigbee.0 (3717) terminating
                                  2024-05-31 14:36:03.302  - info: host.raspberry4 instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                                  2024-05-31 14:36:03.340  - info: admin.0 (2912) <== Disconnect system.user.admin from ::ffff:192.168.0.23
                                  2024-05-31 14:36:05.672  - info: host.raspberry4 instance system.adapter.zigbee.0 started with pid 3768
                                  2024-05-31 14:36:10.832  - info: zigbee.0 (3768) starting. Version 1.10.3 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.14.0, js-controller: 5.0.19
                                  2024-05-31 14:36:10.939  - info: zigbee.0 (3768) delete old Backup files. keep only last 10
                                  2024-05-31 14:36:10.942  - info: zigbee.0 (3768) Starting Zigbee  npm ...
                                  2024-05-31 14:36:11.303  - info: zigbee.0 (3768) Installed Version: iobroker.zigbee@1.10.3
                                  2024-05-31 14:36:10.832  - info: zigbee.0 (3768) starting. Version 1.10.3 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.14.0, js-controller: 5.0.19
                                  2024-05-31 14:36:10.939  - info: zigbee.0 (3768) delete old Backup files. keep only last 10
                                  2024-05-31 14:36:10.942  - info: zigbee.0 (3768) Starting Zigbee  npm ...
                                  2024-05-31 14:36:11.303  - info: zigbee.0 (3768) Installed Version: iobroker.zigbee@1.10.3
                                  2024-05-31 14:36:15.301  - error: zigbee.0 (3768) Starting zigbee-herdsman problem : "startup failed - configuration-adapter mismatch - see logs above for more information"
                                  2024-05-31 14:36:15.302  - error: zigbee.0 (3768) Failed to start Zigbee
                                  2024-05-31 14:36:15.303  - error: zigbee.0 (3768) Error herdsman start
                                  2024-05-31 14:36:15.301  - error: zigbee.0 (3768) Starting zigbee-herdsman problem : "startup failed - configuration-adapter mismatch - see logs above for more information"
                                  2024-05-31 14:36:15.302  - error: zigbee.0 (3768) Failed to start Zigbee
                                  2024-05-31 14:36:15.303  - error: zigbee.0 (3768) Error herdsman start
                                  
                                  
                                  crunchipC Abwesend
                                  crunchipC Abwesend
                                  crunchip
                                  Forum Testing Most Active
                                  schrieb am zuletzt editiert von
                                  #25

                                  @jan-lange sagte in Hilfe beim Zigbee Controller mit Sonoff Zigbee 3.0:

                                  als COM Id habe ich hinterlegt "/dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20240124092219-if00"

                                  fehlt da nicht der Port?

                                  umgestiegen von Proxmox auf Unraid

                                  Thomas BraunT 1 Antwort Letzte Antwort
                                  0
                                  • crunchipC crunchip

                                    @jan-lange sagte in Hilfe beim Zigbee Controller mit Sonoff Zigbee 3.0:

                                    als COM Id habe ich hinterlegt "/dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20240124092219-if00"

                                    fehlt da nicht der Port?

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

                                    @crunchip

                                    Nein.

                                    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_V2_20240124092219-if00
                                    

                                    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

                                    crunchipC 1 Antwort Letzte Antwort
                                    0
                                    • Thomas BraunT Thomas Braun

                                      @crunchip

                                      Nein.

                                      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_V2_20240124092219-if00
                                      
                                      crunchipC Abwesend
                                      crunchipC Abwesend
                                      crunchip
                                      Forum Testing Most Active
                                      schrieb am zuletzt editiert von
                                      #27

                                      @thomas-braun ok, dann wäre vllt noch möglich

                                      Es ist zu achten dass am Ende kein leer Zeichen mitgenommen wird
                                      

                                      umgestiegen von Proxmox auf Unraid

                                      Thomas BraunT 1 Antwort Letzte Antwort
                                      0
                                      • crunchipC crunchip

                                        @thomas-braun ok, dann wäre vllt noch möglich

                                        Es ist zu achten dass am Ende kein leer Zeichen mitgenommen wird
                                        
                                        Thomas BraunT Online
                                        Thomas BraunT Online
                                        Thomas Braun
                                        Most Active
                                        schrieb am zuletzt editiert von
                                        #28

                                        @crunchip

                                        Ja. Hier ist aber vermutlich das nvram/backup zu löschen.

                                        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

                                        crunchipC 1 Antwort Letzte Antwort
                                        0
                                        • Thomas BraunT Thomas Braun

                                          @crunchip

                                          Ja. Hier ist aber vermutlich das nvram/backup zu löschen.

                                          crunchipC Abwesend
                                          crunchipC Abwesend
                                          crunchip
                                          Forum Testing Most Active
                                          schrieb am zuletzt editiert von
                                          #29

                                          @thomas-braun jep, hatte ich auch im parallel Thread geschrieben

                                          umgestiegen von Proxmox auf Unraid

                                          Jan LangeJ 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

                                          378

                                          Online

                                          32.4k

                                          Benutzer

                                          81.5k

                                          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