Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Einsteigerfragen
    4. Installation
    5. Zigbee.0: You need save and run adapter before pairing!

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    Zigbee.0: You need save and run adapter before pairing!

    This topic has been deleted. Only users with topic management privileges can see it.
    • N
      nilli @Thomas Braun last edited by nilli

      @thomas-braun

      leider nichts auffälliges ...

      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-SMLIGHT_SMLIGHT_SLZB-07p7_9c66d41ef372ed1189a81df3fdf7b791-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.0
      Extended Pan ID:
      grep: /opt/iobroker/iobroker-data/zigbee_0/nvbackup.json: No such file or directory
      Pan ID:
      grep: /opt/iobroker/iobroker-data/zigbee_0/nvbackup.json: No such file or directory
      /home/iobroker/.diag.sh: line 699: printf: 0x: invalid hex number
      0
      Channel:
      grep: /opt/iobroker/iobroker-data/zigbee_0/nvbackup.json: No such file or directory
      Network Key:
      grep: /opt/iobroker/iobroker-data/zigbee_0/nvbackup.json: No such file or directory
      
      Adapter State
      + system.adapter.zigbee.0                 : zigbee                : raspi5                                   -  enabled, port: /dev/serial/by-id/usb-SMLIGHT_SMLIGHT_SLZB-07p7_9c66d41ef372ed1189a81df3fdf7b791-if00-port0
      
      Enabled adapters with bindings
      + system.adapter.zigbee.0                 : zigbee                : raspi5                                   -  enabled, port: /dev/serial/by-id/usb-SMLIGHT_SMLIGHT_SLZB-07p7_9c66d41ef372ed1189a81df3fdf7b791-if00-port0
      
      
      ```bash
      Script v.2025-02-23
      
      *** BASE SYSTEM ***
       Static hostname: raspi5
             Icon name: computer
      Operating System: Debian GNU/Linux 12 (bookworm)
                Kernel: Linux 6.6.74+rpt-rpi-2712
          Architecture: arm64
      OS is similar to: 
      
      Model		: Raspberry Pi 5 Model B Rev 1.0
      Docker          : false
      Virtualization  : none
      Kernel          : aarch64
      Userland        : 64 bit
      
      Systemuptime and Load:
       19:16:26 up 1 day, 11:01,  2 users,  load average: 113.00, 112.51, 111.72
      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: Wed 2025-03-19 19:16:27 CET
                 Universal time: Wed 2025-03-19 18:16:27 UTC
                       RTC time: Wed 2025-03-19 18:16:27
                      Time zone: Europe/Berlin (CET, +0100)
      System clock synchronized: yes
                    NTP service: active
                RTC in local TZ: no
      
      *** Users and Groups ***
      User that called 'iob diag':
      nils
      HOME=/home/nils
      GROUPS=nils 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:            2.1G        1.5G        163M        425K        557M        651M
      Swap:           536M        536M        573K
      Total:          2.6G        2.0G        163M
      
      Active iob-Instances: 	22
      
               2009 M total memory
               1387 M used memory
                754 M active memory
                838 M inactive memory
                155 M free memory
                 87 M buffer memory
                443 M swap cache
                511 M total swap
                511 M used swap
                  0 M free swap
      
      *** top - Table Of Processes  ***
      top - 19:16:27 up 1 day, 11:01,  2 users,  load average: 113.00, 112.51, 111.72
      Tasks: 293 total,   1 running, 292 sleeping,   0 stopped,   0 zombie
      %Cpu(s):  0.0 us,  0.0 sy,  0.0 ni, 66.7 id, 33.3 wa,  0.0 hi,  0.0 si,  0.0 st 
      MiB Mem :   2009.0 total,    155.0 free,   1387.7 used,    531.4 buff/cache     
      MiB Swap:    512.0 total,      0.5 free,    511.4 used.    621.3 avail Mem 
      
      *** FAILED SERVICES ***
      
        UNIT LOAD ACTIVE SUB DESCRIPTION
      0 loaded units listed.
      
      
      *** DMESG CRITICAL ERRORS ***
      15 CRITICAL ERRORS DETECTED! 
      Check 'sudo dmesg --level=emerg,alert,crit -T' for details
      
      *** FILESYSTEM ***
      Filesystem     Type      Size  Used Avail Use% Mounted on
      udev           devtmpfs  967M     0  967M   0% /dev
      tmpfs          tmpfs     201M  5.2M  196M   3% /run
      /dev/mmcblk0p2 ext4       59G  9.7G   46G  18% /
      tmpfs          tmpfs    1005M     0 1005M   0% /dev/shm
      tmpfs          tmpfs     5.0M   48K  5.0M   1% /run/lock
      /dev/mmcblk0p1 vfat      510M   55M  456M  11% /boot/firmware
      tmpfs          tmpfs     201M     0  201M   0% /run/user/1000
      
      Messages concerning ext4 filesystem in dmesg:
      [Tue Mar 18 08:14:35 2025] Kernel command line: reboot=w coherent_pool=1M 8250.nr_uarts=1 pci=pcie_bus_safe cgroup_disable=memory numa_policy=interleave  smsc95xx.macaddr=2C:CF:67:7A:6F:0D vc_mem.mem_base=0x3fc00000 vc_mem.mem_size=0x40000000  console=ttyAMA10,115200 console=tty1 root=PARTUUID=a7b4f037-02 rootfstype=ext4 fsck.repair=yes rootwait cfg80211.ieee80211_regdom=DE
      [Tue Mar 18 08:14:38 2025] EXT4-fs (mmcblk0p2): mounted filesystem ce208fd3-38a8-424a-87a2-cd44114eb820 ro with ordered data mode. Quota mode: none.
      [Tue Mar 18 08:14:39 2025] EXT4-fs (mmcblk0p2): re-mounted ce208fd3-38a8-424a-87a2-cd44114eb820 r/w. Quota mode: none.
      
      Show mounted filesystems:
      TARGET           SOURCE         FSTYPE OPTIONS
      /                /dev/mmcblk0p2 ext4   rw,noatime,commit=600
      `-/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.1G	/var/
      206M	/var/cache
      200M	/var/cache/apt
      174M	/var/lib
      135M	/var/lib/apt/lists
      
      Archived and active journals take up 133.0M in the file system.
      
      /opt/iobroker/backups:
      19M	/opt/iobroker/backups/
      
      /opt/iobroker/iobroker-data:
      1.4G	/opt/iobroker/iobroker-data/
      1.3G	/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
      26M	/opt/iobroker/iobroker-data/files/echarts/static/js/main.41cee985.js.map
      26M	/opt/iobroker/iobroker-data/files/echarts.admin/chart/static/js/main.41cee985.js.map
      24M	/opt/iobroker/iobroker-data/files/web.admin/static/js/main.135279a0.js.map
      24M	/opt/iobroker/iobroker-data/files/vis-2/static/js/main.f305bc29.js.map
      
      USB-Devices by-id:
      USB-Sticks -  Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id':
      
      /dev/serial/by-id/usb-SMLIGHT_SMLIGHT_SLZB-07p7_9c66d41ef372ed1189a81df3fdf7b791-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.0
      Extended Pan ID:
      grep: /opt/iobroker/iobroker-data/zigbee_0/nvbackup.json: No such file or directory
      Pan ID:
      grep: /opt/iobroker/iobroker-data/zigbee_0/nvbackup.json: No such file or directory
      /home/iobroker/.diag.sh: line 699: printf: 0x: invalid hex number
      0
      Channel:
      grep: /opt/iobroker/iobroker-data/zigbee_0/nvbackup.json: No such file or directory
      Network Key:
      grep: /opt/iobroker/iobroker-data/zigbee_0/nvbackup.json: No such file or directory
      
      *** NodeJS-Installation ***
      
      /usr/bin/nodejs 	v20.19.0
      /usr/bin/node 		v20.19.0
      /usr/bin/npm 		10.8.2
      /usr/bin/npx 		10.8.2
      /usr/bin/corepack 	0.31.0
      
      nodejs:
        Installed: 20.19.0-1nodesource1
        Candidate: 20.19.0-1nodesource1
        Version table:
       *** 20.19.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
              100 /var/lib/dpkg/status
           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:
      raspi5              raspi5 (version: 7.0.6, hostname: raspi5        , alive, uptime: 114649)
      
      Core adapters versions
      js-controller: 	7.0.6
      admin: 		7.4.10
      javascript: 	8.8.3
      
      nodejs modules from github: 	0
      
      Adapter State
      + system.adapter.admin.0                  : admin                 : raspi5                                   -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
      + system.adapter.backitup.0               : backitup              : raspi5                                   -  enabled
        system.adapter.cloud.0                  : cloud                 : raspi5                                   - disabled
      + system.adapter.discovery.0              : discovery             : raspi5                                   -  enabled
      + system.adapter.echarts.0                : echarts               : raspi5                                   -  enabled
      + system.adapter.email.0                  : email                 : raspi5                                   -  enabled
      + system.adapter.fritzdect.0              : fritzdect             : raspi5                                   -  enabled
      + system.adapter.history.0                : history               : raspi5                                   -  enabled
        system.adapter.iot.0                    : iot                   : raspi5                                   - disabled
      + system.adapter.iqontrol.0               : iqontrol              : raspi5                                   -  enabled
      + system.adapter.jarvis.0                 : jarvis                : raspi5                                   -  enabled, port: 8082, bind: 0.0.0.0, run as: admin
      + system.adapter.javascript.0             : javascript            : raspi5                                   -  enabled
      + system.adapter.maxcube.0                : maxcube               : raspi5                                   -  enabled, port: 62910, bind: 0.0.0.0
      + system.adapter.node-red.0               : node-red              : raspi5                                   -  enabled, port: 1880, bind: 0.0.0.0
      + system.adapter.notification-manager.0   : notification-manager  : raspi5                                   -  enabled
        system.adapter.ping.0                   : ping                  : raspi5                                   - disabled
      + system.adapter.rpi2.0                   : rpi2                  : raspi5                                   -  enabled
      + system.adapter.scenes.0                 : scenes                : raspi5                                   -  enabled
      + system.adapter.signal-cmb.0             : signal-cmb            : raspi5                                   -  enabled
      + system.adapter.sql.0                    : sql                   : raspi5                                   -  enabled
      + system.adapter.tr-064.0                 : tr-064                : raspi5                                   -  enabled
      + system.adapter.vis-2.0                  : vis-2                 : raspi5                                   -  enabled
        system.adapter.weatherunderground.0     : weatherunderground    : raspi5                                   - disabled
      + system.adapter.web.0                    : web                   : raspi5                                   -  enabled, port: 8082, bind: 0.0.0.0, run as: admin
      + system.adapter.zigbee.0                 : zigbee                : raspi5                                   -  enabled, port: /dev/serial/by-id/usb-SMLIGHT_SMLIGHT_SLZB-07p7_9c66d41ef372ed1189a81df3fdf7b791-if00-port0
      
      + instance is alive
      
      Enabled adapters with bindings
      + system.adapter.admin.0                  : admin                 : raspi5                                   -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
      + system.adapter.jarvis.0                 : jarvis                : raspi5                                   -  enabled, port: 8082, bind: 0.0.0.0, run as: admin
      + system.adapter.maxcube.0                : maxcube               : raspi5                                   -  enabled, port: 62910, bind: 0.0.0.0
      + system.adapter.node-red.0               : node-red              : raspi5                                   -  enabled, port: 1880, bind: 0.0.0.0
      + system.adapter.web.0                    : web                   : raspi5                                   -  enabled, port: 8082, bind: 0.0.0.0, run as: admin
      + system.adapter.zigbee.0                 : zigbee                : raspi5                                   -  enabled, port: /dev/serial/by-id/usb-SMLIGHT_SMLIGHT_SLZB-07p7_9c66d41ef372ed1189a81df3fdf7b791-if00-port0
      
      ioBroker-Repositories
      ┌─────────┬──────────┬─────────────────────────────────────────────────────────┬──────────────┐
      │ (index) │ name     │ url                                                     │ auto upgrade │
      ├─────────┼──────────┼─────────────────────────────────────────────────────────┼──────────────┤
      │ 0       │ 'stable' │ 'http://download.iobroker.net/sources-dist.json'        │ true         │
      │ 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.4.10   , installed 7.4.10
      Adapter    "backitup"     : 3.0.31   , installed 3.0.31
      Adapter    "cloud"        : 5.0.1    , installed 5.0.1
      Adapter    "discovery"    : 5.0.0    , installed 5.0.0
      Adapter    "echarts"      : 1.9.2    , installed 1.9.2
      Adapter    "email"        : 1.3.1    , installed 1.3.1
      Adapter    "fritzdect"    : 2.5.11   , installed 2.5.11
      Adapter    "history"      : 3.0.1    , installed 3.0.1
      Adapter    "iot"          : 3.3.0    , installed 3.3.0
      Adapter    "iqontrol"     : 3.0.0    , installed 3.0.0
      Adapter    "jarvis"       : 3.1.8    , installed 3.1.8
      Adapter    "javascript"   : 8.8.3    , installed 8.8.3
      Controller "js-controller": 7.0.6    , installed 7.0.6
      Adapter    "maxcube"      : 1.0.4    , installed 1.0.4
      Adapter    "node-red"     : 5.2.1    , installed 5.2.1
      Adapter    "notification-manager": 1.2.1, installed 1.2.1
      Adapter    "ping"         : 1.6.2    , installed 1.6.2
      Adapter    "rpi2"         : 2.3.1    , installed 2.3.1
      Adapter    "scenes"       : 3.2.3    , installed 3.2.3
      Adapter    "signal-cmb"   : 0.3.0    , installed 0.3.0
      Adapter    "simple-api"   : 2.8.0    , installed 2.8.0
      Adapter    "socketio"     : 6.7.1    , installed 6.7.1
      Adapter    "sql"          : 3.0.1    , installed 3.0.1
      Adapter    "tr-064"       : 4.3.0    , installed 4.3.0
      Adapter    "vis-2"        : 2.9.64   , installed 2.9.64
      Adapter    "weatherunderground": 3.7.0, installed 3.7.0
      Adapter    "web"          : 6.2.5    , installed 6.2.5
      Adapter    "ws"           : 2.6.2    , installed 2.6.2
      Adapter    "zigbee"       : 1.10.14  , installed 1.10.14
      
      Objects and States
      Please stand by - This may take a while
      Objects: 	1841
      States: 	937
      
      *** OS-Repositories and Updates ***
      Hit:1 http://deb.debian.org/debian bookworm InRelease
      Hit:2 http://archive.raspberrypi.com/debian bookworm InRelease
      Hit:3 http://deb.debian.org/debian-security bookworm-security InRelease
      Hit:4 http://deb.debian.org/debian bookworm-updates InRelease
      Hit:5 https://deb.nodesource.com/node_20.x nodistro InRelease
      Hit:6 https://packages.adoptium.net/artifactory/deb bookworm InRelease
      Reading package lists...
      Pending Updates: 12
      
      *** Listening Ports ***
      Active Internet connections (only servers)
      Proto Recv-Q Send-Q Local Address           Foreign Address         State       User       Inode      PID/Program name    
      tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      0          4944       675/sshd: /usr/sbin 
      tcp        0      0 127.0.0.1:9000          0.0.0.0:*               LISTEN      1001       88612      21571/iobroker.js-c 
      tcp        0      0 127.0.0.1:9001          0.0.0.0:*               LISTEN      1001       88607      21571/iobroker.js-c 
      tcp        0      0 0.0.0.0:8400            0.0.0.0:*               LISTEN      1001       90865      22057/io.jarvis.0   
      tcp        0      0 0.0.0.0:1880            0.0.0.0:*               LISTEN      1001       90518      21746/node-red      
      tcp6       0      0 :::22                   :::*                    LISTEN      0          4946       675/sshd: /usr/sbin 
      tcp6       0      0 :::8081                 :::*                    LISTEN      1001       87450      21591/io.admin.0    
      tcp6       0      0 :::8082                 :::*                    LISTEN      1001       89048      21978/io.web.0      
      udp        0      0 192.168.2.87:5353       0.0.0.0:*                           1001       87961      22014/io.tr-064.0   
      udp        0      0 0.0.0.0:5353            0.0.0.0:*                           104        4799       541/avahi-daemon: r 
      udp        0      0 0.0.0.0:39307           0.0.0.0:*                           104        4801       541/avahi-daemon: r 
      udp6       0      0 :::5353                 :::*                                104        4800       541/avahi-daemon: r 
      udp6       0      0 fe80::cfaa:2ac1:4ed:546 :::*                                0          372348     618/NetworkManager  
      udp6       0      0 :::41901                :::*                                104        4802       541/avahi-daemon: r 
      
      *** Log File - Last 25 Lines ***
      
      2025-03-19 19:15:51.328  - debug: fritzdect.0 (22085) polling! fritzdect is alive with 300 s
      2025-03-19 19:15:51.329  - debug: fritzdect.0 (22085) __________________________
      2025-03-19 19:15:51.329  - debug: fritzdect.0 (22085) updating Devices / Groups 
      2025-03-19 19:15:53.097  - debug: fritzdect.0 (22085) devices
      
      2025-03-19 19:15:53.097  - debug: fritzdect.0 (22085) [{"identifier":"08761 0147624","id":"16","functionbitmask":"35456","fwversion":"04.27","manufacturer":"AVM","productname":"FRITZ!Smart Energy 200","present":"0","txbusy":"0","name":"FRITZ!DECT 200 #1","switch":{"state":"","mode":"","lock":"","devicelock":""},"simpleonoff":{"state":""},"powermeter":{"voltage":"","power":"","energy":""}}]
      2025-03-19 19:15:53.097  - debug: fritzdect.0 (22085) update Devices 1
      2025-03-19 19:15:53.097  - debug: fritzdect.0 (22085) _____________________________________________
      2025-03-19 19:15:53.097  - debug: fritzdect.0 (22085) updating Device FRITZ!DECT 200 #1
      2025-03-19 19:15:53.101  - silly: fritzdect.0 (22085) States user redis pmessage fritzdect.0.*/fritzdect.0.DECT_087610147624.present:{"val":false,"ack":true,"ts":1742408153100,"q":0,"from":"system.adapter.fritzdect.0","user":"system.user.admin","lc":1739294859072}
      2025-03-19 19:15:53.101  - debug: fritzdect.0 (22085) onStateChange => state fritzdect.0.DECT_087610147624.present changed: false (ack = true)
      2025-03-19 19:15:53.101  - debug: fritzdect.0 (22085) DECT_087610147624 is not present, check the device connection, no values are written
      2025-03-19 19:15:53.102  - debug: fritzdect.0 (22085) groups
      
      2025-03-19 19:15:53.102  - debug: fritzdect.0 (22085) []
      2025-03-19 19:15:53.102  - debug: fritzdect.0 (22085) __________________________
      2025-03-19 19:15:53.102  - debug: fritzdect.0 (22085) updating Routines 
      2025-03-19 19:15:55.346  - debug: fritzdect.0 (22085) __________________________
      2025-03-19 19:15:55.346  - debug: fritzdect.0 (22085) routines
      
      2025-03-19 19:15:55.346  - debug: fritzdect.0 (22085) []
      2025-03-19 19:15:55.348  - debug: fritzdect.0 (22085) glob state ["087610147624"]
      2025-03-19 19:15:55.348  - debug: fritzdect.0 (22085) updating Stats of device 087610147624
      2025-03-19 19:15:55.348  - debug: fritzdect.0 (22085) update Stats objects 087610147624
      2025-03-19 19:15:56.368  - debug: fritzdect.0 (22085) With 087610147624got the following to parse{"devicestats":{"voltage":"","power":"","energy":""}}
      
      
      Thomas Braun 1 Reply Last reply Reply Quote 0
      • N
        nilli @Asgothian last edited by

        @asgothian said in Zigbee.0: You need save and run adapter before pairing!:

        Deswegen ist ein Update auf eine 2.0.x version zu empfehlen - da habe ich den exakten Quelltext hier.

        Würde ich gerne versuchen, leider bin ich noch etwas unerfahren.
        Wie gehe ich zur Installation vor ? Gibt es irgendwo eine Anleitung ?

        Danke !!

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

          @nilli sagte in Zigbee.0: You need save and run adapter before pairing!:

          *** DMESG CRITICAL ERRORS ***
          15 CRITICAL ERRORS DETECTED!

          Was sind denn das für Errors?

          N 1 Reply Last reply Reply Quote 0
          • N
            nilli @Thomas Braun last edited by

            @thomas-braun

            Ich habe gestern versucht nach https://stmxcsr.com/micro/raspberry-signal-client.html signal-cli zu compelieren, bin aber leider krachend gescheitert 😧

            nils@raspi5:~ $ sudo dmesg --level=emerg,alert,crit -T
            [Tue Mar 18 08:14:41 2025] Unable to handle kernel paging request at virtual address ffffc00080aa3f04
            [Tue Mar 18 08:14:41 2025] Mem abort info:
            [Tue Mar 18 08:14:41 2025]   ESR = 0x0000000096000047
            [Tue Mar 18 08:14:41 2025]   EC = 0x25: DABT (current EL), IL = 32 bits
            [Tue Mar 18 08:14:41 2025]   SET = 0, FnV = 0
            [Tue Mar 18 08:14:41 2025]   EA = 0, S1PTW = 0
            [Tue Mar 18 08:14:41 2025]   FSC = 0x07: level 3 translation fault
            [Tue Mar 18 08:14:41 2025] Data abort info:
            [Tue Mar 18 08:14:41 2025]   ISV = 0, ISS = 0x00000047, ISS2 = 0x00000000
            [Tue Mar 18 08:14:41 2025]   CM = 0, WnR = 1, TnD = 0, TagAccess = 0
            [Tue Mar 18 08:14:41 2025]   GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0
            [Tue Mar 18 08:14:41 2025] swapper pgtable: 16k pages, 47-bit VAs, pgdp=0000000001398000
            [Tue Mar 18 08:14:41 2025] [ffffc00080aa3f04] pgd=100000000619c003, p4d=100000000619c003, pud=100000000619c003, pmd=10000000061a0003, pte=0000000000000000
            [Tue Mar 18 08:14:41 2025] Internal error: Oops: 0000000096000047 [#1] PREEMPT SMP
            [Tue Mar 18 08:14:41 2025] Code: d503201f b50000e2 14000020 38401423 (39000003) 
            
            
            1 Reply Last reply Reply Quote 0
            • N
              nilli @Asgothian last edited by

              Kann mir jemand einen Tip geben wie ich

              https://github.com/asgothian/ioBroker.zigbee/tarball/2.1.0

              installiere ? Danke !

              Asgothian 1 Reply Last reply Reply Quote 0
              • Asgothian
                Asgothian Developer @nilli last edited by Asgothian

                @nilli

                • Adapter anhalten (Wichtig!!!)
                • Adapter Seite aufrufen
                • Experten modus aktivieren (1)
                • Installation mit der 'Katze' (2)
                • Benutzerdefiniert auswählen
                • Link hinein kopieren
                • Installieren

                A.
                Nachtrag: Ich hatte einen Link auf den Post zum Testen der 2.0.x Version gegeben - da stand auch drin von wo die 'standard' 2.0.x zu installieren sind - diese sind im Latest verfügbar.
                Ich hoffe Du hast diesen Post gelesen.

                1 Reply Last reply Reply Quote 0
                • arteck
                  arteck Developer Most Active last edited by

                  @nilli sagte in Zigbee.0: You need save and run adapter before pairing!:

                  Kann mir jemand einen Tip geben wie ich

                  https://github.com/asgothian/ioBroker.zigbee/tarball/2.1.0

                  installiere ? Danke !

                  https://github.com/ioBroker/ioBroker.zigbee/wiki/GIT-install

                  N 1 Reply Last reply Reply Quote 0
                  • N
                    nilli @arteck last edited by

                    @arteck

                    Super ! Danke 🙂 Wenn man weiss wie es geht ganz einfach.

                    Adapter 2.0.4 installiert und konfiguriert.
                    Leider immer noch kein Erfolg ...

                    2025-03-19 21:43:52.019 - info: host.raspi5 iobroker exit 0
                    2025-03-19 21:43:53.877 - info: admin.0 (21591) ==> Connected system.user.admin from ::ffff:192.168.2.66
                    2025-03-19 21:43:54.259 - info: host.raspi5 instance system.adapter.zigbee.1 in version "2.0.4" (non-npm: asgothian/ioBroker.zigbee#2.1.0) started with pid 112722
                    2025-03-19 21:43:55.356 - info: zigbee.1 (112722) starting. Version 2.0.4 (non-npm: asgothian/ioBroker.zigbee#2.1.0) in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.19.0, js-controller: 7.0.6
                    2025-03-19 21:43:55.365 - info: zigbee.1 (112722) init localConfig
                    2025-03-19 21:43:55.368 - error: zigbee.1 (112722) Serial port not selected! Go to settings page.
                    2025-03-19 21:43:55.369 - info: zigbee.1 (112722) --> transmitPower : normal
                    2025-03-19 21:43:55.371 - info: zigbee.1 (112722) --- creating device debug ---
                    
                    2025-03-19 21:47:34.730 - info: host.raspi5 stopInstance system.adapter.zigbee.1 (force=false, process=true)
                    2025-03-19 21:47:34.733 - info: zigbee.1 (112722) Got terminate signal TERMINATE_YOURSELF
                    2025-03-19 21:47:34.734 - info: zigbee.1 (112722) cleaned everything up...
                    2025-03-19 21:47:34.735 - info: zigbee.1 (112722) local config saved
                    2025-03-19 21:47:34.737 - info: zigbee.1 (112722) Saved local configuration data
                    2025-03-19 21:47:34.738 - info: zigbee.1 (112722) terminating
                    2025-03-19 21:47:34.739 - info: zigbee.1 (112722) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                    2025-03-19 21:47:34.743 - error: zigbee.1 (112722) Failed to open the network: TypeError: Cannot read properties of undefined (reading 'permitJoin')
                    at Controller.permitJoin (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:263:35)
                    at ZigbeeController.permitJoin (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:690:33)
                    at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:664:24)
                    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                    at async Zigbee.onUnload (/opt/iobroker/node_modules/iobroker.zigbee/main.js:1070:17)
                    2025-03-19 21:47:34.744 - warn: zigbee.1 (112722) Failed to stop zigbee during startup
                    2025-03-19 21:47:34.744 - info: zigbee.1 (112722) terminating
                    2025-03-19 21:47:35.241 - info: zigbee.1 (112722) terminating
                    2025-03-19 21:47:35.269 - info: host.raspi5 instance system.adapter.zigbee.1 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                    2025-03-19 21:47:38.427 - info: host.raspi5 instance system.adapter.zigbee.1 in version "2.0.4" (non-npm: asgothian/ioBroker.zigbee#2.1.0) started with pid 112848
                    2025-03-19 21:47:39.389 - info: zigbee.1 (112848) starting. Version 2.0.4 (non-npm: asgothian/ioBroker.zigbee#2.1.0) in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.19.0, js-controller: 7.0.6
                    2025-03-19 21:47:39.398 - info: zigbee.1 (112848) init localConfig
                    2025-03-19 21:47:39.401 - info: zigbee.1 (112848) --> transmitPower : normal
                    2025-03-19 21:47:39.403 - info: zigbee.1 (112848) --- creating device debug ---
                    
                    asgothian created this issue in asgothian/ioBroker.zigbee

                    closed 1.3.9dev #2

                    Asgothian 1 Reply Last reply Reply Quote 0
                    • Asgothian
                      Asgothian Developer @nilli last edited by

                      @nilli hast du versucht das zigbee-subsystem direkt aus dem Admin-Interface zu starten, wie das im Post beschrieben ist, oder hast du einfach nur den Haken bei ‘automatisch starten’ gesetzt ?

                      A.

                      N 1 Reply Last reply Reply Quote 0
                      • N
                        nilli @Asgothian last edited by nilli

                        @asgothian

                        'start the Network automaticly' ist in den Instanzeneinstellungen nicht gesetzt.

                        Ich habe den Adapter im 'instanzen' Menue gestartet.

                        2025-03-19 22:08:47.638 - info: admin.0 (21591) ==> Connected system.user.admin from ::ffff:192.168.2.66
                        2025-03-19 22:08:50.036 - info: admin.0 (21591) <== Disconnect system.user.admin from ::ffff:192.168.2.66
                        2025-03-19 22:08:52.842 - info: host.raspi5 "system.adapter.zigbee.1" enabled
                        2025-03-19 22:08:53.076 - info: host.raspi5 instance system.adapter.zigbee.1 in version "2.0.4" (non-npm: asgothian/ioBroker.zigbee#2.1.0) started with pid 113695
                        2025-03-19 22:08:54.050 - info: zigbee.1 (113695) starting. Version 2.0.4 (non-npm: asgothian/ioBroker.zigbee#2.1.0) in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.19.0, js-controller: 7.0.6
                        2025-03-19 22:08:54.060 - info: zigbee.1 (113695) init localConfig
                        2025-03-19 22:08:54.063 - info: zigbee.1 (113695) --> transmitPower : normal
                        2025-03-19 22:08:54.066 - info: zigbee.1 (113695) --- creating device debug ---
                        
                        asgothian created this issue in asgothian/ioBroker.zigbee

                        closed 1.3.9dev #2

                        Asgothian 1 Reply Last reply Reply Quote 0
                        • Asgothian
                          Asgothian Developer @nilli last edited by

                          @nilli dann lies nochmal was ich oben geschrieben habe.

                          Eine wichtige Eigenschaft dieser Version ist das das zigbee subsystem nicht automatisch gestartet wird. Du kannst (und sollst) versuchen das subsystem aus dem Admin zu starten um a die Meldungen vom Start zu kommen. Wenn du das nicht machst bleibt der Adapter “gelb”

                          N 1 Reply Last reply Reply Quote 0
                          • N
                            nilli @Asgothian last edited by

                            @asgothian

                            Danke für Deine Hilfe.
                            Ich habe den Start/Stop button in der Instanzeinstellung benutzt.
                            Ich hoffe das war, was Du meintest.

                            0dfd0839-a01b-476d-9106-5465c2e29709-image.png

                            Asgothian 1 Reply Last reply Reply Quote 0
                            • Asgothian
                              Asgothian Developer @nilli last edited by

                              @nilli Das sieht besser aus, aber nicht gut - das USB Device wird vom Zigbee-Herdsman nicht sauber akzeptiert.

                              halte das Zigbee-Subsystem bitte wieder an (start/stop nochmal drücken) und setz dann den haken beim flow control. Danach noch einmal starten.

                              A.

                              N 1 Reply Last reply Reply Quote 0
                              • N
                                nilli @Asgothian last edited by nilli

                                @asgothian

                                Einmal gedrückt, wird der Start/Stop Button ausgegraut und hat keine Funktion mehr.
                                Extern angehalten, flow control aktiviert und neu gestartet :

                                40beafec-0351-4898-b1ce-cab3ab82b331-image.png

                                2025-03-20 21:03:28.458 - info: zigbee.1 (164560) --- creating device debug ---
                                2025-03-20 21:03:30.876 - info: admin.0 (21591) <== Disconnect system.user.admin from ::ffff:192.168.2.66
                                2025-03-20 21:03:33.961 - info: host.raspi5 stopInstance system.adapter.zigbee.1 (force=false, process=true)
                                2025-03-20 21:03:33.963 - info: zigbee.1 (164560) Got terminate signal TERMINATE_YOURSELF
                                2025-03-20 21:03:33.964 - info: zigbee.1 (164560) cleaned everything up...
                                2025-03-20 21:03:33.965 - info: zigbee.1 (164560) local config saved
                                2025-03-20 21:03:33.965 - info: zigbee.1 (164560) Saved local configuration data
                                2025-03-20 21:03:33.966 - info: zigbee.1 (164560) terminating
                                2025-03-20 21:03:33.967 - info: zigbee.1 (164560) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                                2025-03-20 21:03:33.970 - error: zigbee.1 (164560) Failed to open the network: TypeError: Cannot read properties of undefined (reading 'permitJoin')
                                at Controller.permitJoin (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:263:35)
                                at ZigbeeController.permitJoin (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:690:33)
                                at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:664:24)
                                at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                                at async Zigbee.onUnload (/opt/iobroker/node_modules/iobroker.zigbee/main.js:1070:17)
                                2025-03-20 21:03:33.971 - warn: zigbee.1 (164560) Failed to stop zigbee during startup
                                2025-03-20 21:03:33.972 - info: zigbee.1 (164560) terminating
                                2025-03-20 21:03:34.005 - info: host.raspi5 stopInstance system.adapter.zigbee.1 send kill signal
                                2025-03-20 21:03:34.467 - info: zigbee.1 (164560) terminating
                                2025-03-20 21:03:34.496 - info: host.raspi5 instance system.adapter.zigbee.1 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                                2025-03-20 21:03:37.710 - info: host.raspi5 instance system.adapter.zigbee.1 in version "2.0.4" (non-npm: asgothian/ioBroker.zigbee#2.1.0) started with pid 164576
                                2025-03-20 21:03:38.740 - info: zigbee.1 (164576) starting. Version 2.0.4 (non-npm: asgothian/ioBroker.zigbee#2.1.0) in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.19.0, js-controller: 7.0.6
                                2025-03-20 21:03:38.750 - info: zigbee.1 (164576) init localConfig
                                2025-03-20 21:03:38.753 - info: zigbee.1 (164576) --> transmitPower : normal
                                2025-03-20 21:03:38.755 - info: zigbee.1 (164576) --- creating device debug ---
                                
                                asgothian created this issue in asgothian/ioBroker.zigbee

                                closed 1.3.9dev #2

                                Asgothian 1 Reply Last reply Reply Quote 0
                                • Asgothian
                                  Asgothian Developer @nilli last edited by

                                  @nilli da bin am Ende - ich gehe relativ fest davon aus das der Stick nicht in Ordnung ist.

                                  Der Aufruf in den zigbee-Herdsman läuft so wie er soll, dieser sollte nach entsprechender Wartezeit zurück kommen. Das schreint er nicht zu tun. Der Adapter macht da nichts weiter. Die übergebenen Werte sehen OK aus. Warum der Herdsman ohne weitere Meldungen nicht startet kann ich kaum sagen.

                                  Als letzten Versuch kannst du:

                                  • den Adapter anhalten
                                  • den Adapter auf 'debug' umstellen (wichtig)
                                  • in der Adapter-Konfiguration den Haken bei 'zigbee-herdsman debug info' setzen
                                  • auf der Hardware-Seite versuchen den Herdsman zu starten.
                                  • 10 Minuten warten - schauen ob da überhaupt etwas kommt. Wenn nicht im Log schauen ob da debug-Meldungen aufgetaucht sind.

                                  A.

                                  1 Reply Last reply Reply Quote 0
                                  • D
                                    darkblu last edited by darkblu

                                    Selbigen Fehler wie der Threadersteller hatte ich gestern auch.
                                    Und zwar nachdem es 9 updates für den Raspi gab.
                                    Danach wurde der Adapter einfach nicht grün.
                                    Neustart und stromlos machen hatte alles nix geholfen.
                                    Dann habe ich „iob fix, iob update, iob upgrade self (?)“
                                    (oder so ähnlich) und sudo reboot gemacht und erst danach wurde der Zigbee Adapter wieder grün.

                                    War wieder ein sehr aufregender Abend 😰

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

                                    Support us

                                    ioBroker
                                    Community Adapters
                                    Donate

                                    858
                                    Online

                                    31.9k
                                    Users

                                    80.1k
                                    Topics

                                    1.3m
                                    Posts

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