Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. zigbee nach update gelb

    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 nach update gelb

    This topic has been deleted. Only users with topic management privileges can see it.
    • M
      mpl1338 @arteck last edited by

      @arteck

      dein stick....

      bis vor dem update ging alles. Einstellungen nicht geändert

      zigbee.png

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

        @mpl1338 installiere bitte JETZT von GIT nicht das du eine buggy Version erwischt hast

        https://github.com/ioBroker/ioBroker.zigbee

        M 1 Reply Last reply Reply Quote 0
        • M
          mpl1338 @arteck last edited by

          @arteck zigbee2.png

          zigbee.0	2021-05-24 19:17:59.412	error	at /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/stream/lib/index.js:242:12
          zigbee.0	2021-05-24 19:17:59.412	error	at SerialPort._error (/opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/stream/lib/index.js:198:14)
          zigbee.0	2021-05-24 19:17:59.412	error	at SerialPort.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:134:49)
          zigbee.0	2021-05-24 19:17:59.412	error	at __awaiter (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:23:12)
          zigbee.0	2021-05-24 19:17:59.412	error	at new Promise (<anonymous>)
          zigbee.0	2021-05-24 19:17:59.412	error	at /opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:27:71
          zigbee.0	2021-05-24 19:17:59.412	error	at Generator.next (<anonymous>)
          zigbee.0	2021-05-24 19:17:59.412	error	at Znp.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:136:32)
          zigbee.0	2021-05-24 19:17:59.412	error	(4592) Error: Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'
          zigbee.0	2021-05-24 19:17:59.411	error	(4592) Failed to start Zigbee
          zigbee.0	2021-05-24 19:17:59.312	info	(4592) Installed Version: ioBroker/ioBroker.zigbee#931800aecb03758f9cf7d92a751609de574b1b37
          zigbee.0	2021-05-24 19:17:59.306	info	(4592) Starting Zigbee npm ...
          zigbee.0	2021-05-24 19:17:59.305	info	(4592) Try to reconnect. 1 attempts left
          zigbee.0	2021-05-24 19:17:49.304	error	at fulfilled (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/manager.js:24:58)
          zigbee.0	2021-05-24 19:17:49.304	error	at Generator.next (<anonymous>)
          zigbee.0	2021-05-24 19:17:49.304	error	at ZnpAdapterManager.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/manager.js:201:35)
          zigbee.0	2021-05-24 19:17:49.304	error	(4592) Error: startup failed - configuration-adapter mismatch - see logs above for more information
          zigbee.0	2021-05-24 19:17:49.303	error	(4592) Failed to start Zigbee
          zigbee.0	2021-05-24 19:17:49.303	error	(4592) Re-commissioning your network will require re-pairing of all devices!
          zigbee.0	2021-05-24 19:17:49.303	error	(4592) If you wish to re-commission your network, please remove coordinator backup at /opt/iobroker/iobroker-data/zigbee_0/nvbackup.json.
          zigbee.0	2021-05-24 19:17:49.303	error	(4592) Please update configuration to prevent further issues.
          zigbee.0	2021-05-24 19:17:49.303	error	(4592) - Channel List: configured=11, adapter=11
          zigbee.0	2021-05-24 19:17:49.303	error	(4592) - Network Key: configured=blabla, adapter=blabla
          zigbee.0	2021-05-24 19:17:49.303	error	(4592) - Extended PAN ID: configured=blabla, adapter=00124b00062d6098
          zigbee.0	2021-05-24 19:17:49.303	error	(4592) - PAN ID: configured=6754, adapter=6754
          zigbee.0	2021-05-24 19:17:49.302	error	(4592) Configuration is not consistent with adapter state/backup!
          zigbee.0	2021-05-24 19:17:47.677	info	(4592) Installed Version: ioBroker/ioBroker.zigbee#931800aecb03758f9cf7d92a751609de574b1b37
          zigbee.0	2021-05-24 19:17:47.576	info	(4592) Starting Zigbee npm ...
          zigbee.0	2021-05-24 19:17:47.528	info	(4592) starting. Version 1.5.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.22.1, js-controller: 3.2.16
          

          immernoch

          crunchip Thomas Braun 2 Replies Last reply Reply Quote 0
          • crunchip
            crunchip Forum Testing Most Active @mpl1338 last edited by

            @mpl1338 du fährst mit npm 7.x ??

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

              @mpl1338
              npm@7 ist auch nicht die empfohlene Version zu deinem node12.

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

                wie @crunchip gerade schreibt.... da haben wir das Problem

                1 Reply Last reply Reply Quote 0
                • M
                  mpl1338 last edited by

                  update auf 7 erfolgte erst eben.

                  zurück zu 6:

                  which nodejs node npm && nodejs -v && node -v && npm -v && apt policy nodejs
                  /usr/bin/nodejs
                  /usr/bin/node
                  /usr/bin/npm
                  v12.22.1
                  v12.22.1
                  6.14.13
                  nodejs:
                    Installed: 12.22.1-1nodesource1
                    Candidate: 12.22.1-1nodesource1
                    Version table:
                   *** 12.22.1-1nodesource1 500
                          500 https://deb.nodesource.com/node_12.x buster/main amd64 Packages
                          100 /var/lib/dpkg/status
                       10.24.0~dfsg-1~deb10u1 500
                          500 http://ftp.debian.org/debian buster/main amd64 Packages
                          500 http://security.debian.org buster/updates/main amd64 Packages
                  
                  zigbee.0	2021-05-24 19:41:43.508	error	at /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/stream/lib/index.js:242:12
                  zigbee.0	2021-05-24 19:41:43.508	error	at SerialPort._error (/opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/stream/lib/index.js:198:14)
                  zigbee.0	2021-05-24 19:41:43.508	error	at SerialPort.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:134:49)
                  zigbee.0	2021-05-24 19:41:43.508	error	at __awaiter (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:23:12)
                  zigbee.0	2021-05-24 19:41:43.508	error	at new Promise (<anonymous>)
                  zigbee.0	2021-05-24 19:41:43.508	error	at /opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:27:71
                  zigbee.0	2021-05-24 19:41:43.508	error	at Generator.next (<anonymous>)
                  zigbee.0	2021-05-24 19:41:43.508	error	at Znp.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:136:32)
                  zigbee.0	2021-05-24 19:41:43.508	error	(5962) Error: Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'
                  zigbee.0	2021-05-24 19:41:43.508	error	(5962) Failed to start Zigbee
                  
                  iobroker
                  Platform
                  linux
                  Betriebssystem
                  linux
                  Architektur
                  x64
                  CPUs
                  2
                  Geschwindigkeit
                  3600 MHz
                  Modell
                  Intel(R) Core(TM) i3-8109U CPU @ 3.00GHz
                  RAM
                  4 GB
                  System Betriebszeit
                  4 T. 23:16:12
                  Node.js
                  v12.22.1
                  Festplatte Größe
                  12 GB
                  Festplatte frei
                  7.81 GB
                  Anzahl der Adapter
                  411
                  NPM
                  v6.14.13
                  Betriebszeit
                  00:02:58
                  Aktive Instanzen
                  25
                  Hostname
                  iobroker
                  

                  und problem immernoch da

                  Thomas Braun crunchip 2 Replies Last reply Reply Quote 0
                  • Thomas Braun
                    Thomas Braun Most Active @mpl1338 last edited by

                    @mpl1338 Was liegt denn da drauf?

                    sudo lsof /dev/ttyACM0
                    
                    M 1 Reply Last reply Reply Quote 0
                    • M
                      mpl1338 @Thomas Braun last edited by

                      @thomas-braun said in zigbee nach update gelb:

                      @mpl1338 Was liegt denn da drauf?

                      sudo lsof /dev/ttyACM0
                      
                      sudo lsof /dev/ttyACM0
                      COMMAND  PID     USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
                      node    1305 iobroker   27uW  CHR  166,0      0t0  361 /dev/ttyACM0
                      
                      Thomas Braun 1 Reply Last reply Reply Quote 0
                      • Thomas Braun
                        Thomas Braun Most Active @mpl1338 last edited by

                        @mpl1338
                        Stop den Adapter,

                        sudo -u iobroker kill 1305
                        

                        Adapter starten.

                        1 Reply Last reply Reply Quote 0
                        • crunchip
                          crunchip Forum Testing Most Active @mpl1338 last edited by

                          @mpl1338 proxmox selbst mal neu gestartet, bzw stick mal abgesteckt?

                          M 1 Reply Last reply Reply Quote 0
                          • M
                            mpl1338 @crunchip last edited by

                            @crunchip

                            mehrmals

                            @Thomas-Braun

                            keine besserung

                            M Thomas Braun 2 Replies Last reply Reply Quote 0
                            • M
                              mpl1338 @mpl1338 last edited by

                              downgrade auf 1.4.1 und es geht wieder....

                              crunchip 1 Reply Last reply Reply Quote 0
                              • crunchip
                                crunchip Forum Testing Most Active @mpl1338 last edited by

                                @mpl1338 seltsam

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

                                  @mpl1338

                                  iobroker stop
                                  

                                  Damn nochmal schauen ob das File noch offen ist, process ggf. killen,

                                  iobroker start
                                  
                                  M 1 Reply Last reply Reply Quote 0
                                  • M
                                    mpl1338 @Thomas Braun last edited by

                                    @thomas-braun

                                    bin jetzt auf 1.4.1 runter - da läufts wieder

                                    1 Reply Last reply Reply Quote 0
                                    • P
                                      Peter213 last edited by

                                      Habe auch gerade Update gemacht und der Adapter bleibt rot. Folgende Fehler habe ich:

                                      6dde7cd6-87bc-4cd7-aa77-2d8581ff61b1-image.png

                                      Hat einer eine Idee?

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

                                        @peter213 multihost ?

                                        P 1 Reply Last reply Reply Quote 0
                                        • P
                                          Peter213 @arteck last edited by

                                          @arteck nein. Nuc mit Proxmox als VM mit Conbee II Stick. Mit 1.4.1 läuft es wieder wie bei den anderen. Bin vor kurzem umgezogen von PI auf NUC. Bis jetzt lief auch alles. Erst gestern mit dem Update auf 1.5.5 kam das Problem. mit 1.5.4 war es auch noch in Ordnung. Waren allerdings gestern noch ein paar andere Updates dabei.

                                          1 Reply Last reply Reply Quote 0
                                          • A
                                            Allodo last edited by Allodo

                                            EDIT:
                                            Bin auch zurück auf 1.4.1 und der Adapter ist wieder grün!

                                            Ich habe auch das Problem, dass mein Zigbee-Adapter seit gestern gelb bleibt 😞
                                            Gestern gab es, glaube ich, ein Update auf die jetzige Version 1.5.6.
                                            Der Zigbee-Stick (CC2538+CC2592) wird von iobroker nicht mehr erkannt.

                                            Von mir wurde keinen Änderungen an den Einstellungen vorgenommen.

                                            root@raspberrypi:~# sudo lsof /dev/ttyACM0
                                            COMMAND  PID     USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
                                            node    4119 iobroker   27uW  CHR  166,0      0t0  489 /dev/ttyACM0
                                            

                                            Und hier der Log-File:

                                            zigbee.0	2021-06-01 17:33:17.898	error	(4119) Error herdsman start
                                            zigbee.0	2021-06-01 17:33:17.898	error	(4119) Failed to start Zigbee
                                            zigbee.0	2021-06-01 17:33:17.897	error	(4119) Starting zigbee-herdsman problem : "startup failed - configuration-adapter mismatch - see logs above for more information"
                                            zigbee.0	2021-06-01 17:33:17.897	error	(4119) Re-commissioning your network will require re-pairing of all devices!
                                            zigbee.0	2021-06-01 17:33:17.896	error	(4119) If you wish to re-commission your network, please remove coordinator backup at /opt/iobroker/iobroker-data/zigbee_0/nvbackup.json.
                                            zigbee.0	2021-06-01 17:33:17.896	error	(4119) Please update configuration to prevent further issues.
                                            zigbee.0	2021-06-01 17:33:17.895	error	(4119) - Channel List: configured=11, adapter=
                                            zigbee.0	2021-06-01 17:33:17.895	error	(4119) - Network Key: configured=01030507090b0d0f00020406080a0c0d, adapter=01030507090b0d0f00020406080a0c0d
                                            zigbee.0	2021-06-01 17:33:17.894	error	(4119) - Extended PAN ID: configured=00124b001940c090, adapter=0000000000000000
                                            zigbee.0	2021-06-01 17:33:17.894	error	(4119) - PAN ID: configured=6754, adapter=65535
                                            zigbee.0	2021-06-01 17:33:17.893	error	(4119) Configuration is not consistent with adapter state/backup!
                                            

                                            Ein Reboot der RPi4 brachte keinen Erfolg. Was kann ich jetzt tun, möglichst ohne alle Geräte wieder mühselig anlernen zu müssen?

                                            jogge Thomas Braun 2 Replies 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

                                            930
                                            Online

                                            31.9k
                                            Users

                                            80.1k
                                            Topics

                                            1.3m
                                            Posts

                                            12
                                            50
                                            2989
                                            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