Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. Zigbee-Adapter verbindet sich nicht

    NEWS

    • Neues Video "KI im Smart Home" - ioBroker plus n8n

    • Neues Video über Aliase, virtuelle Geräte und Kategorien

    • Wir empfehlen: Node.js 22.x

    Zigbee-Adapter verbindet sich nicht

    This topic has been deleted. Only users with topic management privileges can see it.
    • S
      smartyH last edited by

      Ich nutze eine rpi4 und den Sonoff ZB 3.0 usb dongle plus Adapter. Nachdem ich im ioBroker auf "start" der Zigbee Instanz drücke, werden zunächst "Verbunden mit Host" & "Lebenszeichen" grün, dann werden alle (inklusive "Verbunden mit Gerät oder Dienst") rot. Ich habe es bisher nicht einmal geschafft eine Verbindung zwischen rpi und zigbee-interface herzustellen. Über mögliche Ansätze bin ich dankbar!

      Es ist folgender Adapter "ZBDongle-P" (basiert auf CC2652P).
      Firmware habe ich aktualisiert (diese hier habe ich genommen https://github.com/Koenkk/Z-Stack-firmware/tree/master/coordinator/Z-Stack_3.x.0/bin), ich habe es sowohl mit Router als auch mit Coordinator-Firmware versucht.

      Folgende Einstellungen habe ich im ioBroker vorgenommen:
      COM-Anschlussname: /dev/ttyUSB0
      Typ: TI Z-Stack/CCxxxx
      Network: DDDDDDDDDDDDaaaa
      der Rest entspricht den default-Settings

      ff42d502-f3d5-4a47-a134-826f65b8b5e6-image.png

      Systemdata
      Hardwaresystem: Pi4
      Arbeitsspeicher: 5GB
      Festplattenart: SD-Karte
      Betriebssystem: Linux
      Node-Version: 18.16.1
      Nodejs-Version: ?.?.?
      NPM-Version: 9.5.1
      Installationsart: Befehl "curl -sLf https://iobroker.net/install.sh I bash -"
      Image genutzt: Nein, kein Verwendung von Docker

      Hier noch ein paar Consolen-Befehle die vielleicht interessant sein könnten:

      villa@raspberrypi:~/zigbee $ uname -a
      Linux raspberrypi 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr  3 17:24:16 BST 2023 aarch64 GNU/Linux
      villa@raspberrypi:~/zigbee $ ls -la /dev/serial/
      insgesamt 0
      drwxr-xr-x  3 root root   60 13. Jul 20:28 .
      drwxr-xr-x 17 root root 4020 13. Jul 20:28 ..
      drwxr-xr-x  2 root root   60 13. Jul 20:28 by-path
      villa@raspberrypi:~/zigbee $ ls -la /dev/serial/by-path/
      insgesamt 0
      drwxr-xr-x 2 root root 60 13. Jul 20:28 .
      drwxr-xr-x 3 root root 60 13. Jul 20:28 ..
      lrwxrwxrwx 1 root root 13 13. Jul 20:28 platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1.4:1.0-port0 -> ../../ttyUSB0
      villa@raspberrypi:~/zigbee $ lsusb
      Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
      Bus 001 Device 003: ID 10c4:ea60 Silicon Labs CP210x UART Bridge
      Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
      Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
      

      Hier die Logs:

      host.raspberrypi	2023-07-14 20:45:52.373	info	Do not restart adapter system.adapter.zigbee.0 because disabled or deleted
      host.raspberrypi	2023-07-14 20:45:52.372	error	instance system.adapter.zigbee.0 terminated with code 3 (NO_ADAPTER_CONFIG_FOUND)
      zigbee.0		2023-07-14 20:45:51.763	warn	Terminated (NO_ADAPTER_CONFIG_FOUND): Without reason
      zigbee.0		2023-07-14 20:45:51.670	error	adapter disabled
      host.raspberrypi	2023-07-14 20:45:43.735	info	"system.adapter.zigbee.0" disabled
      host.raspberrypi	2023-07-14 20:45:17.012	info	Restart adapter system.adapter.zigbee.0 because enabled
      host.raspberrypi	2023-07-14 20:45:17.011	error	instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
      host.raspberrypi	2023-07-14 20:45:17.010	error	Caught by controller[1]: at Zigbee.doConnect (/opt/iobroker/node_modules/iobroker.zigbee/main.js:345:18)
      host.raspberrypi	2023-07-14 20:45:17.010	error	Caught by controller[1]: at Zigbee.sendError (/opt/iobroker/node_modules/iobroker.zigbee/main.js:118:32)
      host.raspberrypi	2023-07-14 20:45:17.009	error	Caught by controller[1]: at Object.configureScope (/opt/iobroker/node_modules/@sentry/src/exports.ts:76:1)
      host.raspberrypi	2023-07-14 20:45:17.009	error	Caught by controller[1]: at Hub.configureScope (/opt/iobroker/node_modules/@sentry/src/hub.ts:340:1)
      host.raspberrypi	2023-07-14 20:45:17.008	error	Caught by controller[1]: at /opt/iobroker/node_modules/iobroker.zigbee/main.js:122:56
      host.raspberrypi	2023-07-14 20:45:17.008	error	Caught by controller[1]: TypeError: Cannot read properties of undefined (reading 'Error')
      host.raspberrypi	2023-07-14 20:45:17.007	error	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:
      zigbee.0		2023-07-14 20:45:11.591	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
      zigbee.0		2023-07-14 20:45:11.590	info	terminating
      zigbee.0		2023-07-14 20:45:11.589	warn	Failed to stop zigbee during startup
      zigbee.0		2023-07-14 20:45:11.563	info	Zigbee: disabling joining new devices.
      zigbee.0		2023-07-14 20:45:11.552	info	cleaned everything up...
      zigbee.0		2023-07-14 20:45:11.542	error	Cannot read properties of undefined (reading 'Error')
      zigbee.0		2023-07-14 20:45:11.542	error	TypeError: Cannot read properties of undefined (reading 'Error') at /opt/iobroker/node_modules/iobroker.zigbee/main.js:122:56 at Hub.configureScope (/opt/iobroker/node_modules/@sentry/src/hub.ts:340:1) at Object.configureScope (/opt/iobroker/node_modules/@sentry/src/exports.ts:76:1) at Zigbee.sendError (/opt/iobroker/node_modules/iobroker.zigbee/main.js:118:32) at Zigbee.doConnect (/opt/iobroker/node_modules/iobroker.zigbee/main.js:345:18)
      zigbee.0		2023-07-14 20:45:11.488	error	unhandled promise rejection: Cannot read properties of undefined (reading 'Error')
      zigbee.0		2023-07-14 20:45:11.487	error	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().
      zigbee.0		2023-07-14 20:45:11.486	error	Error herdsman start
      zigbee.0		2023-07-14 20:45:11.485	error	Failed to start Zigbee
      zigbee.0		2023-07-14 20:45:11.484	error	Starting zigbee-herdsman problem : "Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)"
      zigbee.0		2023-07-14 20:44:51.275	info	Installed Version: iobroker.zigbee@1.8.16
      zigbee.0		2023-07-14 20:44:50.501	info	Starting Zigbee npm ...
      zigbee.0		2023-07-14 20:44:50.499	info	delete old Backup files. keep only last 10
      zigbee.0		2023-07-14 20:44:50.363	info	starting. Version 1.8.16 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.16.1, js-controller: 4.0.24
      host.raspberrypi	2023-07-14 20:44:45.636	info	instance system.adapter.zigbee.0 started with pid 3230
      host.raspberrypi	2023-07-14 20:44:45.551	info	"system.adapter.zigbee.0" enabled
      
      mickym Thomas Braun 2 Replies Last reply Reply Quote 0
      • mickym
        mickym Most Active @smartyH last edited by

        @smartyh Und hier was zum Lesen

        https://forum.iobroker.net/topic/65017/zigbee-conbee2-funktioniert-nach-update-nicht-mehr-udev

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

          @smartyh

          sudo apt update
          apt policy udev
          

          sagt?

          S 1 Reply Last reply Reply Quote 0
          • S
            smartyH @Thomas Braun last edited by

            @thomas-braun, sagt Folgendes

            villa@raspberrypi:~ $ sudo apt update
            OK:1 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
            OK:2 http://archive.raspberrypi.org/debian bullseye InRelease
            OK:3 https://deb.nodesource.com/node_18.x bullseye InRelease
            Paketlisten werden gelesen… Fertig
            Abhängigkeitsbaum wird aufgebaut… Fertig
            Statusinformationen werden eingelesen… Fertig
            Alle Pakete sind aktuell.
            villa@raspberrypi:~ $ apt policy udev
            udev:
              Installiert:           247.3-7+rpi1+deb11u2
              Installationskandidat: 247.3-7+rpi1+deb11u2
              Versionstabelle:
             *** 247.3-7+rpi1+deb11u2 500
                    500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages
                    100 /var/lib/dpkg/status
            
            mickym 1 Reply Last reply Reply Quote 0
            • mickym
              mickym Most Active @smartyH last edited by mickym

              @smartyh Bingo - wieder einer in die Falle gegangen. 😉 Tja dann lesen, wie empfohlen. Keine Ahnung warum nie gesucht wird und man muss auch nur den ersten Post durchlesen.

              S 1 Reply Last reply Reply Quote 0
              • S
                smartyH @mickym last edited by

                @mickym vielen Dank, habe die empfohlenen Schritte gemacht, hat leider nicht gefruchtet. Ich lese mir den Thread mal weiter durch.

                Hier mein Output für 'apt update' und 'apt policy udev' ist, sollte also passen.

                villa@raspberrypi:~ $ sudo apt update
                Hit:1 http://archive.raspberrypi.org/debian bullseye InRelease
                Hit:2 https://deb.nodesource.com/node_18.x bullseye InRelease
                Hit:3 http://deb.debian.org/debian bullseye InRelease
                Hit:4 http://security.debian.org/debian-security bullseye-security InRelease
                Hit:5 http://deb.debian.org/debian bullseye-updates InRelease
                Hit:6 http://deb.debian.org/debian bullseye-proposed-updates InRelease
                Reading package lists... Done
                Building dependency tree... Done
                Reading state information... Done
                24 packages can be upgraded. Run 'apt list --upgradable' to see them.
                villa@raspberrypi:~ $ apt policy udev
                udev:
                  Installed: 247.3-7+deb11u4
                  Candidate: 247.3-7+deb11u4
                  Version table:
                 *** 247.3-7+deb11u4 500
                        500 http://deb.debian.org/debian bullseye-proposed-updates/main arm64 Packages
                        100 /var/lib/dpkg/status
                     247.3-7+deb11u2 500
                        500 http://deb.debian.org/debian bullseye/main arm64 Packages
                

                Meine neuen logs:

                host.raspberrypi	2023-07-14 23:42:29.235	info	"system.adapter.zigbee.0" disabled
                host.raspberrypi	2023-07-14 23:42:24.235	info	Restart adapter system.adapter.zigbee.0 because enabled
                host.raspberrypi	2023-07-14 23:42:24.234	error	instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
                host.raspberrypi	2023-07-14 23:42:24.234	error	Caught by controller[1]: at Zigbee.onZigbeeAdapterReady (/opt/iobroker/node_modules/iobroker.zigbee/main.js:415:30)
                host.raspberrypi	2023-07-14 23:42:24.234	error	Caught by controller[1]: at Zigbee.sendError (/opt/iobroker/node_modules/iobroker.zigbee/main.js:118:32)
                host.raspberrypi	2023-07-14 23:42:24.234	error	Caught by controller[1]: at Object.configureScope (/opt/iobroker/node_modules/@sentry/src/exports.ts:76:1)
                host.raspberrypi	2023-07-14 23:42:24.234	error	Caught by controller[1]: at Hub.configureScope (/opt/iobroker/node_modules/@sentry/src/hub.ts:340:1)
                host.raspberrypi	2023-07-14 23:42:24.233	error	Caught by controller[1]: at /opt/iobroker/node_modules/iobroker.zigbee/main.js:122:56
                host.raspberrypi	2023-07-14 23:42:24.233	error	Caught by controller[1]: TypeError: Cannot read properties of undefined (reading 'Error')
                host.raspberrypi	2023-07-14 23:42:24.232	error	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:
                zigbee.0		2023-07-14 23:42:23.659	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
                zigbee.0		2023-07-14 23:42:23.656	info	terminating
                zigbee.0		2023-07-14 23:42:23.156	info	Zigbee: disabling joining new devices.
                zigbee.0		2023-07-14 23:42:23.154	info	cleaned everything up...
                zigbee.0		2023-07-14 23:42:23.139	error	Cannot read properties of undefined (reading 'Error')
                zigbee.0		2023-07-14 23:42:23.139	error	TypeError: Cannot read properties of undefined (reading 'Error') at /opt/iobroker/node_modules/iobroker.zigbee/main.js:122:56 at Hub.configureScope (/opt/iobroker/node_modules/@sentry/src/hub.ts:340:1) at Object.configureScope (/opt/iobroker/node_modules/@sentry/src/exports.ts:76:1) at Zigbee.sendError (/opt/iobroker/node_modules/iobroker.zigbee/main.js:118:32) at Zigbee.onZigbeeAdapterReady (/opt/iobroker/node_modules/iobroker.zigbee/main.js:415:30)
                zigbee.0		2023-07-14 23:42:23.094	error	unhandled promise rejection: Cannot read properties of undefined (reading 'Error')
                zigbee.0		2023-07-14 23:42:23.093	error	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().
                zigbee.0		2023-07-14 23:42:23.091	error	Unable to apply ExtPanID changes: Error: SRSP - SYS - osalNvRead after 0,2ms
                zigbee.0		2023-07-14 23:42:23.088	info	Zigbee started
                
                mickym 1 Reply Last reply Reply Quote 0
                • mickym
                  mickym Most Active @smartyH last edited by

                  @smarty Na mit der udev Version sollte es kein Problem mehr sein. Was anderes wirst in dem Thread nicht finden. Dann hast Du noch ein anderes Problem, da kann ich Dir aber nicht helfen.

                  1 Reply Last reply Reply Quote 0
                  • S
                    smartyH last edited by

                    @mickym okay schade, trd. danke dir!

                    T 1 Reply Last reply Reply Quote 0
                    • T
                      TT-Tom @smartyH last edited by TT-Tom

                      @smartyh

                      Könnte das sentry Problem sein. Schalte mal den expertenmodus ein und deaktiviere In der Instanz hinten das Sentry. Starte mal neu.

                      S 1 Reply Last reply Reply Quote 0
                      • S
                        smartyH @TT-Tom last edited by

                        @tt-tom vielen Dank dir, ich habe jetzt 'Home Assistant' auf Raspi gespielt und dort hat alles ganz smooth geklappt. Werde jetzt erstmal damit arbeiten.

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

                        Support us

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

                        855
                        Online

                        32.1k
                        Users

                        80.7k
                        Topics

                        1.3m
                        Posts

                        4
                        10
                        457
                        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