Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. Zigbee startet nach Recovery nicht mehr

    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 startet nach Recovery nicht mehr

    This topic has been deleted. Only users with topic management privileges can see it.
    • T
      Tapdance 0 last edited by

      Hallo,

      ich hatte schwirigkeiten mit meinem IO Brocker, also habe ich eine Sicherung auf einer neuen sd Karte mit frisch instalierten iobroker zurück gespielt. Danach funktionierte alles Top. Mein Io Brocker stratet jeden nacht einmal duch, da er früher nicht stabil lief. Seir dem ersten neustart nach dem alles funktionierte startet mein Zigbee adapter nicht. Wenn ich die Fehlermeldung richtig verstehe findet er den Stick oder ein Verzeichnis nicht 🤷‍♂️

      Leider komme ich auch mit den vorhandenen Forum beiträgen nicht weiter.

      Wer kann bitte helfen 🙏
      Ich kenne mich mit der Komandozeile nicht so aus hoffe das Log reicht so. Falls nicht verratet mir bitte wie ich das besser erstelle

      DANKE für Eure Unterstützung

      2023-10-10 19:48:09.095 - info: zigbee.0 (17045) Got terminate signal TERMINATE_YOURSELF
      2023-10-10 19:48:09.289 - info: host.raspberrypi stopInstance system.adapter.zigbee.0 send kill signal
      2023-10-10 19:48:09.099 - info: zigbee.0 (17045) cleaned everything up...
      2023-10-10 19:48:09.148 - debug: zigbee.0 (17045) DeviceAvailability:Publish available for 0x00158d00044d8e0b = false
      2023-10-10 19:48:09.162 - debug: zigbee.0 (17045) DeviceAvailability:Publish LQ for 0x00158d00044d8e0b = 0
      2023-10-10 19:48:09.179 - debug: zigbee.0 (17045) DeviceAvailability:Publish available for 0x00158d000257bae7 = false
      2023-10-10 19:48:09.190 - debug: zigbee.0 (17045) DeviceAvailability:Publish LQ for 0x00158d000257bae7 = 0
      2023-10-10 19:48:09.195 - debug: zigbee.0 (17045) DeviceAvailability:Publish available for 0x00158d00045f7cee = false
      2023-10-10 19:48:09.199 - debug: zigbee.0 (17045) DeviceAvailability:Publish LQ for 0x00158d00045f7cee = 0
      2023-10-10 19:48:09.203 - debug: zigbee.0 (17045) DeviceAvailability:Publish available for 0x00158d0004521481 = false
      2023-10-10 19:48:09.206 - debug: zigbee.0 (17045) DeviceAvailability:Publish LQ for 0x00158d0004521481 = 0
      2023-10-10 19:48:09.211 - debug: zigbee.0 (17045) DeviceAvailability:Publish available for 0x00158d000461b53e = false
      2023-10-10 19:48:09.214 - debug: zigbee.0 (17045) DeviceAvailability:Publish LQ for 0x00158d000461b53e = 0
      2023-10-10 19:48:09.218 - debug: zigbee.0 (17045) DeviceAvailability:Publish available for 0x680ae2fffec91ea4 = false
      2023-10-10 19:48:09.221 - debug: zigbee.0 (17045) DeviceAvailability:Publish LQ for 0x680ae2fffec91ea4 = 0
      2023-10-10 19:48:09.226 - debug: zigbee.0 (17045) DeviceAvailability:Publish available for 0x588e81fffe2b8762 = false
      2023-10-10 19:48:09.229 - debug: zigbee.0 (17045) DeviceAvailability:Publish LQ for 0x588e81fffe2b8762 = 0
      2023-10-10 19:48:09.233 - debug: zigbee.0 (17045) DeviceAvailability:Publish available for 0x680ae2fffe924d57 = false
      2023-10-10 19:48:09.236 - debug: zigbee.0 (17045) DeviceAvailability:Publish LQ for 0x680ae2fffe924d57 = 0
      2023-10-10 19:48:09.240 - debug: zigbee.0 (17045) DeviceAvailability:Publish available for 0x00158d00045eb708 = false
      2023-10-10 19:48:09.244 - debug: zigbee.0 (17045) DeviceAvailability:Publish LQ for 0x00158d00045eb708 = 0
      2023-10-10 19:48:09.248 - debug: zigbee.0 (17045) DeviceAvailability:Publish available for 0x00158d0002a71e25 = false
      2023-10-10 19:48:09.251 - debug: zigbee.0 (17045) DeviceAvailability:Publish LQ for 0x00158d0002a71e25 = 0
      2023-10-10 19:48:09.255 - debug: zigbee.0 (17045) DeviceAvailability:Publish available for 0x04cf8cdf3c794764 = false
      2023-10-10 19:48:09.259 - debug: zigbee.0 (17045) DeviceAvailability:Publish LQ for 0x04cf8cdf3c794764 = 0
      2023-10-10 19:48:09.262 - debug: zigbee.0 (17045) DeviceAvailability:Publish available for 0x04cf8cdf3c7946a1 = false
      2023-10-10 19:48:09.265 - debug: zigbee.0 (17045) DeviceAvailability:Publish LQ for 0x04cf8cdf3c7946a1 = 0
      2023-10-10 19:48:09.270 - debug: zigbee.0 (17045) DeviceAvailability:Publish available for 0x00158d00045f8d3d = false
      2023-10-10 19:48:09.273 - debug: zigbee.0 (17045) DeviceAvailability:Publish LQ for 0x00158d00045f8d3d = 0
      2023-10-10 19:48:09.277 - debug: zigbee.0 (17045) DeviceAvailability:Publish available for 0x00158d0004597653 = false
      2023-10-10 19:48:09.280 - debug: zigbee.0 (17045) DeviceAvailability:Publish LQ for 0x00158d0004597653 = 0
      2023-10-10 19:48:09.295 - debug: zigbee.0 (17045) DeviceAvailability:Publish available for 0x842e14fffe768d41 = false
      2023-10-10 19:48:09.298 - debug: zigbee.0 (17045) DeviceAvailability:Publish LQ for 0x842e14fffe768d41 = 0
      2023-10-10 19:48:09.302 - debug: zigbee.0 (17045) DeviceAvailability:Publish available for 0xbc33acfffe2ab392 = false
      2023-10-10 19:48:09.318 - debug: zigbee.0 (17045) DeviceAvailability:Publish LQ for 0xbc33acfffe2ab392 = 0
      2023-10-10 19:48:09.327 - debug: zigbee.0 (17045) DeviceAvailability:Publish available for 0x04cf8cdf3c7b5255 = false
      2023-10-10 19:48:09.331 - debug: zigbee.0 (17045) DeviceAvailability:Publish LQ for 0x04cf8cdf3c7b5255 = 0
      2023-10-10 19:48:09.334 - debug: zigbee.0 (17045) DeviceAvailability:Publish available for 0x04cf8cdf3c7b51f7 = false
      2023-10-10 19:48:09.338 - debug: zigbee.0 (17045) DeviceAvailability:Publish LQ for 0x04cf8cdf3c7b51f7 = 0
      2023-10-10 19:48:09.359 - debug: zigbee.0 (17045) DeviceAvailability:Publish available for 0x04cf8cdf3c78b7ba = false
      2023-10-10 19:48:09.363 - debug: zigbee.0 (17045) DeviceAvailability:Publish LQ for 0x04cf8cdf3c78b7ba = 0
      2023-10-10 19:48:09.366 - debug: zigbee.0 (17045) DeviceAvailability:Publish available for 0x00158d000461da61 = false
      2023-10-10 19:48:09.378 - debug: zigbee.0 (17045) DeviceAvailability:Publish LQ for 0x00158d000461da61 = 0
      2023-10-10 19:48:09.391 - debug: zigbee.0 (17045) DeviceAvailability:Publish available for 0xf4b3b1fffef87315 = false
      2023-10-10 19:48:09.395 - debug: zigbee.0 (17045) DeviceAvailability:Publish LQ for 0xf4b3b1fffef87315 = 0
      2023-10-10 19:48:09.398 - debug: zigbee.0 (17045) DeviceAvailability:Publish available for 0xf4b3b1fffef8731e = false
      2023-10-10 19:48:09.411 - debug: zigbee.0 (17045) DeviceAvailability:Publish LQ for 0xf4b3b1fffef8731e = 0
      2023-10-10 19:48:09.415 - debug: zigbee.0 (17045) DeviceAvailability:Publish available for 0xf4b3b1fffef84d2d = false
      2023-10-10 19:48:09.417 - debug: zigbee.0 (17045) DeviceAvailability:Publish LQ for 0xf4b3b1fffef84d2d = 0
      2023-10-10 19:48:09.424 - debug: zigbee.0 (17045) DeviceAvailability:Publish available for 0xf4b3b1fffef87b6a = false
      2023-10-10 19:48:09.431 - debug: zigbee.0 (17045) DeviceAvailability:Publish LQ for 0xf4b3b1fffef87b6a = 0
      2023-10-10 19:48:09.435 - debug: zigbee.0 (17045) DeviceAvailability:Publish available for 0xf4b3b1fffef853ac = false
      2023-10-10 19:48:09.438 - debug: zigbee.0 (17045) DeviceAvailability:Publish LQ for 0xf4b3b1fffef853ac = 0
      2023-10-10 19:48:09.442 - debug: zigbee.0 (17045) DeviceAvailability:Publish available for 0x04cd15fffefe9ca8 = false
      2023-10-10 19:48:09.445 - debug: zigbee.0 (17045) DeviceAvailability:Publish LQ for 0x04cd15fffefe9ca8 = 0
      2023-10-10 19:48:09.449 - debug: zigbee.0 (17045) DeviceAvailability:Publish available for 0xa4c138c66404899e = false
      2023-10-10 19:48:09.452 - debug: zigbee.0 (17045) DeviceAvailability:Publish LQ for 0xa4c138c66404899e = 0
      2023-10-10 19:48:09.463 - info: zigbee.0 (17045) Zigbee: disabling joining new devices.
      2023-10-10 19:48:09.643 - warn: zigbee.0 (17045) Failed to stop zigbee during startup
      2023-10-10 19:48:09.643 - info: zigbee.0 (17045) terminating
      2023-10-10 19:48:09.644 - debug: zigbee.0 (17045) Plugin sentry destroyed
      2023-10-10 19:48:09.645 - info: zigbee.0 (17045) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
      2023-10-10 19:48:09.646 - info: zigbee.0 (17045) terminating
      2023-10-10 19:48:09.710 - info: zigbee.0 (17045) debug devices set to []
      2023-10-10 19:48:10.268 - info: host.raspberrypi instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
      2023-10-10 19:48:12.424 - info: host.raspberrypi instance system.adapter.zigbee.0 started with pid 17514
      2023-10-10 19:48:15.481 - warn: shelly.0 (1514) [authEnabled] 192.168.2.214 (shellydimmer2 / shellydimmer2-8CAAB54C4B57 / SHDM-2#8CAAB54C4B57#1): This device is not protected via restricted login (see adapter documentation for details)
      2023-10-10 19:48:16.592 - debug: zigbee.0 (17514) Redis Objects: Use Redis connection: 127.0.0.1:9001
      2023-10-10 19:48:16.641 - debug: zigbee.0 (17514) Objects client ready ... initialize now
      2023-10-10 19:48:16.644 - debug: zigbee.0 (17514) Objects create System PubSub Client
      2023-10-10 19:48:16.646 - debug: zigbee.0 (17514) Objects create User PubSub Client
      2023-10-10 19:48:16.699 - debug: zigbee.0 (17514) Objects client initialize lua scripts
      2023-10-10 19:48:16.709 - debug: zigbee.0 (17514) Objects connected to redis: 127.0.0.1:9001
      2023-10-10 19:48:16.754 - debug: zigbee.0 (17514) Redis States: Use Redis connection: 127.0.0.1:9000
      2023-10-10 19:48:16.773 - debug: zigbee.0 (17514) States create System PubSub Client
      2023-10-10 19:48:16.775 - debug: zigbee.0 (17514) States create User PubSub Client
      2023-10-10 19:48:16.847 - debug: zigbee.0 (17514) States connected to redis: 127.0.0.1:9000
      2023-10-10 19:48:16.955 - debug: zigbee.0 (17514) Plugin sentry Initialize Plugin (enabled=true)
      2023-10-10 19:48:17.076 - warn: shelly.0 (1514) [authEnabled] 192.168.2.226 (shellydimmer2 / shellydimmer2-8CAAB54C4E21 / SHDM-2#8CAAB54C4E21#1): This device is not protected via restricted login (see adapter documentation for details)
      2023-10-10 19:48:17.555 - info: zigbee.0 (17514) starting. Version 1.8.23 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.17.1, js-controller: 5.0.12
      2023-10-10 19:48:17.611 - debug: zigbee.0 (17514) Using zigbee-herdsman with settings: {"network":{"panID":6754,"extendedPanID":[221,221,221,221,221,221,221,221],"channelList":[11],"networkKey":[1,3,5,7,9,11,13,15,0,2,4,6,8,10,12,13]},"databasePath":"/opt/iobroker/iobroker-data/zigbee_0/shepherd.db","backupPath":"/opt/iobroker/iobroker-data/zigbee_0/nvbackup.json","serialPort":{"baudRate":115200,"rtscts":false,"path":"/dev/serial/by-id/usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B0018E2F56A-if00","adapter":"zstack"},"adapter":{"forceStartWithInconsistentAdapterConfiguration":false}}
      2023-10-10 19:48:17.698 - info: zigbee.0 (17514) delete old Backup files. keep only last 10
      2023-10-10 19:48:17.701 - info: zigbee.0 (17514) Starting Zigbee npm ...
      2023-10-10 19:48:17.747 - debug: zigbee.0 (17514) Starting zigbee-herdsman...
      2023-10-10 19:48:17.833 - warn: shelly.0 (1514) [authEnabled] 192.168.2.180 (shellydimmer / shellydimmer-D3E918 / SHDM-1#D3E918#1): This device is not protected via restricted login (see adapter documentation for details)
      2023-10-10 19:48:18.138 - error: zigbee.0 (17514) Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B0018E2F56A-if00'"
      2023-10-10 19:48:18.140 - error: zigbee.0 (17514) Failed to start Zigbee
      2023-10-10 19:48:18.140 - error: zigbee.0 (17514) Error herdsman start
      2023-10-10 19:48:18.144 - info: zigbee.0 (17514) Installed Version: iobroker.zigbee@1.8.23
      2023-10-10 19:48:18.474 - debug: zigbee.0 (17514) Backup /opt/iobroker/iobroker-data/zigbee_0/backup_2023_10_10-19_48_17.tar.gz success
      2023-10-10 19:48:25.902 - warn: shelly.0 (1514) [authEnabled] 192.168.2.214 (shellydimmer2 / shellydimmer2-8CAAB54C4B57 / SHDM-2#8CAAB54C4B57#1): This device is not protected via restricted login (see adapter documentation for details)
      2023-10-10 19:48:27.425 - warn: shelly.0 (1514) [authEnabled] 192.168.2.226 (shellydimmer2 / shellydimmer2-8CAAB54C4E21 / SHDM-2#8CAAB54C4E21#1): This device is not protected via restricted login (see adapter documentation for details)
      2023-10-10 19:48:28.021 - warn: shelly.0 (1514) [authEnabled] 192.168.2.180 (shellydimmer / shellydimmer-D3E918 / SHDM-1#D3E918#1): This device is not protected via restricted login (see adapter documentation for details)
      2023-10-10 19:48:28.144 - info: zigbee.0 (17514) Try to reconnect. 1 attempts left
      2023-10-10 19:48:28.145 - info: zigbee.0 (17514) Starting Zigbee npm ...
      2023-10-10 19:48:28.151 - debug: zigbee.0 (17514) Starting zigbee-herdsman...
      2023-10-10 19:48:28.162 - error: zigbee.0 (17514) Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B0018E2F56A-if00'"
      2023-10-10 19:48:28.162 - error: zigbee.0 (17514) Failed to start Zigbee
      2023-10-10 19:48:28.163 - error: zigbee.0 (17514) Error herdsman start
      2023-10-10 19:48:28.171 - info: zigbee.0 (17514) Installed Version: iobroker.zigbee@1.8.23
      2023-10-10 19:48:36.366 - warn: shelly.0 (1514) [authEnabled] 192.168.2.214 (shellydimmer2 / shellydimmer2-8CAAB54C4B57 / SHDM-2#8CAAB54C4B57#1): This device is not protected via restricted login (see adapter documentation for details)
      2023-10-10 19:48:36.898 - warn: shelly.0 (1514) State value to set for "shelly.0.SHDM-2#8CAAB54C4B57#1.temperatureF" has value "111.55" greater than max "100"
      2023-10-10 19:48:38.017 - warn: shelly.0 (1514) [authEnabled] 192.168.2.226 (shellydimmer2 / shellydimmer2-8CAAB54C4E21 / SHDM-2#8CAAB54C4E21#1): This device is not protected via restricted login (see adapter documentation for details)
      2023-10-10 19:48:38.261 - warn: shelly.0 (1514) [authEnabled] 192.168.2.180 (shellydimmer / shellydimmer-D3E918 / SHDM-1#D3E918#1): This device is not protected via restricted login (see adapter documentation for details)
      2023-10-10 19:48:46.840 - warn: shelly.0 (1514) [authEnabled] 192.168.2.214 (shellydimmer2 / shellydimmer2-8CAAB54C4B57 / SHDM-2#8CAAB54C4B57#1): This device is not protected via restricted login (see adapter documentation for details)
      2023-10-10 19:48:48.396 - warn: shelly.0 (1514) [authEnabled] 192.168.2.226 (shellydimmer2 / shellydimmer2-8CAAB54C4E21 / SHDM-2#8CAAB54C4E21#1): This device is not protected via restricted login (see adapter documentation for details)
      2023-10-10 19:48:48.580 - warn: shelly.0 (1514) [authEnabled] 192.168.2.180 (shellydimmer / shellydimmer-D3E918 / SHDM-1#D3E918#1): This device is not protected via restricted login (see adapter documentation for details)
      2023-10-10 19:48:51.951 - warn: shelly.0 (1514) State value to set for "shelly.0.SHDM-2#8CAAB54C4B57#1.temperatureF" has value "111.69" greater than max "100"
      2023-10-10 19:48:57.659 - warn: shelly.0 (1514) [authEnabled] 192.168.2.214 (shellydimmer2 / shellydimmer2-8CAAB54C4B57 / SHDM-2#8CAAB54C4B57#1): This device is not protected via restricted login (see adapter documentation for details)
      2023-10-10 19:48:58.865 - warn: shelly.0 (1514) [authEnabled] 192.168.2.226 (shellydimmer2 / shellydimmer2-8CAAB54C4E21 / SHDM-2#8CAAB54C4E21#1): This device is not protected via restricted login (see adapter documentation for details)
      2023-10-10 19:48:58.908 - warn: shelly.0 (1514) [authEnabled] 192.168.2.180 (shellydimmer / shellydimmer-D3E918 / SHDM-1#D3E918#1): This device is not protected via restricted login (see adapter documentation for details)

      1 Reply Last reply Reply Quote 0
      • ?
        A Former User last edited by A Former User

        Moin,

        Log ausgaben bitte in Code Tags einschließen </>, damit das besser zu lesen ist.
        2538f416-bfc4-4c6e-ad8e-b3d6f0c974f3-image.png

        Dann hast Du im Log nicht nur Meldungen zum eigentlichen Problem, sondern auch andere Meldungen vom Shelly, das verwirrt zusätzlich.
        cf5bc832-790a-4525-9afe-09c3ee6fb1fd-image.png

        Dann fehlt jegliche Information, zur Installation, welche Debian Version, usw.

        Zeig mal die lange Ausführung, in Code Tags, von

        iob diag

        Ich vermute, dass Du das Problem mit udev hast, such mal nach dem Stichwort hier im Forum, da gibt es schon einige Themen dazu.

        VG
        Bernd

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

          @tapdance-0 sagte in Zigbee startet nach Recovery nicht mehr:

          Wenn ich die Fehlermeldung richtig verstehe findet er den Stick oder ein Verzeichnis nicht

          ja genau richtig LESEN

          cannot open /dev/serial/by-id/usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B0018E2F56A-if00'"

          dieses Zeichen ist bei KOPIEREN reingekommen

          4e380bf2-2326-468a-ab9a-090207419de0-grafik.png

          der muss da raus

          @dp20eic ne nix udev.. der hat copy/paste gemacht und ein Sonderzeichen mitgenommen

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

            BTW:

            In der aktuellen Version von

            iob diag

            werden die /dev/serial-Links übrigens als Service direkt in kopierbarer Version ausgespuckt.

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

            Support us

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

            893
            Online

            32.1k
            Users

            80.6k
            Topics

            1.3m
            Posts

            4
            4
            133
            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