Skip to content
  • Home
  • Recent
  • Tags
  • 0 Unread 0
  • Categories
  • Unreplied
  • Popular
  • 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

  • Default (No Skin)
  • No Skin
Collapse
ioBroker Logo

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. ioBroker Allgemein
  4. [gelöst]SONOFF ZigBee 3.0 wird n. in Zigbee eingebunden

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.3k

[gelöst]SONOFF ZigBee 3.0 wird n. in Zigbee eingebunden

Scheduled Pinned Locked Moved ioBroker Allgemein
11 Posts 4 Posters 602 Views 4 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • H Offline
    H Offline
    Högi
    wrote on last edited by Högi
    #1
    *** BASE SYSTEM ***
     Static hostname: raspberrypi64bitbookworm
           Icon name: computer
    Operating System: Debian GNU/Linux 12 (bookworm)
              Kernel: Linux 6.12.25+rpt-rpi-v8
        Architecture: arm64
    OS is similar to:
    
    Model           : Raspberry Pi 4 Model B Rev 1.1
    Docker          : false
    Virtualization  : none
    Kernel          : aarch64
    Userland        : 64 bit
    
    Systemuptime and Load:
     20:35:21 up 59 min,  2 users,  load average: 0.23, 0.20, 0.27
    CPU threads: 4
    
    
    *** LIFE CYCLE STATUS ***
    Operating System is the current Debian stable version codenamed 'bookworm'!
    
    *** RASPBERRY THROTTLING ***
    Current issues:
    No throttling issues detected.
    
    Previously detected issues:
    No throttling issues detected.
    
    *** TIME AND TIMEZONES ***
                   Local time: Thu 2025-05-22 20:35:21 CEST
               Universal time: Thu 2025-05-22 18:35:21 UTC
                     RTC time: Thu 2025-05-22 18:35:21
                    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':
    josef
    HOME=/home/josef
    GROUPS=josef adm dialout cdrom sudo audio video plugdev games users input render netdev gpio i2c spi iobroker
    
    User that is running 'js-controller':
    iobroker
    HOME=/home/iobroker
    GROUPS=iobroker tty dialout audio video plugdev bluetooth gpio i2c
    
    *** DISPLAY-SERVER SETUP ***
    Display-Server: false
    Desktop:
    Terminal:       tty
    
    *** MEMORY ***
                   total        used        free      shared  buff/cache   available
    Mem:            4.0G        2.2G        1.3G        6.3M        554M        1.8G
    Swap:           536M          0B        536M
    Total:          4.5G        2.2G        1.8G
    
    Active iob-Instances:   23
    
             3791 M total memory
             2097 M used memory
             2147 M active memory
              256 M inactive memory
             1243 M free memory
               50 M buffer memory
              478 M swap cache
              511 M total swap
                0 M used swap
              511 M free swap
    
    *** top - Table Of Processes  ***
    top - 20:35:22 up 59 min,  2 users,  load average: 0.23, 0.20, 0.27
    Tasks: 235 total,   1 running, 234 sleeping,   0 stopped,   0 zombie
    %Cpu(s):  0.0 us, 16.7 sy,  0.0 ni, 83.3 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
    MiB Mem :   3791.4 total,   1243.5 free,   2097.5 used,    529.2 buff/cache
    MiB Swap:    512.0 total,    512.0 free,      0.0 used.   1694.0 avail Mem
    
    *** FAILED SERVICES ***
    
      UNIT LOAD ACTIVE SUB DESCRIPTION
    0 loaded units listed.
    
    
    *** DMESG CRITICAL ERRORS ***
    No critical errors detected
    
    *** FILESYSTEM ***
    Filesystem     Type      Size  Used Avail Use% Mounted on
    udev           devtmpfs  1.6G     0  1.6G   0% /dev
    tmpfs          tmpfs     380M  6.0M  374M   2% /run
    /dev/mmcblk0p2 ext4       59G  7.1G   49G  13% /
    tmpfs          tmpfs     1.9G     0  1.9G   0% /dev/shm
    tmpfs          tmpfs     5.0M   16K  5.0M   1% /run/lock
    /dev/mmcblk0p1 vfat      510M   57M  454M  12% /boot/firmware
    tmpfs          tmpfs     380M     0  380M   0% /run/user/1000
    
    Messages concerning ext4 filesystem in dmesg:
    [Thu May 22 19:35:30 2025] Kernel command line: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_headphones=0 cgroup_disable=memory numa_policy=interleave snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0  smsc95xx.macaddr=DC:A6:32:1C:58:B7 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000  console=tty1 root=PARTUUID=3907a7b3-02 rootfstype=ext4 fsck.repair=yes rootwait
    [Thu May 22 19:35:31 2025] EXT4-fs (mmcblk0p2): mounted filesystem d4cc7d63-da78-48ad-9bdd-64ffbba449a8 ro with ordered data mode. Quota mode: none.
    [Thu May 22 19:35:33 2025] EXT4-fs (mmcblk0p2): re-mounted d4cc7d63-da78-48ad-9bdd-64ffbba449a8 r/w. Quota mode: none.
    
    Show mounted filesystems:
    TARGET           SOURCE         FSTYPE OPTIONS
    /                /dev/mmcblk0p2 ext4   rw,noatime
    `-/boot/firmware /dev/mmcblk0p1 vfat   rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro
    
    Files in neuralgic directories:
    
    /var:
    1.6G    /var/
    861M    /var/lib
    684M    /var/lib/piVCCU3
    617M    /var/lib/piVCCU3/rootfs
    288M    /var/lib/piVCCU3/rootfs/opt
    
    Archived and active journals take up 4.7M in the file system.
    
    /opt/iobroker/backups:
    1.8M    /opt/iobroker/backups/
    
    /opt/iobroker/iobroker-data:
    924M    /opt/iobroker/iobroker-data/
    836M    /opt/iobroker/iobroker-data/files
    617M    /opt/iobroker/iobroker-data/files/javascript.admin
    560M    /opt/iobroker/iobroker-data/files/javascript.admin/static
    558M    /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.d3d286bd.js.map
    25M     /opt/iobroker/iobroker-data/objects.jsonl
    24M     /opt/iobroker/iobroker-data/files/scenes.admin/static/js/main.c9369f6c.js.map
    19M     /opt/iobroker/iobroker-data/files/text2command.admin/static/js/main.02fc3820.js.map
    8.8M    /opt/iobroker/iobroker-data/files/iot.admin/static/js/main.d3d286bd.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_2e3882639474ef11b58fd08c8fcc3fa0-if00-port0
    
    *** ZigBee Settings ***
    
    Your zigbee.0 COM-Port is matching 'by-id'. Very good!
    Zigbee Network Settings on your coordinator/in nvbackup are:
    
    zigbee.X
    Extended Pan ID:
    *** MASKED ***
    Pan ID:
    *** MASKED ***
    Channel:
    *** MASKED ***
    Network Key:
    *** MASKED ***
    
    To unmask the settings run 'iob diag --unmask'
    
    
    *** NodeJS-Installation ***
    
    /usr/bin/nodejs         v20.19.2
    /usr/bin/node           v20.19.2
    /usr/bin/npm            10.8.2
    /usr/bin/npx            10.8.2
    /usr/bin/corepack       0.31.0
    
    nodejs:
      Installed: 20.19.2-1nodesource1
      Candidate: 20.19.2-1nodesource1
      Version table:
     *** 20.19.2-1nodesource1 1001
            500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
            100 /var/lib/dpkg/status
         20.19.1-1nodesource1 1001
            500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
         20.19.0-1nodesource1 1001
            500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
         20.18.3-1nodesource1 1001
            500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
         20.18.2-1nodesource1 1001
            500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
         20.18.1-1nodesource1 1001
            500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
         20.18.0-1nodesource1 1001
            500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
         20.17.0-1nodesource1 1001
            500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
         20.16.0-1nodesource1 1001
            500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
         20.15.1-1nodesource1 1001
            500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
         20.15.0-1nodesource1 1001
            500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
         20.14.0-1nodesource1 1001
            500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
         20.13.1-1nodesource1 1001
            500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
         20.13.0-1nodesource1 1001
            500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
         20.12.2-1nodesource1 1001
            500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
         20.12.1-1nodesource1 1001
            500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
         20.12.0-1nodesource1 1001
            500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
         20.11.1-1nodesource1 1001
            500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
         20.11.0-1nodesource1 1001
            500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
         20.10.0-1nodesource1 1001
            500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
         20.9.0-1nodesource1 1001
            500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
         20.8.1-1nodesource1 1001
            500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
         20.8.0-1nodesource1 1001
            500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
         20.7.0-1nodesource1 1001
            500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
         20.6.1-1nodesource1 1001
            500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
         20.6.0-1nodesource1 1001
            500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
         20.5.1-1nodesource1 1001
            500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
         20.5.0-1nodesource1 1001
            500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
         20.4.0-1nodesource1 1001
            500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
         20.3.1-1nodesource1 1001
            500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
         20.3.0-1nodesource1 1001
            500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
         20.2.0-1nodesource1 1001
            500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
         20.1.0-1nodesource1 1001
            500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
         20.0.0-1nodesource1 1001
            500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
         18.19.0+dfsg-6~deb12u2 500
            500 http://deb.debian.org/debian bookworm/main arm64 Packages
         18.19.0+dfsg-6~deb12u1 500
            500 http://deb.debian.org/debian-security bookworm-security/main arm64 Packages
    
    Temp directories causing deletion problem: 0
    No problems detected
    
    Errors in npm tree: 0
    No problems detected
    
    *** ioBroker-Installation ***
    
    ioBroker Status
    iobroker is running on this host.
    
    
    Objects type: jsonl
    States  type: jsonl
    
    Hosts:
    raspberrypi64bitbookworm raspberrypi64bitbookworm (version: 7.0.6, hostname: raspberrypi64bitbookworm, alive, uptime: 3591)
    
    Core adapters versions
    js-controller:  7.0.6
    admin:          7.6.3
    javascript:     8.8.3
    
    nodejs modules from github:     0
    
    Adapter State
    + system.adapter.admin.0                  : admin                 : raspberrypi64bitbookworm                 -  enabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin
    + system.adapter.alexa2.0                 : alexa2                : raspberrypi64bitbookworm                 -  enabled
    + system.adapter.backitup.0               : backitup              : raspberrypi64bitbookworm                 -  enabled
    + system.adapter.broadlink2.0             : broadlink2            : raspberrypi64bitbookworm                 -  enabled
    + system.adapter.discovery.0              : discovery             : raspberrypi64bitbookworm                 -  enabled
    + system.adapter.email.0                  : email                 : raspberrypi64bitbookworm                 -  enabled
    + system.adapter.hm-rega.0                : hm-rega               : raspberrypi64bitbookworm                 -  enabled
    + system.adapter.hm-rpc.0                 : hm-rpc                : raspberrypi64bitbookworm                 -  enabled, port: 0
    + system.adapter.hm-rpc.1                 : hm-rpc                : raspberrypi64bitbookworm                 -  enabled, port: 0
    + system.adapter.hm-rpc.2                 : hm-rpc                : raspberrypi64bitbookworm                 -  enabled, port: 0
    + system.adapter.iot.0                    : iot                   : raspberrypi64bitbookworm                 -  enabled
    + system.adapter.javascript.0             : javascript            : raspberrypi64bitbookworm                 -  enabled
    + system.adapter.ping.0                   : ping                  : raspberrypi64bitbookworm                 -  enabled
    + system.adapter.pushover.0               : pushover              : raspberrypi64bitbookworm                 -  enabled
    + system.adapter.scenes.0                 : scenes                : raspberrypi64bitbookworm                 -  enabled
    + system.adapter.shelly.0                 : shelly                : raspberrypi64bitbookworm                 -  enabled, port: 1882, bind: 0.0.0.0
    + system.adapter.simple-api.0             : simple-api            : raspberrypi64bitbookworm                 -  enabled, port: 8087, bind: 192.168.178.150, run as: admin
    + system.adapter.sureflap.0               : sureflap              : raspberrypi64bitbookworm                 -  enabled
    + system.adapter.telegram.0               : telegram              : raspberrypi64bitbookworm                 -  enabled, port: 8443, bind: 0.0.0.0
    + system.adapter.text2command.0           : text2command          : raspberrypi64bitbookworm                 -  enabled
    + system.adapter.tuya.0                   : tuya                  : raspberrypi64bitbookworm                 -  enabled
    + system.adapter.web.0                    : web                   : raspberrypi64bitbookworm                 -  enabled, port: 8082, bind: 0.0.0.0, run as: admin
      system.adapter.zigbee.0                 : zigbee                : raspberrypi64bitbookworm                 -  enabled, port: /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_2e3882639474ef11b58fd08c8fcc3fa0-if00-port0
    
    + instance is alive
    
    Enabled adapters with bindings
    + system.adapter.admin.0                  : admin                 : raspberrypi64bitbookworm                 -  enabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin
    + system.adapter.hm-rpc.0                 : hm-rpc                : raspberrypi64bitbookworm                 -  enabled, port: 0
    + system.adapter.hm-rpc.1                 : hm-rpc                : raspberrypi64bitbookworm                 -  enabled, port: 0
    + system.adapter.hm-rpc.2                 : hm-rpc                : raspberrypi64bitbookworm                 -  enabled, port: 0
    + system.adapter.shelly.0                 : shelly                : raspberrypi64bitbookworm                 -  enabled, port: 1882, bind: 0.0.0.0
    + system.adapter.simple-api.0             : simple-api            : raspberrypi64bitbookworm                 -  enabled, port: 8087, bind: 192.168.178.150, run as: admin
    + system.adapter.telegram.0               : telegram              : raspberrypi64bitbookworm                 -  enabled, port: 8443, bind: 0.0.0.0
    + system.adapter.web.0                    : web                   : raspberrypi64bitbookworm                 -  enabled, port: 8082, bind: 0.0.0.0, run as: admin
      system.adapter.zigbee.0                 : zigbee                : raspberrypi64bitbookworm                 -  enabled, port: /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_2e3882639474ef11b58fd08c8fcc3fa0-if00-port0
    
    ioBroker-Repositories
    ┌─────────┬──────────┬─────────────────────────────────────────────────────────┬──────────────┐
    │ (index) │ name     │ url                                                     │ auto upgrade │
    ├─────────┼──────────┼─────────────────────────────────────────────────────────┼──────────────┤
    │ 0       │ 'stable' │ 'http://download.iobroker.net/sources-dist.json'        │ false        │
    │ 1       │ 'beta'   │ 'http://download.iobroker.net/sources-dist-latest.json' │ false        │
    └─────────┴──────────┴─────────────────────────────────────────────────────────┴──────────────┘
    
    Active repo(s): stable
    Upgrade policy: none
    
    Installed ioBroker-Adapters
    Used repository: stable
    Adapter    "admin"        : 7.6.3    , installed 7.6.3
    Adapter    "alexa2"       : 3.26.5   , installed 3.26.5
    Adapter    "backitup"     : 3.0.31   , installed 3.0.31
    Adapter    "broadlink2"   : 2.3.0    , installed 2.3.0
    Adapter    "deyeidc"      : 0.2.0    , installed 0.2.0
    Adapter    "discovery"    : 5.0.0    , installed 5.0.0
    Adapter    "email"        : 2.0.4    , installed 2.0.4
    Adapter    "hm-rega"      : 5.1.0    , installed 5.1.0
    Adapter    "hm-rpc"       : 2.0.2    , installed 2.0.2
    Adapter    "iot"          : 3.3.0    , installed 3.3.0
    Adapter    "javascript"   : 8.8.3    , installed 8.8.3
    Controller "js-controller": 7.0.6    , installed 7.0.6
    Adapter    "ping"         : 1.6.2    , installed 1.6.2
    Adapter    "pushover"     : 4.1.0    , installed 4.1.0
    Adapter    "scenes"       : 3.2.3    , installed 3.2.3
    Adapter    "shelly"       : 9.2.0    , installed 9.2.0
    Adapter    "simple-api"   : 2.8.0    , installed 2.8.0
    Adapter    "socketio"     : 6.7.1    , installed 7.0.8
    Adapter    "sureflap"     : 3.1.1    , installed 3.1.1
    Adapter    "telegram"     : 4.1.0    , installed 4.1.0
    Adapter    "text2command" : 3.0.3    , installed 3.0.3
    Adapter    "tuya"         : 3.16.0   , installed 3.16.0
    Adapter    "web"          : 7.0.8    , installed 7.0.8
    Adapter    "ws"           : 2.6.2    , installed 3.0.19
    Adapter    "zigbee"       : 2.0.5    , installed 2.0.5
    
    Objects and States
    Please stand by - This may take a while
    Objects:        13034
    States:         10197
    
    *** OS-Repositories and Updates ***
    Hit:1 http://deb.debian.org/debian bookworm InRelease
    Hit:2 http://phoscon.de/apt/deconz generic InRelease
    Hit:3 http://archive.raspberrypi.com/debian bookworm InRelease
    Hit:4 http://deb.debian.org/debian-security bookworm-security InRelease
    Hit:5 http://deb.debian.org/debian bookworm-updates InRelease
    Hit:6 https://deb.nodesource.com/node_20.x nodistro InRelease
    Hit:7 https://apt.pivccu.de/piVCCU stable 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 10.0.3.1:53             0.0.0.0:*               LISTEN      0          6464       912/dnsmasq
    tcp        0      0 192.168.178.21:8701     0.0.0.0:*               LISTEN      1001       9054       2223/io.hm-rpc.1
    tcp        0      0 0.0.0.0:1882            0.0.0.0:*               LISTEN      1001       7782       1800/io.shelly.0
    tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      0          6228       637/sshd: /usr/sbin
    tcp        0      0 192.168.178.21:2010     0.0.0.0:*               LISTEN      1001       10540      2287/io.hm-rpc.2
    tcp        0      0 192.168.178.21:42001    0.0.0.0:*               LISTEN      1001       9439       2202/io.hm-rpc.0
    tcp        0      0 127.0.0.1:9001          0.0.0.0:*               LISTEN      1001       5437       625/iobroker.js-con
    tcp        0      0 127.0.0.1:9000          0.0.0.0:*               LISTEN      1001       6247       625/iobroker.js-con
    tcp6       0      0 :::8082                 :::*                    LISTEN      1001       6124       2010/io.web.0
    tcp6       0      0 :::8081                 :::*                    LISTEN      1001       6307       687/io.admin.0
    tcp6       0      0 :::22                   :::*                    LISTEN      0          6230       637/sshd: /usr/sbin
    udp        0      0 10.0.3.1:53             0.0.0.0:*                           0          6463       912/dnsmasq
    udp        0      0 0.0.0.0:67              0.0.0.0:*                           0          6460       912/dnsmasq
    udp        0      0 0.0.0.0:6666            0.0.0.0:*                           1001       7786       1679/io.tuya.0
    udp        0      0 0.0.0.0:6667            0.0.0.0:*                           1001       7787       1679/io.tuya.0
    udp        0      0 0.0.0.0:15001           0.0.0.0:*                           1001       8263       960/io.broadlink2.0
    udp        0      0 0.0.0.0:33798           0.0.0.0:*                           104        6174       503/avahi-daemon: r
    udp        0      0 0.0.0.0:46187           0.0.0.0:*                           1001       8287       960/io.broadlink2.0
    udp        0      0 0.0.0.0:5353            0.0.0.0:*                           104        6172       503/avahi-daemon: r
    udp        0      0 0.0.0.0:44317           0.0.0.0:*                           1001       7465       960/io.broadlink2.0
    udp6       0      0 :::40622                :::*                                104        6175       503/avahi-daemon: r
    udp6       0      0 :::5353                 :::*                                104        6173       503/avahi-daemon: r
    
    *** Log File - Last 25 Lines ***
    
    2025-05-22 20:18:28.783  - info: zigbee.0 (5204) Installed Version: iobroker.zigbee@2.0.5 (Converters 23.6.0 Herdsman 3.5.2)
    2025-05-22 20:18:28.785  - info: zigbee.0 (5204) Starting Zigbee-Herdsman
    2025-05-22 20:18:55.193  - info: zigbee.0 (5204) Unable to obtain herdsman settings
    2025-05-22 20:18:55.345  - error: zigbee.0 (5204) Starting zigbee-herdsman problem : Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
    2025-05-22 20:18:55.347  - error: zigbee.0 (5204) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
    2025-05-22 20:18:55.348  - error: zigbee.0 (5204) unhandled promise rejection: undefined
    2025-05-22 20:18:55.349  - error: zigbee.0 (5204) undefined
    2025-05-22 20:18:55.403  - info: zigbee.0 (5204) cleaned everything up...
    2025-05-22 20:18:55.405  - info: zigbee.0 (5204) local config saved
    2025-05-22 20:18:55.408  - info: zigbee.0 (5204) Saved local configuration data
    2025-05-22 20:18:55.409  - info: zigbee.0 (5204) terminating
    2025-05-22 20:18:55.412  - warn: zigbee.0 (5204) Terminated (UNCAUGHT_EXCEPTION): Without reason
    2025-05-22 20:18:55.423  - error: zigbee.0 (5204) Failed to open the network: TypeError: Cannot read properties of undefined (reading 'permitJoin')
        at Controller.permitJoin (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/controller.ts:315:35)
        at ZigbeeController.permitJoin (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:659:33)
        at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:634:24)
        at processTicksAndRejections (node:internal/process/task_queues:95:5)
        at Zigbee.onUnload (/opt/iobroker/node_modules/iobroker.zigbee/main.js:1037:17)
    2025-05-22 20:18:55.427  - info: zigbee.0 (5204) terminating
    2025-05-22 20:18:55.914  - info: zigbee.0 (5204) terminating
    2025-05-22 20:18:56.099  - error: host.raspberrypi64bitbookworm Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
    2025-05-22 20:18:56.100  - error: host.raspberrypi64bitbookworm Caught by controller[0]: Error herdsman start
    2025-05-22 20:18:56.100  - error: host.raspberrypi64bitbookworm instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
    2025-05-22 20:18:56.100  - info: host.raspberrypi64bitbookworm Restart adapter system.adapter.zigbee.0 because enabled
    2025-05-22 20:18:56.100  - warn: host.raspberrypi64bitbookworm Do not restart adapter system.adapter.zigbee.0 because restart loop detected
    
    

    Hallo zusammen,
    vorab bitte ich um ein etwas Nachsicht, da ich auf die 70 zugehe und was
    Linux angeht einfach copy und paste Laie bin.

    Ich betreibe meine Hausautomation mit Iobroker und PVICCU3.
    Ich habe mein System neu aufsetzen müssen (10 Jahre lief alles sehr gut auch mit root rechten) und habe soweit alles wieder am laufen. Bin auf einen PI 4 umgezogen.
    Einzig am verzweifeln bin ich an der Einbindung von meines neuen SONOFF ZigBee 3.0 USB DONGLE PLUS in den Adapter zigbee.

    Nach der Eingabe (siehe Bild)
    ZigbeeJPG.JPG
    bleibt der Adapter auf gelb und die Fehlermeldungen (siehe iob diag) erscheinen.
    Habe schon im Netz alles an Vorschlägen etc. probiert aber ich komme nicht weiter.
    Habe es auch mit einem Conbee2 versucht aber auch das ging nicht.

    Vielleicht liest ja Thomas Braun mit, von dem ich dank seiner Expertise viel gelernt habe :+1:
    Ich glaube das Problem hängt mit der Installation von PVICCU3 zusammen.

    Auf github (https://github.com/alexreinert/piVCCU/blob/master/docs/setup/raspberrypi.md)
    musste ich bei der Installation Raspbarry PI unter Punkt 8 die alte Methode zur Netzwerkkonfiguration ändern mit folgenden Befehlen:

    sudo nmcli connection show --active
    sudo apt install bridge-utils
    sudo nmcli connection add ifname br0 type bridge con-name br0
    sudo nmcli connection add type bridge-slave ifname eth0 master br0
    

    Vielleicht wird hier etwas geblockt.

    Ich hoffe Ihr könnt mir helfen.
    Danke im Voraus
    Jupp

    P.S
    Da meine Frau nicht mehr so fit ist, muss ich sagen, das der Alltag mit Alexa und Sprachsteuerung uns das Leben viel einfacher macht.
    Und das ist auch vielleicht mal ein Thema. Wenn mir z.b. mal was passiert und das System
    stürzt ab und nichts geht mehr was dann?
    Ich habe eine Dokumentation mit allen Passwörtern meiner Frau übergeben,
    und einen mir bekannten Ansprechpartner, der sich auskennt, der dann aushelfen muss.
    Das mal zum Nachdenken für die jüngere Generation.

    1 Reply Last reply
    0
    • AsgothianA Offline
      AsgothianA Offline
      Asgothian
      Developer
      wrote on last edited by Asgothian
      #2

      @högi

      • du musst unbedingt die panID anpassen - die ist so nicht gut. (16 stellige zahl, nicht 16 mal D
      • mach bitte folgendes:
        — zigbee Adapter anhalten
        — iobroker log löschen
        — zigbee Adapter starten
        — 120 Sekunden (plus/minus ein paar Sekunden ) warten.
        — log herunter laden
        — das herunter geladene log hier in code-tags posten.

      A.

      ioBroker auf RPi4 - Hardware soweit wie möglich via Zigbee.
      "Shit don't work" ist keine Fehlermeldung, sondern ein Fluch.

      H 1 Reply Last reply
      0
      • AsgothianA Asgothian

        @högi

        • du musst unbedingt die panID anpassen - die ist so nicht gut. (16 stellige zahl, nicht 16 mal D
        • mach bitte folgendes:
          — zigbee Adapter anhalten
          — iobroker log löschen
          — zigbee Adapter starten
          — 120 Sekunden (plus/minus ein paar Sekunden ) warten.
          — log herunter laden
          — das herunter geladene log hier in code-tags posten.

        A.

        H Offline
        H Offline
        Högi
        wrote on last edited by Högi
        #3

        @asgothian
        Hallo,
        hier die Ausgabe vom log.

        2025-05-22 22:05:30.312 - info: host.raspberrypi64bitbookworm instance system.adapter.zigbee.0 in version "2.0.5" started with pid 13269
        2025-05-22 22:05:34.282 - info: zigbee.0 (13269) starting. Version 2.0.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.19.2, js-controller: 7.0.6
        2025-05-22 22:05:34.312 - info: zigbee.0 (13269) init localConfig
        2025-05-22 22:05:34.323 - info: zigbee.0 (13269) --> transmitPower : normal
        2025-05-22 22:05:34.339 - info: zigbee.0 (13269) delete old Backup files. keep only last 10
        2025-05-22 22:05:34.344 - info: zigbee.0 (13269) --- creating device debug ---
        2025-05-22 22:05:34.346 - info: zigbee.0 (13269) Starting Adapter npm ...
        2025-05-22 22:05:34.404 - info: zigbee.0 (13269) Installed Version: iobroker.zigbee@2.0.5 (Converters 23.6.0 Herdsman 3.5.2)
        2025-05-22 22:05:34.406 - info: zigbee.0 (13269) Starting Zigbee-Herdsman
        2025-05-22 22:05:48.281 - info: host.raspberrypi64bitbookworm "system.adapter.zigbee.0" disabled
        2025-05-22 22:05:48.286 - info: host.raspberrypi64bitbookworm stopInstance system.adapter.zigbee.0 (force=false, process=true)
        2025-05-22 22:05:48.294 - info: zigbee.0 (13269) Got terminate signal TERMINATE_YOURSELF
        2025-05-22 22:05:48.298 - info: zigbee.0 (13269) cleaned everything up...
        2025-05-22 22:05:48.299 - info: zigbee.0 (13269) local config saved
        2025-05-22 22:05:48.301 - info: zigbee.0 (13269) Saved local configuration data
        2025-05-22 22:05:48.302 - info: zigbee.0 (13269) terminating
        2025-05-22 22:05:48.304 - info: zigbee.0 (13269) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
        2025-05-22 22:05:48.405 - error: zigbee.0 (13269) Failed to open the network: TypeError: Cannot read properties of undefined (reading 'permitJoin')
        at Controller.permitJoin (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/controller.ts:315:35)
        at ZigbeeController.permitJoin (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:659:33)
        at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:634:24)
        at processTicksAndRejections (node:internal/process/task_queues:95:5)
        at Zigbee.onUnload (/opt/iobroker/node_modules/iobroker.zigbee/main.js:1037:17)
        2025-05-22 22:05:48.416 - info: zigbee.0 (13269) terminating
        2025-05-22 22:05:48.452 - info: host.raspberrypi64bitbookworm stopInstance system.adapter.zigbee.0 send kill signal
        2025-05-22 22:05:48.806 - info: zigbee.0 (13269) terminating
        2025-05-22 22:05:48.982 - info: host.raspberrypi64bitbookworm instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
        2025-05-22 22:12:25.154 - info: admin.0 (687) ==> Connected system.user.admin from ::ffff:192.168.178.102
        2025-05-22 22:17:25.242 - info: admin.0 (687) <== Disconnect system.user.admin from ::ffff:192.168.178.102
        2025-05-22 22:18:55.896 - info: host.raspberrypi64bitbookworm "system.adapter.zigbee.0" enabled
        2025-05-22 22:18:57.325 - info: host.raspberrypi64bitbookworm instance system.adapter.zigbee.0 in version "2.0.5" started with pid 14090
        2025-05-22 22:19:01.371 - info: zigbee.0 (14090) starting. Version 2.0.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.19.2, js-controller: 7.0.6
        2025-05-22 22:19:01.402 - info: zigbee.0 (14090) init localConfig
        2025-05-22 22:19:01.412 - info: zigbee.0 (14090) --> transmitPower : normal
        2025-05-22 22:19:01.429 - info: zigbee.0 (14090) delete old Backup files. keep only last 10
        2025-05-22 22:19:01.433 - info: zigbee.0 (14090) --- creating device debug ---
        2025-05-22 22:19:01.436 - info: zigbee.0 (14090) Starting Adapter npm ...
        2025-05-22 22:19:01.492 - info: zigbee.0 (14090) Installed Version: iobroker.zigbee@2.0.5 (Converters 23.6.0 Herdsman 3.5.2)
        2025-05-22 22:19:01.494 - info: zigbee.0 (14090) Starting Zigbee-Herdsman
        2025-05-22 22:19:24.177 - info: admin.0 (687) ==> Connected system.user.admin from ::ffff:192.168.178.102
        2025-05-22 22:19:24.473 - error: zigbee.0 (14090) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
        2025-05-22 22:19:24.475 - error: zigbee.0 (14090) unhandled promise rejection: Cannot read properties of undefined (reading 'CleanupRequired')
        2025-05-22 22:19:24.804 - error: zigbee.0 (14090) TypeError: Cannot read properties of undefined (reading 'CleanupRequired')
        at Commands.onMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:155:97)
        at Zigbee. (/opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:20:48)
        at Zigbee.emit (node:events:536:35)
        at Zigbee.emit (node:domain:489:12)
        at change (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:10953:34)
        at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:368:37)
        at processImmediate (node:internal/timers:483:21)
        2025-05-22 22:19:24.805 - error: zigbee.0 (14090) Cannot read properties of undefined (reading 'CleanupRequired')
        2025-05-22 22:19:24.865 - info: zigbee.0 (14090) cleaned everything up...
        2025-05-22 22:19:24.866 - info: zigbee.0 (14090) local config saved
        2025-05-22 22:19:24.868 - info: zigbee.0 (14090) Saved local configuration data
        2025-05-22 22:19:24.869 - info: zigbee.0 (14090) terminating
        2025-05-22 22:19:24.873 - warn: zigbee.0 (14090) Terminated (UNCAUGHT_EXCEPTION): Without reason
        2025-05-22 22:19:24.920 - error: zigbee.0 (14090) Failed to open the network: TypeError: Cannot read properties of undefined (reading 'permitJoin')
        at Controller.permitJoin (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/controller.ts:315:35)
        at ZigbeeController.permitJoin (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:659:33)
        at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:634:24)
        at processTicksAndRejections (node:internal/process/task_queues:95:5)
        at Zigbee.onUnload (/opt/iobroker/node_modules/iobroker.zigbee/main.js:1037:17)
        2025-05-22 22:19:24.927 - info: zigbee.0 (14090) terminating
        2025-05-22 22:19:25.007 - info: zigbee.0 (14090) List of port: [{"path":"/dev/ttyUSB0","manufacturer":"ITead","serialNumber":"2e3882639474ef11b58fd08c8fcc3fa0","pnpId":"usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_2e3882639474ef11b58fd08c8fcc3fa0-if00-port0","vendorId":"10c4","productId":"ea60"},{"path":"/dev/ttyS0"}]
        2025-05-22 22:19:25.382 - info: zigbee.0 (14090) terminating
        2025-05-22 22:19:25.562 - error: host.raspberrypi64bitbookworm Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
        2025-05-22 22:19:25.563 - error: host.raspberrypi64bitbookworm Caught by controller[0]: TypeError: Cannot read properties of undefined (reading 'CleanupRequired')
        2025-05-22 22:19:25.563 - error: host.raspberrypi64bitbookworm Caught by controller[0]: at Commands.onMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:155:97)
        2025-05-22 22:19:25.563 - error: host.raspberrypi64bitbookworm Caught by controller[0]: at Zigbee. (/opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:20:48)
        2025-05-22 22:19:25.563 - error: host.raspberrypi64bitbookworm Caught by controller[0]: at Zigbee.emit (node:events:536:35)
        2025-05-22 22:19:25.563 - error: host.raspberrypi64bitbookworm Caught by controller[0]: at Zigbee.emit (node:domain:489:12)
        2025-05-22 22:19:25.563 - error: host.raspberrypi64bitbookworm Caught by controller[0]: at change (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:10953:34)
        2025-05-22 22:19:25.564 - error: host.raspberrypi64bitbookworm Caught by controller[0]: at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:368:37)
        2025-05-22 22:19:25.564 - error: host.raspberrypi64bitbookworm Caught by controller[0]: at processImmediate (node:internal/timers:483:21)
        2025-05-22 22:19:25.564 - error: host.raspberrypi64bitbookworm instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
        2025-05-22 22:19:25.564 - info: host.raspberrypi64bitbookworm Restart adapter system.adapter.zigbee.0 because enabled
        2025-05-22 22:19:56.435 - info: host.raspberrypi64bitbookworm instance system.adapter.zigbee.0 in version "2.0.5" started with pid 14168
        2025-05-22 22:20:00.397 - info: zigbee.0 (14168) starting. Version 2.0.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.19.2, js-controller: 7.0.6
        2025-05-22 22:20:00.428 - info: zigbee.0 (14168) init localConfig
        2025-05-22 22:20:00.441 - info: zigbee.0 (14168) --> transmitPower : normal
        2025-05-22 22:20:00.460 - info: zigbee.0 (14168) delete old Backup files. keep only last 10
        2025-05-22 22:20:00.465 - info: zigbee.0 (14168) --- creating device debug ---
        2025-05-22 22:20:00.467 - info: zigbee.0 (14168) Starting Adapter npm ...
        2025-05-22 22:20:00.542 - info: zigbee.0 (14168) Installed Version: iobroker.zigbee@2.0.5 (Converters 23.6.0 Herdsman 3.5.2)
        2025-05-22 22:20:00.544 - info: zigbee.0 (14168) Starting Zigbee-Herdsman
        2025-05-22 22:20:26.959 - info: zigbee.0 (14168) Unable to obtain herdsman settings
        2025-05-22 22:20:27.179 - error: zigbee.0 (14168) Starting zigbee-herdsman problem : Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
        2025-05-22 22:20:27.181 - error: zigbee.0 (14168) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
        2025-05-22 22:20:27.182 - error: zigbee.0 (14168) unhandled promise rejection: undefined
        2025-05-22 22:20:27.183 - error: zigbee.0 (14168) undefined
        2025-05-22 22:20:27.240 - info: zigbee.0 (14168) cleaned everything up...
        2025-05-22 22:20:27.241 - info: zigbee.0 (14168) local config saved
        2025-05-22 22:20:27.243 - info: zigbee.0 (14168) Saved local configuration data
        2025-05-22 22:20:27.244 - info: zigbee.0 (14168) terminating
        2025-05-22 22:20:27.247 - warn: zigbee.0 (14168) Terminated (UNCAUGHT_EXCEPTION): Without reason
        2025-05-22 22:20:27.256 - error: zigbee.0 (14168) Failed to open the network: TypeError: Cannot read properties of undefined (reading 'permitJoin')
        at Controller.permitJoin (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/controller.ts:315:35)
        at ZigbeeController.permitJoin (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:659:33)
        at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:634:24)
        at processTicksAndRejections (node:internal/process/task_queues:95:5)
        at Zigbee.onUnload (/opt/iobroker/node_modules/iobroker.zigbee/main.js:1037:17)
        2025-05-22 22:20:27.263 - info: zigbee.0 (14168) terminating
        2025-05-22 22:20:27.749 - info: zigbee.0 (14168) terminating
        2025-05-22 22:20:27.965 - error: host.raspberrypi64bitbookworm Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
        2025-05-22 22:20:27.966 - error: host.raspberrypi64bitbookworm Caught by controller[1]: Error herdsman start
        2025-05-22 22:20:27.967 - error: host.raspberrypi64bitbookworm instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
        2025-05-22 22:20:27.967 - info: host.raspberrypi64bitbookworm Restart adapter system.adapter.zigbee.0 because enabled
        2025-05-22 22:20:58.998 - info: host.raspberrypi64bitbookworm instance system.adapter.zigbee.0 in version "2.0.5" started with pid 14246
        2025-05-22 22:20:59.706 - info: admin.0 (687) <== Disconnect system.user.admin from ::ffff:192.168.178.102
        2025-05-22 22:21:03.058 - info: zigbee.0 (14246) starting. Version 2.0.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.19.2, js-controller: 7.0.6
        2025-05-22 22:21:03.090 - info: zigbee.0 (14246) init localConfig
        2025-05-22 22:21:03.100 - info: zigbee.0 (14246) --> transmitPower : normal
        2025-05-22 22:21:03.116 - info: zigbee.0 (14246) delete old Backup files. keep only last 10
        2025-05-22 22:21:03.122 - info: zigbee.0 (14246) --- creating device debug ---
        2025-05-22 22:21:03.123 - info: zigbee.0 (14246) Starting Adapter npm ...
        2025-05-22 22:21:03.181 - info: zigbee.0 (14246) Installed Version: iobroker.zigbee@2.0.5 (Converters 23.6.0 Herdsman 3.5.2)
        2025-05-22 22:21:03.184 - info: zigbee.0 (14246) Starting Zigbee-Herdsman
        2025-05-22 22:21:29.603 - info: zigbee.0 (14246) Unable to obtain herdsman settings
        2025-05-22 22:21:29.785 - error: zigbee.0 (14246) Starting zigbee-herdsman problem : Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
        2025-05-22 22:21:29.788 - error: zigbee.0 (14246) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
        2025-05-22 22:21:29.789 - error: zigbee.0 (14246) unhandled promise rejection: undefined
        2025-05-22 22:21:29.790 - error: zigbee.0 (14246) undefined
        2025-05-22 22:21:29.852 - info: zigbee.0 (14246) cleaned everything up...
        2025-05-22 22:21:29.854 - info: zigbee.0 (14246) local config saved
        2025-05-22 22:21:29.856 - info: zigbee.0 (14246) Saved local configuration data
        2025-05-22 22:21:29.857 - info: zigbee.0 (14246) terminating
        2025-05-22 22:21:29.859 - warn: zigbee.0 (14246) Terminated (UNCAUGHT_EXCEPTION): Without reason
        2025-05-22 22:21:29.867 - error: zigbee.0 (14246) Failed to open the network: TypeError: Cannot read properties of undefined (reading 'permitJoin')
        at Controller.permitJoin (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/controller.ts:315:35)
        at ZigbeeController.permitJoin (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:659:33)
        at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:634:24)
        at processTicksAndRejections (node:internal/process/task_queues:95:5)
        at Zigbee.onUnload (/opt/iobroker/node_modules/iobroker.zigbee/main.js:1037:17)
        2025-05-22 22:21:29.875 - info: zigbee.0 (14246) terminating
        2025-05-22 22:21:30.363 - info: zigbee.0 (14246) terminating
        2025-05-22 22:21:30.561 - error: host.raspberrypi64bitbookworm Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
        2025-05-22 22:21:30.562 - error: host.raspberrypi64bitbookworm Caught by controller[0]: Error herdsman start
        2025-05-22 22:21:30.563 - error: host.raspberrypi64bitbookworm instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
        2025-05-22 22:21:30.563 - info: host.raspberrypi64bitbookworm Restart adapter system.adapter.zigbee.0 because enabled
        2025-05-22 22:21:30.563 - warn: host.raspberrypi64bitbookworm Do not restart adapter system.adapter.zigbee.0 because restart loop detected
        

        Die pan id habe ich geändert: 1437834385923494

        @högi So ich habe jetzt noch folgendes probiert.

        1.) aktuelle Firmware auf den Sonoff coordinator aufgespielt.
        2.) Kpl neu raspberry pi os lite (64bit) Debian Bookworm aufgesetzt und
        Iobroker mit : curl -sSLf https://iobroker.net/install.sh | bash -
        installiert.
        3.) Zigbee Adapter 2.0.5 installiert.
        4.) Coordinator wird unter /dev/serial/by-id angezeigt:
        usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_2e3882639474ef11b58fd08c8fcc3fa0-if00-port0
        5.)Pan ID 16 stellig vergeben.
        6.) Zigbee Adapter Version 2.0.4 probiert.
        7.) USB 0,5 m Verlängerung benutzt
        8.)Raspberry USB 2.0 und USB 3.0 benutzt.

        Alles hat nichts geholfen. Instanz bleibt rot.
        Bin mit meinem Latein am Ende.:anguished:

        AsgothianA 1 Reply Last reply
        0
        • H Högi

          @asgothian
          Hallo,
          hier die Ausgabe vom log.

          2025-05-22 22:05:30.312 - info: host.raspberrypi64bitbookworm instance system.adapter.zigbee.0 in version "2.0.5" started with pid 13269
          2025-05-22 22:05:34.282 - info: zigbee.0 (13269) starting. Version 2.0.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.19.2, js-controller: 7.0.6
          2025-05-22 22:05:34.312 - info: zigbee.0 (13269) init localConfig
          2025-05-22 22:05:34.323 - info: zigbee.0 (13269) --> transmitPower : normal
          2025-05-22 22:05:34.339 - info: zigbee.0 (13269) delete old Backup files. keep only last 10
          2025-05-22 22:05:34.344 - info: zigbee.0 (13269) --- creating device debug ---
          2025-05-22 22:05:34.346 - info: zigbee.0 (13269) Starting Adapter npm ...
          2025-05-22 22:05:34.404 - info: zigbee.0 (13269) Installed Version: iobroker.zigbee@2.0.5 (Converters 23.6.0 Herdsman 3.5.2)
          2025-05-22 22:05:34.406 - info: zigbee.0 (13269) Starting Zigbee-Herdsman
          2025-05-22 22:05:48.281 - info: host.raspberrypi64bitbookworm "system.adapter.zigbee.0" disabled
          2025-05-22 22:05:48.286 - info: host.raspberrypi64bitbookworm stopInstance system.adapter.zigbee.0 (force=false, process=true)
          2025-05-22 22:05:48.294 - info: zigbee.0 (13269) Got terminate signal TERMINATE_YOURSELF
          2025-05-22 22:05:48.298 - info: zigbee.0 (13269) cleaned everything up...
          2025-05-22 22:05:48.299 - info: zigbee.0 (13269) local config saved
          2025-05-22 22:05:48.301 - info: zigbee.0 (13269) Saved local configuration data
          2025-05-22 22:05:48.302 - info: zigbee.0 (13269) terminating
          2025-05-22 22:05:48.304 - info: zigbee.0 (13269) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
          2025-05-22 22:05:48.405 - error: zigbee.0 (13269) Failed to open the network: TypeError: Cannot read properties of undefined (reading 'permitJoin')
          at Controller.permitJoin (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/controller.ts:315:35)
          at ZigbeeController.permitJoin (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:659:33)
          at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:634:24)
          at processTicksAndRejections (node:internal/process/task_queues:95:5)
          at Zigbee.onUnload (/opt/iobroker/node_modules/iobroker.zigbee/main.js:1037:17)
          2025-05-22 22:05:48.416 - info: zigbee.0 (13269) terminating
          2025-05-22 22:05:48.452 - info: host.raspberrypi64bitbookworm stopInstance system.adapter.zigbee.0 send kill signal
          2025-05-22 22:05:48.806 - info: zigbee.0 (13269) terminating
          2025-05-22 22:05:48.982 - info: host.raspberrypi64bitbookworm instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
          2025-05-22 22:12:25.154 - info: admin.0 (687) ==> Connected system.user.admin from ::ffff:192.168.178.102
          2025-05-22 22:17:25.242 - info: admin.0 (687) <== Disconnect system.user.admin from ::ffff:192.168.178.102
          2025-05-22 22:18:55.896 - info: host.raspberrypi64bitbookworm "system.adapter.zigbee.0" enabled
          2025-05-22 22:18:57.325 - info: host.raspberrypi64bitbookworm instance system.adapter.zigbee.0 in version "2.0.5" started with pid 14090
          2025-05-22 22:19:01.371 - info: zigbee.0 (14090) starting. Version 2.0.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.19.2, js-controller: 7.0.6
          2025-05-22 22:19:01.402 - info: zigbee.0 (14090) init localConfig
          2025-05-22 22:19:01.412 - info: zigbee.0 (14090) --> transmitPower : normal
          2025-05-22 22:19:01.429 - info: zigbee.0 (14090) delete old Backup files. keep only last 10
          2025-05-22 22:19:01.433 - info: zigbee.0 (14090) --- creating device debug ---
          2025-05-22 22:19:01.436 - info: zigbee.0 (14090) Starting Adapter npm ...
          2025-05-22 22:19:01.492 - info: zigbee.0 (14090) Installed Version: iobroker.zigbee@2.0.5 (Converters 23.6.0 Herdsman 3.5.2)
          2025-05-22 22:19:01.494 - info: zigbee.0 (14090) Starting Zigbee-Herdsman
          2025-05-22 22:19:24.177 - info: admin.0 (687) ==> Connected system.user.admin from ::ffff:192.168.178.102
          2025-05-22 22:19:24.473 - error: zigbee.0 (14090) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
          2025-05-22 22:19:24.475 - error: zigbee.0 (14090) unhandled promise rejection: Cannot read properties of undefined (reading 'CleanupRequired')
          2025-05-22 22:19:24.804 - error: zigbee.0 (14090) TypeError: Cannot read properties of undefined (reading 'CleanupRequired')
          at Commands.onMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:155:97)
          at Zigbee. (/opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:20:48)
          at Zigbee.emit (node:events:536:35)
          at Zigbee.emit (node:domain:489:12)
          at change (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:10953:34)
          at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:368:37)
          at processImmediate (node:internal/timers:483:21)
          2025-05-22 22:19:24.805 - error: zigbee.0 (14090) Cannot read properties of undefined (reading 'CleanupRequired')
          2025-05-22 22:19:24.865 - info: zigbee.0 (14090) cleaned everything up...
          2025-05-22 22:19:24.866 - info: zigbee.0 (14090) local config saved
          2025-05-22 22:19:24.868 - info: zigbee.0 (14090) Saved local configuration data
          2025-05-22 22:19:24.869 - info: zigbee.0 (14090) terminating
          2025-05-22 22:19:24.873 - warn: zigbee.0 (14090) Terminated (UNCAUGHT_EXCEPTION): Without reason
          2025-05-22 22:19:24.920 - error: zigbee.0 (14090) Failed to open the network: TypeError: Cannot read properties of undefined (reading 'permitJoin')
          at Controller.permitJoin (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/controller.ts:315:35)
          at ZigbeeController.permitJoin (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:659:33)
          at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:634:24)
          at processTicksAndRejections (node:internal/process/task_queues:95:5)
          at Zigbee.onUnload (/opt/iobroker/node_modules/iobroker.zigbee/main.js:1037:17)
          2025-05-22 22:19:24.927 - info: zigbee.0 (14090) terminating
          2025-05-22 22:19:25.007 - info: zigbee.0 (14090) List of port: [{"path":"/dev/ttyUSB0","manufacturer":"ITead","serialNumber":"2e3882639474ef11b58fd08c8fcc3fa0","pnpId":"usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_2e3882639474ef11b58fd08c8fcc3fa0-if00-port0","vendorId":"10c4","productId":"ea60"},{"path":"/dev/ttyS0"}]
          2025-05-22 22:19:25.382 - info: zigbee.0 (14090) terminating
          2025-05-22 22:19:25.562 - error: host.raspberrypi64bitbookworm Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
          2025-05-22 22:19:25.563 - error: host.raspberrypi64bitbookworm Caught by controller[0]: TypeError: Cannot read properties of undefined (reading 'CleanupRequired')
          2025-05-22 22:19:25.563 - error: host.raspberrypi64bitbookworm Caught by controller[0]: at Commands.onMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:155:97)
          2025-05-22 22:19:25.563 - error: host.raspberrypi64bitbookworm Caught by controller[0]: at Zigbee. (/opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:20:48)
          2025-05-22 22:19:25.563 - error: host.raspberrypi64bitbookworm Caught by controller[0]: at Zigbee.emit (node:events:536:35)
          2025-05-22 22:19:25.563 - error: host.raspberrypi64bitbookworm Caught by controller[0]: at Zigbee.emit (node:domain:489:12)
          2025-05-22 22:19:25.563 - error: host.raspberrypi64bitbookworm Caught by controller[0]: at change (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:10953:34)
          2025-05-22 22:19:25.564 - error: host.raspberrypi64bitbookworm Caught by controller[0]: at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:368:37)
          2025-05-22 22:19:25.564 - error: host.raspberrypi64bitbookworm Caught by controller[0]: at processImmediate (node:internal/timers:483:21)
          2025-05-22 22:19:25.564 - error: host.raspberrypi64bitbookworm instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
          2025-05-22 22:19:25.564 - info: host.raspberrypi64bitbookworm Restart adapter system.adapter.zigbee.0 because enabled
          2025-05-22 22:19:56.435 - info: host.raspberrypi64bitbookworm instance system.adapter.zigbee.0 in version "2.0.5" started with pid 14168
          2025-05-22 22:20:00.397 - info: zigbee.0 (14168) starting. Version 2.0.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.19.2, js-controller: 7.0.6
          2025-05-22 22:20:00.428 - info: zigbee.0 (14168) init localConfig
          2025-05-22 22:20:00.441 - info: zigbee.0 (14168) --> transmitPower : normal
          2025-05-22 22:20:00.460 - info: zigbee.0 (14168) delete old Backup files. keep only last 10
          2025-05-22 22:20:00.465 - info: zigbee.0 (14168) --- creating device debug ---
          2025-05-22 22:20:00.467 - info: zigbee.0 (14168) Starting Adapter npm ...
          2025-05-22 22:20:00.542 - info: zigbee.0 (14168) Installed Version: iobroker.zigbee@2.0.5 (Converters 23.6.0 Herdsman 3.5.2)
          2025-05-22 22:20:00.544 - info: zigbee.0 (14168) Starting Zigbee-Herdsman
          2025-05-22 22:20:26.959 - info: zigbee.0 (14168) Unable to obtain herdsman settings
          2025-05-22 22:20:27.179 - error: zigbee.0 (14168) Starting zigbee-herdsman problem : Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
          2025-05-22 22:20:27.181 - error: zigbee.0 (14168) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
          2025-05-22 22:20:27.182 - error: zigbee.0 (14168) unhandled promise rejection: undefined
          2025-05-22 22:20:27.183 - error: zigbee.0 (14168) undefined
          2025-05-22 22:20:27.240 - info: zigbee.0 (14168) cleaned everything up...
          2025-05-22 22:20:27.241 - info: zigbee.0 (14168) local config saved
          2025-05-22 22:20:27.243 - info: zigbee.0 (14168) Saved local configuration data
          2025-05-22 22:20:27.244 - info: zigbee.0 (14168) terminating
          2025-05-22 22:20:27.247 - warn: zigbee.0 (14168) Terminated (UNCAUGHT_EXCEPTION): Without reason
          2025-05-22 22:20:27.256 - error: zigbee.0 (14168) Failed to open the network: TypeError: Cannot read properties of undefined (reading 'permitJoin')
          at Controller.permitJoin (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/controller.ts:315:35)
          at ZigbeeController.permitJoin (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:659:33)
          at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:634:24)
          at processTicksAndRejections (node:internal/process/task_queues:95:5)
          at Zigbee.onUnload (/opt/iobroker/node_modules/iobroker.zigbee/main.js:1037:17)
          2025-05-22 22:20:27.263 - info: zigbee.0 (14168) terminating
          2025-05-22 22:20:27.749 - info: zigbee.0 (14168) terminating
          2025-05-22 22:20:27.965 - error: host.raspberrypi64bitbookworm Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
          2025-05-22 22:20:27.966 - error: host.raspberrypi64bitbookworm Caught by controller[1]: Error herdsman start
          2025-05-22 22:20:27.967 - error: host.raspberrypi64bitbookworm instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
          2025-05-22 22:20:27.967 - info: host.raspberrypi64bitbookworm Restart adapter system.adapter.zigbee.0 because enabled
          2025-05-22 22:20:58.998 - info: host.raspberrypi64bitbookworm instance system.adapter.zigbee.0 in version "2.0.5" started with pid 14246
          2025-05-22 22:20:59.706 - info: admin.0 (687) <== Disconnect system.user.admin from ::ffff:192.168.178.102
          2025-05-22 22:21:03.058 - info: zigbee.0 (14246) starting. Version 2.0.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.19.2, js-controller: 7.0.6
          2025-05-22 22:21:03.090 - info: zigbee.0 (14246) init localConfig
          2025-05-22 22:21:03.100 - info: zigbee.0 (14246) --> transmitPower : normal
          2025-05-22 22:21:03.116 - info: zigbee.0 (14246) delete old Backup files. keep only last 10
          2025-05-22 22:21:03.122 - info: zigbee.0 (14246) --- creating device debug ---
          2025-05-22 22:21:03.123 - info: zigbee.0 (14246) Starting Adapter npm ...
          2025-05-22 22:21:03.181 - info: zigbee.0 (14246) Installed Version: iobroker.zigbee@2.0.5 (Converters 23.6.0 Herdsman 3.5.2)
          2025-05-22 22:21:03.184 - info: zigbee.0 (14246) Starting Zigbee-Herdsman
          2025-05-22 22:21:29.603 - info: zigbee.0 (14246) Unable to obtain herdsman settings
          2025-05-22 22:21:29.785 - error: zigbee.0 (14246) Starting zigbee-herdsman problem : Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
          2025-05-22 22:21:29.788 - error: zigbee.0 (14246) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
          2025-05-22 22:21:29.789 - error: zigbee.0 (14246) unhandled promise rejection: undefined
          2025-05-22 22:21:29.790 - error: zigbee.0 (14246) undefined
          2025-05-22 22:21:29.852 - info: zigbee.0 (14246) cleaned everything up...
          2025-05-22 22:21:29.854 - info: zigbee.0 (14246) local config saved
          2025-05-22 22:21:29.856 - info: zigbee.0 (14246) Saved local configuration data
          2025-05-22 22:21:29.857 - info: zigbee.0 (14246) terminating
          2025-05-22 22:21:29.859 - warn: zigbee.0 (14246) Terminated (UNCAUGHT_EXCEPTION): Without reason
          2025-05-22 22:21:29.867 - error: zigbee.0 (14246) Failed to open the network: TypeError: Cannot read properties of undefined (reading 'permitJoin')
          at Controller.permitJoin (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/controller.ts:315:35)
          at ZigbeeController.permitJoin (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:659:33)
          at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:634:24)
          at processTicksAndRejections (node:internal/process/task_queues:95:5)
          at Zigbee.onUnload (/opt/iobroker/node_modules/iobroker.zigbee/main.js:1037:17)
          2025-05-22 22:21:29.875 - info: zigbee.0 (14246) terminating
          2025-05-22 22:21:30.363 - info: zigbee.0 (14246) terminating
          2025-05-22 22:21:30.561 - error: host.raspberrypi64bitbookworm Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
          2025-05-22 22:21:30.562 - error: host.raspberrypi64bitbookworm Caught by controller[0]: Error herdsman start
          2025-05-22 22:21:30.563 - error: host.raspberrypi64bitbookworm instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
          2025-05-22 22:21:30.563 - info: host.raspberrypi64bitbookworm Restart adapter system.adapter.zigbee.0 because enabled
          2025-05-22 22:21:30.563 - warn: host.raspberrypi64bitbookworm Do not restart adapter system.adapter.zigbee.0 because restart loop detected
          

          Die pan id habe ich geändert: 1437834385923494

          @högi So ich habe jetzt noch folgendes probiert.

          1.) aktuelle Firmware auf den Sonoff coordinator aufgespielt.
          2.) Kpl neu raspberry pi os lite (64bit) Debian Bookworm aufgesetzt und
          Iobroker mit : curl -sSLf https://iobroker.net/install.sh | bash -
          installiert.
          3.) Zigbee Adapter 2.0.5 installiert.
          4.) Coordinator wird unter /dev/serial/by-id angezeigt:
          usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_2e3882639474ef11b58fd08c8fcc3fa0-if00-port0
          5.)Pan ID 16 stellig vergeben.
          6.) Zigbee Adapter Version 2.0.4 probiert.
          7.) USB 0,5 m Verlängerung benutzt
          8.)Raspberry USB 2.0 und USB 3.0 benutzt.

          Alles hat nichts geholfen. Instanz bleibt rot.
          Bin mit meinem Latein am Ende.:anguished:

          AsgothianA Offline
          AsgothianA Offline
          Asgothian
          Developer
          wrote on last edited by
          #4

          @högi du musst schon systematisch vorgehen. Bei dem geposteten Log ist dieser Eintrag entscheidend:

          2025-05-22 22:21:29.785 - error: zigbee.0 (14246) Starting zigbee-herdsman problem : Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
          

          Dieses bedeutet das

          • die serielle Schnittstelle geöffnet wurde (erfolgreich)
          • keine Kommunikation zur Firmware entsteht.

          Genau das musst du dir bei den einzelnen Versuchen anschauen.

          Bevor du da aber loslegst, bitte noch einmal verifizieren :

          Bitte noch einmal verifizieren - hast du einen Sonoff Dongle P oder Dongle E (steht auf dem Gerät selber drauf.

          A.

          ioBroker auf RPi4 - Hardware soweit wie möglich via Zigbee.
          "Shit don't work" ist keine Fehlermeldung, sondern ein Fluch.

          H 1 Reply Last reply
          0
          • AsgothianA Asgothian

            @högi du musst schon systematisch vorgehen. Bei dem geposteten Log ist dieser Eintrag entscheidend:

            2025-05-22 22:21:29.785 - error: zigbee.0 (14246) Starting zigbee-herdsman problem : Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
            

            Dieses bedeutet das

            • die serielle Schnittstelle geöffnet wurde (erfolgreich)
            • keine Kommunikation zur Firmware entsteht.

            Genau das musst du dir bei den einzelnen Versuchen anschauen.

            Bevor du da aber loslegst, bitte noch einmal verifizieren :

            Bitte noch einmal verifizieren - hast du einen Sonoff Dongle P oder Dongle E (steht auf dem Gerät selber drauf.

            A.

            H Offline
            H Offline
            Högi
            wrote on last edited by
            #5

            @asgothian Ich habe den Sonoff Dongle P

            arteckA 1 Reply Last reply
            0
            • H Högi

              @asgothian Ich habe den Sonoff Dongle P

              arteckA Offline
              arteckA Offline
              arteck
              Developer Most Active
              wrote on last edited by
              #6

              @högi sagte in SONOFF ZigBee 3.0 wird nicht in Iobroker Zigbee eingebunden:

              @asgothian Ich habe den Sonoff Dongle P

              und welche Firmware hast du da aufgespielt.. zeigmal den link

              zigbee hab ich, zwave auch, nuc's genauso und HA auch

              H 1 Reply Last reply
              0
              • arteckA arteck

                @högi sagte in SONOFF ZigBee 3.0 wird nicht in Iobroker Zigbee eingebunden:

                @asgothian Ich habe den Sonoff Dongle P

                und welche Firmware hast du da aufgespielt.. zeigmal den link

                H Offline
                H Offline
                Högi
                wrote on last edited by Högi
                #7

                @arteck
                Über diesen link:https://github.com/Koenkk/Z-Stack-firmware/blob/master/coordinator/Z-Stack_3.x.0/bin/CC1352P2_CC2652P_launchpad_coordinator_20240710.zip

                Und nach dieser Anleitung die Firmware aufgespielt:
                https://haus-automatisierung.com/hardware/sonoff/2022/01/11/sonoff-zigbee-usb-dongle-plus.html

                1 Reply Last reply
                0
                • W Offline
                  W Offline
                  Walter Weiss
                  wrote on last edited by
                  #8

                  @Högi
                  das der Zigbee-Stick in Verbindung mit der pivccu3 nicht gefunden wurde, hat ich auch schon.
                  Bei mir hat der CUx-Daemon von der pivccu3 die USB-Schnittstelle für den Zigbee-Stick blockiert.
                  Dies kann man verhindern, wenn man in der Pivccu3-Oberfläche in der Systemsteuerung unter CUx-Daemon das Setup anwählt und dort am Ende folgenden Eintrag ergänzt:

                  TTYASSIGN=ttyACM0:NC

                  und das Setup dann speichert.
                  Danach alles neu starten.
                  Ich hoffe es hilft.

                  H 1 Reply Last reply
                  0
                  • W Walter Weiss

                    @Högi
                    das der Zigbee-Stick in Verbindung mit der pivccu3 nicht gefunden wurde, hat ich auch schon.
                    Bei mir hat der CUx-Daemon von der pivccu3 die USB-Schnittstelle für den Zigbee-Stick blockiert.
                    Dies kann man verhindern, wenn man in der Pivccu3-Oberfläche in der Systemsteuerung unter CUx-Daemon das Setup anwählt und dort am Ende folgenden Eintrag ergänzt:

                    TTYASSIGN=ttyACM0:NC

                    und das Setup dann speichert.
                    Danach alles neu starten.
                    Ich hoffe es hilft.

                    H Offline
                    H Offline
                    Högi
                    wrote on last edited by
                    #9

                    @walter-weiss Ich habe das auch probiert und es hat sich nichts geändert.
                    Hatte ja mal testweise System nur mit Iobroker aufgesetzt und der Stick ließ sich
                    auch nicht einbinden.
                    Ich habe den Stick über Amazon gekauft und in den Rezessionen gelesen, das
                    auch defekte Sticks auch ausgeliefert wurden.
                    Bekomme Montag einen neuen Stick.
                    Dann bin ich gespannt.

                    H 1 Reply Last reply
                    0
                    • H Högi

                      @walter-weiss Ich habe das auch probiert und es hat sich nichts geändert.
                      Hatte ja mal testweise System nur mit Iobroker aufgesetzt und der Stick ließ sich
                      auch nicht einbinden.
                      Ich habe den Stick über Amazon gekauft und in den Rezessionen gelesen, das
                      auch defekte Sticks auch ausgeliefert wurden.
                      Bekomme Montag einen neuen Stick.
                      Dann bin ich gespannt.

                      H Offline
                      H Offline
                      Högi
                      wrote on last edited by
                      #10

                      @högi
                      So Problem gelöst und danke an Walter Weiss.
                      Das mit dem CUx-Daemon von der pivccu3 hat mich zur Lösung geführt.
                      Aber zuvor, der erste Sonoff coordinator war wirklich kaputt.

                      Nach dem ich den neuen Sonoff Stick in die Zigbee Instanz einbinden wollte war die Enttäuschung groß und ich wollte schon allen hinschmeißen.

                      Als ich aber den CUx-Daemon von der pivccu3 gestoppt habe, siehe da
                      den Zigbee Adapter wurde grün.

                      Danach habe ich TTYASSIGN=ttyACM0:NC im CUx-Daemon eingetragen
                      aber das hat auch nicht funktioniert.
                      Danach TTYASSIGN=ttyttyUSB0 :NC eingetragen und alles läuft reibungslos.
                      Mein Gott schwere Geburt

                      Danke an Alle

                      W 1 Reply Last reply
                      0
                      • H Högi

                        @högi
                        So Problem gelöst und danke an Walter Weiss.
                        Das mit dem CUx-Daemon von der pivccu3 hat mich zur Lösung geführt.
                        Aber zuvor, der erste Sonoff coordinator war wirklich kaputt.

                        Nach dem ich den neuen Sonoff Stick in die Zigbee Instanz einbinden wollte war die Enttäuschung groß und ich wollte schon allen hinschmeißen.

                        Als ich aber den CUx-Daemon von der pivccu3 gestoppt habe, siehe da
                        den Zigbee Adapter wurde grün.

                        Danach habe ich TTYASSIGN=ttyACM0:NC im CUx-Daemon eingetragen
                        aber das hat auch nicht funktioniert.
                        Danach TTYASSIGN=ttyttyUSB0 :NC eingetragen und alles läuft reibungslos.
                        Mein Gott schwere Geburt

                        Danke an Alle

                        W Offline
                        W Offline
                        Walter Weiss
                        wrote on last edited by
                        #11

                        @högi
                        Entschuldigung, ich hätte noch darauf hinweisen sollen, dass auf unterschiedlichen Systemen die USB-Schnittstellen unterschiedlich benannt werden. ich poste nicht so oft. Aber wieder was dazugelernt. Aber schön dass es geklappt hat.

                        1 Reply Last reply
                        0
                        Reply
                        • Reply as topic
                        Log in to reply
                        • Oldest to Newest
                        • Newest to Oldest
                        • Most Votes


                        Support us

                        ioBroker
                        Community Adapters
                        Donate
                        FAQ Cloud / IOT
                        HowTo: Node.js-Update
                        HowTo: Backup/Restore
                        Downloads
                        BLOG

                        867

                        Online

                        32.4k

                        Users

                        81.5k

                        Topics

                        1.3m

                        Posts
                        Community
                        Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                        ioBroker Community 2014-2025
                        logo
                        • Login

                        • Don't have an account? Register

                        • Login or register to search.
                        • First post
                          Last post
                        0
                        • Home
                        • Recent
                        • Tags
                        • Unread 0
                        • Categories
                        • Unreplied
                        • Popular
                        • GitHub
                        • Docu
                        • Hilfe