Skip to content
  • Home
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Standard: (Kein Skin)
  • Kein Skin
Einklappen
ioBroker Logo

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. Einsteigerfragen
  4. Zigbee Adapter stürzt ständig ab

NEWS

  • UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?
    apollon77A
    apollon77
    48
    3
    8.9k

  • Monatsrückblick – September 2025
    BluefoxB
    Bluefox
    13
    1
    2.3k

  • Neues Video "KI im Smart Home" - ioBroker plus n8n
    BluefoxB
    Bluefox
    16
    1
    3.5k

Zigbee Adapter stürzt ständig ab

Geplant Angeheftet Gesperrt Verschoben Einsteigerfragen
61 Beiträge 4 Kommentatoren 5.5k Aufrufe 4 Watching
  • Älteste zuerst
  • Neuste zuerst
  • Meiste Stimmen
Antworten
  • In einem neuen Thema antworten
Anmelden zum Antworten
Dieses Thema wurde gelöscht. Nur Nutzer mit entsprechenden Rechten können es sehen.
  • K klaris

    @thomas-braun sagte in Zigbee Adapter stürzt ständig ab:

    uname -m && which nodejs node npm && nodejs -v && node -v && npm -v && whoami && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs

    pi@raspberrypi:~ $ uname -m && which nodejs node npm && nodejs -v && node -v &&                                                                                                                                                                                                                                              npm -v && whoami && pwd && sudo apt update &> /dev/null && sudo apt update && ap                                                                                                                                                                                                                                             t policy nodejs
    armv7l
    /usr/bin/nodejs
    /usr/bin/node
    /usr/bin/npm
    v14.19.3
    v14.19.3
    6.14.17
    pi
    /home/pi
    Hit:1 http://archive.raspberrypi.org/debian bullseye InRelease
    Hit:2 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
    Get:3 https://phoscon.de/apt/deconz bullseye InRelease [2,873 B]
    Hit:4 https://deb.nodesource.com/node_14.x bullseye InRelease
    Fetched 2,873 B in 4s (693 B/s)
    Reading package lists... Done
    Building dependency tree... Done
    Reading state information... Done
    All packages are up to date.
    N: Ignoring file 'nodesource.list.save.1' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension
    N: Ignoring file 'nodesource.list.save.5' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension
    N: Ignoring file 'nodesource.list.save.4' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension
    N: Ignoring file 'nodesource.list.save.2' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension
    N: Ignoring file 'nodesource.list.save.3' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension
    nodejs:
      Installed: 14.19.3-deb-1nodesource1
      Candidate: 14.19.3-deb-1nodesource1
      Version table:
     *** 14.19.3-deb-1nodesource1 500
            500 https://deb.nodesource.com/node_14.x bullseye/main armhf Packages
            100 /var/lib/dpkg/status
         12.22.5~dfsg-2~11u1 500
            500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages
    N: Ignoring file 'nodesource.list.save.1' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension
    N: Ignoring file 'nodesource.list.save.5' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension
    N: Ignoring file 'nodesource.list.save.4' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension
    N: Ignoring file 'nodesource.list.save.2' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension
    N: Ignoring file 'nodesource.list.save.3' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension
    
    
    Thomas BraunT Online
    Thomas BraunT Online
    Thomas Braun
    Most Active
    schrieb am zuletzt editiert von
    #40

    @klaris

    Der Fragmente sind ja immer noch da...

    sudo rm /etc/apt/sources.list.d/nodesource.list.sav*
    

    Linux-Werkzeugkasten:
    https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
    NodeJS Fixer Skript:
    https://forum.iobroker.net/topic/68035/iob-node-fix-skript
    iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

    K 1 Antwort Letzte Antwort
    0
    • Thomas BraunT Thomas Braun

      @klaris

      Der Fragmente sind ja immer noch da...

      sudo rm /etc/apt/sources.list.d/nodesource.list.sav*
      
      K Offline
      K Offline
      klaris
      schrieb am zuletzt editiert von
      #41

      @thomas-braun :+1: :+1: :+1: :+1:

      pi@raspberrypi:~ $ sudo rm /etc/apt/sources.list.d/nodesource.list.sav*
      pi@raspberrypi:~ $ uname -m && which nodejs node npm && nodejs -v && node -v &&                                                                                                                                                                                                                                              npm -v && whoami && pwd && sudo apt update &> /dev/null && sudo apt update && ap                                                                                                                                                                                                                                             t policy nodejs
      armv7l
      /usr/bin/nodejs
      /usr/bin/node
      /usr/bin/npm
      v14.19.3
      v14.19.3
      6.14.17
      pi
      /home/pi
      Hit:1 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
      Hit:2 http://archive.raspberrypi.org/debian bullseye InRelease
      Hit:3 https://deb.nodesource.com/node_14.x bullseye InRelease
      Get:4 https://phoscon.de/apt/deconz bullseye InRelease [2,873 B]
      Fetched 2,873 B in 3s (942 B/s)
      Reading package lists... Done
      Building dependency tree... Done
      Reading state information... Done
      All packages are up to date.
      nodejs:
        Installed: 14.19.3-deb-1nodesource1
        Candidate: 14.19.3-deb-1nodesource1
        Version table:
       *** 14.19.3-deb-1nodesource1 500
              500 https://deb.nodesource.com/node_14.x bullseye/main armhf Packages
              100 /var/lib/dpkg/status
           12.22.5~dfsg-2~11u1 500
              500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages
      
      
      Thomas BraunT 1 Antwort Letzte Antwort
      0
      • K klaris

        @thomas-braun :+1: :+1: :+1: :+1:

        pi@raspberrypi:~ $ sudo rm /etc/apt/sources.list.d/nodesource.list.sav*
        pi@raspberrypi:~ $ uname -m && which nodejs node npm && nodejs -v && node -v &&                                                                                                                                                                                                                                              npm -v && whoami && pwd && sudo apt update &> /dev/null && sudo apt update && ap                                                                                                                                                                                                                                             t policy nodejs
        armv7l
        /usr/bin/nodejs
        /usr/bin/node
        /usr/bin/npm
        v14.19.3
        v14.19.3
        6.14.17
        pi
        /home/pi
        Hit:1 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
        Hit:2 http://archive.raspberrypi.org/debian bullseye InRelease
        Hit:3 https://deb.nodesource.com/node_14.x bullseye InRelease
        Get:4 https://phoscon.de/apt/deconz bullseye InRelease [2,873 B]
        Fetched 2,873 B in 3s (942 B/s)
        Reading package lists... Done
        Building dependency tree... Done
        Reading state information... Done
        All packages are up to date.
        nodejs:
          Installed: 14.19.3-deb-1nodesource1
          Candidate: 14.19.3-deb-1nodesource1
          Version table:
         *** 14.19.3-deb-1nodesource1 500
                500 https://deb.nodesource.com/node_14.x bullseye/main armhf Packages
                100 /var/lib/dpkg/status
             12.22.5~dfsg-2~11u1 500
                500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages
        
        
        Thomas BraunT Online
        Thomas BraunT Online
        Thomas Braun
        Most Active
        schrieb am zuletzt editiert von
        #42

        @klaris

        iobroker update -i
        

        Linux-Werkzeugkasten:
        https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
        NodeJS Fixer Skript:
        https://forum.iobroker.net/topic/68035/iob-node-fix-skript
        iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

        K 1 Antwort Letzte Antwort
        0
        • Thomas BraunT Thomas Braun

          @klaris

          iobroker update -i
          
          K Offline
          K Offline
          klaris
          schrieb am zuletzt editiert von
          #43

          @thomas-braun

          Adapter    "zigbee"       : 1.7.5    , installed 1.7.5
          
          

          komisch ist nur wenn ich im iobroker unter adapter gehe steht :
          Verfügbare Version:1.7.5 Installierte Version:1.6.18 obwohl ich ja 1.7.5 instaliert habe ...aber läuft ... das ist wichtig

          Thomas BraunT 1 Antwort Letzte Antwort
          0
          • K klaris

            @thomas-braun

            Adapter    "zigbee"       : 1.7.5    , installed 1.7.5
            
            

            komisch ist nur wenn ich im iobroker unter adapter gehe steht :
            Verfügbare Version:1.7.5 Installierte Version:1.6.18 obwohl ich ja 1.7.5 instaliert habe ...aber läuft ... das ist wichtig

            Thomas BraunT Online
            Thomas BraunT Online
            Thomas Braun
            Most Active
            schrieb am zuletzt editiert von
            #44

            @klaris

            Nix kürzen...

            Zum dritten Mal:

            iobroker update -i
            

            Linux-Werkzeugkasten:
            https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
            NodeJS Fixer Skript:
            https://forum.iobroker.net/topic/68035/iob-node-fix-skript
            iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

            K 1 Antwort Letzte Antwort
            0
            • Thomas BraunT Thomas Braun

              @klaris

              Nix kürzen...

              Zum dritten Mal:

              iobroker update -i
              
              K Offline
              K Offline
              klaris
              schrieb am zuletzt editiert von
              #45

              @thomas-braun

              pi@raspberrypi:~ $ iobroker update -i
              Used repository: stable
              Adapter    "admin"        : 5.3.8    , installed 5.3.8
              Adapter    "alexa2"       : 3.11.2   , installed 3.11.2
              Adapter    "backitup"     : 2.4.6    , installed 2.4.6
              Adapter    "countdown"    : 1.2.5    , installed 1.2.5
              Adapter    "daswetter"    : 3.1.2    , installed 3.1.2
              Adapter    "discovery"    : 3.0.3    , installed 3.0.3
              Adapter    "icons-mfd-png": 1.1.0    , installed 1.1.0
              Adapter    "icons-mfd-svg": 1.1.0    , installed 1.1.0
              Adapter    "info"         : 1.9.19   , installed 1.9.19
              Adapter    "iot"          : 1.11.4   , installed 1.11.4
              Adapter    "javascript"   : 5.7.0    , installed 5.7.0
              Controller "js-controller": 4.0.23   , installed 4.0.23
              Adapter    "meross"       : 1.10.5   , installed 1.10.5
              Adapter    "ping"         : 1.5.3    , installed 1.5.3
              Adapter    "shelly"       : 5.3.2    , installed 5.3.2
              Adapter    "simple-api"   : 2.6.5    , installed 2.7.0
              Adapter    "socketio"     : 4.2.0    , installed 4.2.0
              Adapter    "sonoff"       : 2.5.1    , installed 2.5.1
              Adapter    "telegram"     : 1.12.6   , installed 1.12.6
              Adapter    "tr-064"       : 4.2.16   , installed 4.2.16
              Adapter    "vis"          : 1.4.15   , installed 1.4.15
              Adapter    "vis-hqwidgets": 1.2.0    , installed 1.2.0
              Adapter    "vis-metro"    : 1.2.0    , installed 1.2.0
              Adapter    "vis-timeandweather": 1.1.7, installed 1.1.7
              Adapter    "web"          : 4.3.0    , installed 4.3.0
              Adapter    "whatsapp-cmb" : 0.2.2    , installed 0.2.2
              Adapter    "ws"           : 1.3.0    , installed 1.3.0
              Adapter    "zigbee"       : 1.7.5    , installed 1.7.5
              
              
              Thomas BraunT 1 Antwort Letzte Antwort
              0
              • K klaris

                @thomas-braun

                pi@raspberrypi:~ $ iobroker update -i
                Used repository: stable
                Adapter    "admin"        : 5.3.8    , installed 5.3.8
                Adapter    "alexa2"       : 3.11.2   , installed 3.11.2
                Adapter    "backitup"     : 2.4.6    , installed 2.4.6
                Adapter    "countdown"    : 1.2.5    , installed 1.2.5
                Adapter    "daswetter"    : 3.1.2    , installed 3.1.2
                Adapter    "discovery"    : 3.0.3    , installed 3.0.3
                Adapter    "icons-mfd-png": 1.1.0    , installed 1.1.0
                Adapter    "icons-mfd-svg": 1.1.0    , installed 1.1.0
                Adapter    "info"         : 1.9.19   , installed 1.9.19
                Adapter    "iot"          : 1.11.4   , installed 1.11.4
                Adapter    "javascript"   : 5.7.0    , installed 5.7.0
                Controller "js-controller": 4.0.23   , installed 4.0.23
                Adapter    "meross"       : 1.10.5   , installed 1.10.5
                Adapter    "ping"         : 1.5.3    , installed 1.5.3
                Adapter    "shelly"       : 5.3.2    , installed 5.3.2
                Adapter    "simple-api"   : 2.6.5    , installed 2.7.0
                Adapter    "socketio"     : 4.2.0    , installed 4.2.0
                Adapter    "sonoff"       : 2.5.1    , installed 2.5.1
                Adapter    "telegram"     : 1.12.6   , installed 1.12.6
                Adapter    "tr-064"       : 4.2.16   , installed 4.2.16
                Adapter    "vis"          : 1.4.15   , installed 1.4.15
                Adapter    "vis-hqwidgets": 1.2.0    , installed 1.2.0
                Adapter    "vis-metro"    : 1.2.0    , installed 1.2.0
                Adapter    "vis-timeandweather": 1.1.7, installed 1.1.7
                Adapter    "web"          : 4.3.0    , installed 4.3.0
                Adapter    "whatsapp-cmb" : 0.2.2    , installed 0.2.2
                Adapter    "ws"           : 1.3.0    , installed 1.3.0
                Adapter    "zigbee"       : 1.7.5    , installed 1.7.5
                
                
                Thomas BraunT Online
                Thomas BraunT Online
                Thomas Braun
                Most Active
                schrieb am zuletzt editiert von
                #46

                @klaris

                iobroker upload all
                

                Und starte den Browser mal neu. Zumindest die Admin-Seite nochmal richtig neuladen.

                Linux-Werkzeugkasten:
                https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                NodeJS Fixer Skript:
                https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                K 1 Antwort Letzte Antwort
                0
                • Thomas BraunT Thomas Braun

                  @klaris

                  iobroker upload all
                  

                  Und starte den Browser mal neu. Zumindest die Admin-Seite nochmal richtig neuladen.

                  K Offline
                  K Offline
                  klaris
                  schrieb am zuletzt editiert von
                  #47

                  @thomas-braun :+1: läuft

                  K 1 Antwort Letzte Antwort
                  0
                  • K klaris

                    @thomas-braun :+1: läuft

                    K Offline
                    K Offline
                    klaris
                    schrieb am zuletzt editiert von klaris
                    #48

                    @klaris heute morgen ..leider das gleiche ...

                    daswetter.0
                    	7089	2022-06-03 09:00:35.846	info	Terminated (ADAPTER_REQUESTED_TERMINATION): All data handled, adapter stopped until next scheduled moment
                    daswetter.0
                    	7089	2022-06-03 09:00:29.165	info	still wrong data structure from server received! repaired...
                    daswetter.0
                    	7089	2022-06-03 09:00:03.641	info	starting. Version 3.1.2 in /opt/iobroker/node_modules/iobroker.daswetter, node: v14.19.3, js-controller: 4.0.23
                    host.raspberrypi
                    		2022-06-03 09:00:00.150	info	instance system.adapter.daswetter.0 started with pid 7089
                    host.raspberrypi
                    		2022-06-03 08:59:39.971	warn	Do not restart adapter system.adapter.zigbee.0 because restart loop detected
                    host.raspberrypi
                    		2022-06-03 08:59:39.970	info	Restart adapter system.adapter.zigbee.0 because enabled
                    host.raspberrypi
                    		2022-06-03 08:59:39.969	error	instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
                    host.raspberrypi
                    		2022-06-03 08:59:39.968	info	Restart adapter system.adapter.zigbee.0 because enabled
                    host.raspberrypi
                    		2022-06-03 08:59:39.967	error	instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
                    host.raspberrypi
                    		2022-06-03 08:59:39.967	error	Caught by controller[3]: at /opt/iobroker/node_modules/@serialport/stream/lib/index.js:242:12
                    host.raspberrypi
                    		2022-06-03 08:59:39.967	error	Caught by controller[3]: at SerialPort._error (/opt/iobroker/node_modules/@serialport/stream/lib/index.js:198:14)
                    host.raspberrypi
                    		2022-06-03 08:59:39.966	error	Caught by controller[3]: at SerialPort.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/deconz/driver/driver.ts:182:28)
                    host.raspberrypi
                    		2022-06-03 08:59:39.966	error	Caught by controller[3]: Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0'
                    host.raspberrypi
                    		2022-06-03 08:59:39.965	error	Caught by controller[2]: at /opt/iobroker/node_modules/@serialport/stream/lib/index.js:242:12
                    host.raspberrypi
                    		2022-06-03 08:59:39.965	error	Caught by controller[2]: at SerialPort._error (/opt/iobroker/node_modules/@serialport/stream/lib/index.js:198:14)
                    host.raspberrypi
                    		2022-06-03 08:59:39.965	error	Caught by controller[2]: at SerialPort.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/deconz/driver/driver.ts:182:28)
                    host.raspberrypi
                    		2022-06-03 08:59:39.964	error	Caught by controller[2]: Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0'
                    host.raspberrypi
                    		2022-06-03 08:59:39.964	error	Caught by controller[1]: 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:
                    host.raspberrypi
                    		2022-06-03 08:59:39.963	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
                    	7060	2022-06-03 08:59:39.207	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
                    zigbee.0
                    	7060	2022-06-03 08:59:39.204	info	terminating
                    zigbee.0
                    	7060	2022-06-03 08:59:39.195	info	Zigbee: disabling joining new devices.
                    zigbee.0
                    	7060	2022-06-03 08:59:39.064	info	cleaned everything up...
                    zigbee.0
                    	7060	2022-06-03 08:59:39.050	error	Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0'
                    zigbee.0
                    	7060	2022-06-03 08:59:39.050	error	Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0' at SerialPort.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/deconz/driver/driver.ts:182:28) at SerialPort._error (/opt/iobroker/node_modules/@serialport/stream/lib/index.js:198:14) at /opt/iobroker/node_modules/@serialport/stream/lib/index.js:242:12
                    zigbee.0
                    	7060	2022-06-03 08:59:39.048	error	unhandled promise rejection: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0'
                    zigbee.0
                    	7060	2022-06-03 08:59:39.047	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().
                    web.0
                    	2689	2022-06-03 08:59:33.060	info	<== Disconnect system.user.admin from ::ffff:192.168.178.40
                    zigbee.0
                    	7060	2022-06-03 08:59:19.680	error	Error herdsman start
                    zigbee.0
                    	7060	2022-06-03 08:59:19.679	error	Failed to start Zigbee
                    zigbee.0
                    	7060	2022-06-03 08:59:19.676	error	Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0'"
                    zigbee.0
                    	7060	2022-06-03 08:59:19.393	info	Installed Version: iobroker.zigbee@1.7.5
                    zigbee.0
                    	7060	2022-06-03 08:59:19.367	info	Starting Zigbee npm ...
                    zigbee.0
                    	7060	2022-06-03 08:59:19.365	info	Try to reconnect. 1 attempts left
                    zigbee.0
                    	7060	2022-06-03 08:59:09.371	info	Installed Version: iobroker.zigbee@1.7.5
                    zigbee.0
                    	7060	2022-06-03 08:59:09.359	error	Error herdsman start
                    zigbee.0
                    	7060	2022-06-03 08:59:09.357	error	Failed to start Zigbee
                    zigbee.0
                    	7060	2022-06-03 08:59:09.355	error	Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0'"
                    zigbee.0
                    	7060	2022-06-03 08:59:08.095	info	Starting Zigbee npm ...
                    zigbee.0
                    	7060	2022-06-03 08:59:08.090	info	delete old Backup files. keep only last 10
                    zigbee.0
                    	7060	2022-06-03 08:59:07.908	info	starting. Version 1.7.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v14.19.3, js-controller: 4.0.23
                    host.raspberrypi
                    		2022-06-03 08:59:00.487	info	instance system.adapter.zigbee.0 started with pid 7060
                    host.raspberrypi
                    		2022-06-03 08:59:00.484	info	instance system.adapter.zigbee.0 started with pid 7060
                    host.raspberrypi
                    		2022-06-03 08:59:00.173	info	"system.adapter.zigbee.0" enabled
                    host.raspberrypi
                    		2022-06-03 08:58:59.002	info	instance system.adapter.zigbee.0 terminated with code null ()
                    host.raspberrypi
                    		2022-06-03 08:58:59.001	warn	instance system.adapter.zigbee.0 terminated due to SIGTERM
                    host.raspberrypi
                    		2022-06-03 08:58:58.900	info	stopInstance system.adapter.zigbee.0 killing pid 7053
                    host.raspberrypi
                    		2022-06-03 08:58:57.898	info	stopInstance system.adapter.zigbee.0 send kill signal
                    host.raspberrypi
                    		2022-06-03 08:58:57.822	info	stopInstance system.adapter.zigbee.0 (force=false, process=true)
                    host.raspberrypi
                    		2022-06-03 08:58:57.821	info	"system.adapter.zigbee.0" disabled
                    host.raspberrypi
                    		2022-06-03 08:58:57.148	info	stopInstance system.adapter.zigbee.0 send kill signal
                    host.raspberrypi
                    		2022-06-03 08:58:57.075	info	stopInstance system.adapter.zigbee.0 (force=false, process=true)
                    host.raspberrypi
                    		2022-06-03 08:58:56.777	info	instance system.adapter.zigbee.0 started with pid 7053
                    host.raspberrypi
                    		2022-06-03 08:58:54.713	info	instance system.adapter.zigbee.0 terminated with code null ()
                    host.raspberrypi
                    		2022-06-03 08:58:54.712	warn	instance system.adapter.zigbee.0 terminated due to SIGTERM
                    host.raspberrypi
                    		2022-06-03 08:58:54.607	info	stopInstance system.adapter.zigbee.0 killing pid 7046
                    host.raspberrypi
                    		2022-06-03 08:58:53.605	info	stopInstance system.adapter.zigbee.0 send kill signal
                    host.raspberrypi
                    		2022-06-03 08:58:53.592	info	stopInstance system.adapter.zigbee.0 (force=false, process=true)
                    host.raspberrypi
                    		2022-06-03 08:58:52.424	info	instance system.adapter.zigbee.0 started with pid 7046
                    host.raspberrypi
                    		2022-06-03 08:58:26.981	info	Restart adapter system.adapter.zigbee.0 because enabled
                    host.raspberrypi
                    		2022-06-03 08:58:26.980	error	instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
                    host.raspberrypi
                    		2022-06-03 08:58:26.979	error	Caught by controller[0]: at /opt/iobroker/node_modules/@serialport/stream/lib/index.js:242:12
                    host.raspberrypi
                    		2022-06-03 08:58:26.979	error	Caught by controller[0]: at SerialPort._error (/opt/iobroker/node_modules/@serialport/stream/lib/index.js:198:14)
                    host.raspberrypi
                    		2022-06-03 08:58:26.978	error	Caught by controller[0]: at SerialPort.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/deconz/driver/driver.ts:182:28)
                    host.raspberrypi
                    		2022-06-03 08:58:26.977	error	Caught by controller[0]: Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0'
                    host.raspberrypi
                    		2022-06-03 08:58:26.976	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
                    	7029	2022-06-03 08:58:26.300	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
                    zigbee.0
                    	7029	2022-06-03 08:58:26.297	info	terminating
                    zigbee.0
                    	7029	2022-06-03 08:58:26.278	info	Zigbee: disabling joining new devices.
                    zigbee.0
                    	7029	2022-06-03 08:58:26.116	info	cleaned everything up...
                    zigbee.0
                    	7029	2022-06-03 08:58:26.097	error	Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0'
                    zigbee.0
                    	7029	2022-06-03 08:58:26.096	error	Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0' at SerialPort.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/deconz/driver/driver.ts:182:28) at SerialPort._error (/opt/iobroker/node_modules/@serialport/stream/lib/index.js:198:14) at /opt/iobroker/node_modules/@serialport/stream/lib/index.js:242:12
                    zigbee.0
                    	7029	2022-06-03 08:58:26.093	error	unhandled promise rejection: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0'
                    zigbee.0
                    	7029	2022-06-03 08:58:26.091	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().
                    host.raspberrypi
                    		2022-06-03 08:58:13.379	error	instance system.adapter.daswetter.0 terminated with code 15 (UNKNOWN_ERROR)
                    daswetter.0
                    	7013	2022-06-03 08:58:13.348	error	Cannot check object existence of "daswetter.0.NextHours2.Location_1.Day_1.Hour_3.symbol": Connection is closed.
                    daswetter.0
                    	7013	2022-06-03 08:58:13.345	error	exception in await insertIntoList [Error: Could not check object existence of daswetter.0.NextHours2.Location_1.Day_1.current.temp: Cannot check object existence of "daswetter.0.NextHours2.Location_1.Day_1.current.temp": Connection is closed.]
                    daswetter.0
                    	7013	2022-06-03 08:58:13.343	error	Cannot check object existence of "daswetter.0.NextHours2.Location_1.Day_1.current.temp": Connection is closed.
                    daswetter.0
                    	7013	2022-06-03 08:58:13.340	error	exception in await insertIntoList [Error: Could not check object existence of daswetter.0.NextHours2.Location_1.Day_1.Hour_3.temp: Cannot check object existence of "daswetter.0.NextHours2.Location_1.Day_1.Hour_3.temp": Connection is closed.]
                    daswetter.0
                    	7013	2022-06-03 08:58:13.338	error	Cannot check object existence of "daswetter.0.NextHours2.Location_1.Day_1.Hour_3.temp": Connection is closed.
                    daswetter.0
                    	7013	2022-06-03 08:58:13.336	error	exception in await insertIntoList [Error: Could not check object existence of daswetter.0.NextHours2.Location_1.Day_1.current.hour: Cannot check object existence of "daswetter.0.NextHours2.Location_1.Day_1.current.hour": Connection is closed.]
                    daswetter.0
                    	7013	2022-06-03 08:58:13.333	error	Cannot check object existence of "daswetter.0.NextHours2.Location_1.Day_1.current.hour": Connection is closed.
                    daswetter.0
                    	7013	2022-06-03 08:58:13.329	error	exception in await insertIntoList [Error: DB closed]
                    daswetter.0
                    	7013	2022-06-03 08:58:13.325	warn	get state error: Connection is closed.
                    daswetter.0
                    	7013	2022-06-03 08:58:12.808	warn	Terminated (UNKNOWN_ERROR): Without reason
                    daswetter.0
                    	7013	2022-06-03 08:58:12.805	error	force terminate
                    daswetter.0
                    	7013	2022-06-03 08:58:12.738	info	still wrong data structure from server received! repaired...
                    zigbee.0
                    	7029	2022-06-03 08:58:06.750	error	Error herdsman start
                    zigbee.0
                    	7029	2022-06-03 08:58:06.749	error	Failed to start Zigbee
                    zigbee.0
                    	7029	2022-06-03 08:58:06.745	error	Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0'"
                    zigbee.0
                    	7029	2022-06-03 08:58:06.424	info	Installed Version: iobroker.zigbee@1.7.5
                    zigbee.0
                    	7029	2022-06-03 08:58:06.386	info	Starting Zigbee npm ...
                    zigbee.0
                    	7029	2022-06-03 08:58:06.384	info	Try to reconnect. 1 attempts left
                    zigbee.0
                    	7029	2022-06-03 08:57:56.384	info	Installed Version: iobroker.zigbee@1.7.5
                    zigbee.0
                    	7029	2022-06-03 08:57:56.378	error	Error herdsman start
                    zigbee.0
                    	7029	2022-06-03 08:57:56.377	error	Failed to start Zigbee
                    zigbee.0
                    	7029	2022-06-03 08:57:56.375	error	Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0'"
                    zigbee.0
                    	7029	2022-06-03 08:57:54.880	info	Starting Zigbee npm ...
                    zigbee.0
                    	7029	2022-06-03 08:57:54.873	info	delete old Backup files. keep only last 10
                    zigbee.0
                    	7029	2022-06-03 08:57:54.612	info	starting. Version 1.7.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v14.19.3, js-controller: 4.0.23
                    host.raspberrypi
                    		2022-06-03 08:57:44.648	info	instance system.adapter.zigbee.0 started with pid 7029
                    daswetter.0
                    	7013	2022-06-03 08:57:12.755	info	starting. Version 3.1.2 in /opt/iobroker/node_modules/iobroker.daswetter, node: v14.19.3, js-controller: 4.0.23
                    web.0
                    	2689	2022-06-03 08:57:09.172	info	==> Connected system.user.admin from ::ffff:192.168.178.40
                    iot.2
                    	983	2022-06-03 08:57:07.961	info	Connection changed: connect
                    host.raspberrypi
                    		2022-06-03 08:57:06.801	info	instance system.adapter.daswetter.0 started with pid 7013
                    host.raspberrypi
                    		2022-06-03 08:57:06.681	info	Restart adapter system.adapter.zigbee.0 because enabled
                    host.raspberrypi
                    		2022-06-03 08:57:06.674	info	instance system.adapter.zigbee.0 terminated with code NaN ()
                    host.raspberrypi
                    	
                    
                    arteckA Thomas BraunT 2 Antworten Letzte Antwort
                    0
                    • K klaris

                      @klaris heute morgen ..leider das gleiche ...

                      daswetter.0
                      	7089	2022-06-03 09:00:35.846	info	Terminated (ADAPTER_REQUESTED_TERMINATION): All data handled, adapter stopped until next scheduled moment
                      daswetter.0
                      	7089	2022-06-03 09:00:29.165	info	still wrong data structure from server received! repaired...
                      daswetter.0
                      	7089	2022-06-03 09:00:03.641	info	starting. Version 3.1.2 in /opt/iobroker/node_modules/iobroker.daswetter, node: v14.19.3, js-controller: 4.0.23
                      host.raspberrypi
                      		2022-06-03 09:00:00.150	info	instance system.adapter.daswetter.0 started with pid 7089
                      host.raspberrypi
                      		2022-06-03 08:59:39.971	warn	Do not restart adapter system.adapter.zigbee.0 because restart loop detected
                      host.raspberrypi
                      		2022-06-03 08:59:39.970	info	Restart adapter system.adapter.zigbee.0 because enabled
                      host.raspberrypi
                      		2022-06-03 08:59:39.969	error	instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
                      host.raspberrypi
                      		2022-06-03 08:59:39.968	info	Restart adapter system.adapter.zigbee.0 because enabled
                      host.raspberrypi
                      		2022-06-03 08:59:39.967	error	instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
                      host.raspberrypi
                      		2022-06-03 08:59:39.967	error	Caught by controller[3]: at /opt/iobroker/node_modules/@serialport/stream/lib/index.js:242:12
                      host.raspberrypi
                      		2022-06-03 08:59:39.967	error	Caught by controller[3]: at SerialPort._error (/opt/iobroker/node_modules/@serialport/stream/lib/index.js:198:14)
                      host.raspberrypi
                      		2022-06-03 08:59:39.966	error	Caught by controller[3]: at SerialPort.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/deconz/driver/driver.ts:182:28)
                      host.raspberrypi
                      		2022-06-03 08:59:39.966	error	Caught by controller[3]: Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0'
                      host.raspberrypi
                      		2022-06-03 08:59:39.965	error	Caught by controller[2]: at /opt/iobroker/node_modules/@serialport/stream/lib/index.js:242:12
                      host.raspberrypi
                      		2022-06-03 08:59:39.965	error	Caught by controller[2]: at SerialPort._error (/opt/iobroker/node_modules/@serialport/stream/lib/index.js:198:14)
                      host.raspberrypi
                      		2022-06-03 08:59:39.965	error	Caught by controller[2]: at SerialPort.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/deconz/driver/driver.ts:182:28)
                      host.raspberrypi
                      		2022-06-03 08:59:39.964	error	Caught by controller[2]: Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0'
                      host.raspberrypi
                      		2022-06-03 08:59:39.964	error	Caught by controller[1]: 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:
                      host.raspberrypi
                      		2022-06-03 08:59:39.963	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
                      	7060	2022-06-03 08:59:39.207	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
                      zigbee.0
                      	7060	2022-06-03 08:59:39.204	info	terminating
                      zigbee.0
                      	7060	2022-06-03 08:59:39.195	info	Zigbee: disabling joining new devices.
                      zigbee.0
                      	7060	2022-06-03 08:59:39.064	info	cleaned everything up...
                      zigbee.0
                      	7060	2022-06-03 08:59:39.050	error	Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0'
                      zigbee.0
                      	7060	2022-06-03 08:59:39.050	error	Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0' at SerialPort.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/deconz/driver/driver.ts:182:28) at SerialPort._error (/opt/iobroker/node_modules/@serialport/stream/lib/index.js:198:14) at /opt/iobroker/node_modules/@serialport/stream/lib/index.js:242:12
                      zigbee.0
                      	7060	2022-06-03 08:59:39.048	error	unhandled promise rejection: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0'
                      zigbee.0
                      	7060	2022-06-03 08:59:39.047	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().
                      web.0
                      	2689	2022-06-03 08:59:33.060	info	<== Disconnect system.user.admin from ::ffff:192.168.178.40
                      zigbee.0
                      	7060	2022-06-03 08:59:19.680	error	Error herdsman start
                      zigbee.0
                      	7060	2022-06-03 08:59:19.679	error	Failed to start Zigbee
                      zigbee.0
                      	7060	2022-06-03 08:59:19.676	error	Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0'"
                      zigbee.0
                      	7060	2022-06-03 08:59:19.393	info	Installed Version: iobroker.zigbee@1.7.5
                      zigbee.0
                      	7060	2022-06-03 08:59:19.367	info	Starting Zigbee npm ...
                      zigbee.0
                      	7060	2022-06-03 08:59:19.365	info	Try to reconnect. 1 attempts left
                      zigbee.0
                      	7060	2022-06-03 08:59:09.371	info	Installed Version: iobroker.zigbee@1.7.5
                      zigbee.0
                      	7060	2022-06-03 08:59:09.359	error	Error herdsman start
                      zigbee.0
                      	7060	2022-06-03 08:59:09.357	error	Failed to start Zigbee
                      zigbee.0
                      	7060	2022-06-03 08:59:09.355	error	Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0'"
                      zigbee.0
                      	7060	2022-06-03 08:59:08.095	info	Starting Zigbee npm ...
                      zigbee.0
                      	7060	2022-06-03 08:59:08.090	info	delete old Backup files. keep only last 10
                      zigbee.0
                      	7060	2022-06-03 08:59:07.908	info	starting. Version 1.7.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v14.19.3, js-controller: 4.0.23
                      host.raspberrypi
                      		2022-06-03 08:59:00.487	info	instance system.adapter.zigbee.0 started with pid 7060
                      host.raspberrypi
                      		2022-06-03 08:59:00.484	info	instance system.adapter.zigbee.0 started with pid 7060
                      host.raspberrypi
                      		2022-06-03 08:59:00.173	info	"system.adapter.zigbee.0" enabled
                      host.raspberrypi
                      		2022-06-03 08:58:59.002	info	instance system.adapter.zigbee.0 terminated with code null ()
                      host.raspberrypi
                      		2022-06-03 08:58:59.001	warn	instance system.adapter.zigbee.0 terminated due to SIGTERM
                      host.raspberrypi
                      		2022-06-03 08:58:58.900	info	stopInstance system.adapter.zigbee.0 killing pid 7053
                      host.raspberrypi
                      		2022-06-03 08:58:57.898	info	stopInstance system.adapter.zigbee.0 send kill signal
                      host.raspberrypi
                      		2022-06-03 08:58:57.822	info	stopInstance system.adapter.zigbee.0 (force=false, process=true)
                      host.raspberrypi
                      		2022-06-03 08:58:57.821	info	"system.adapter.zigbee.0" disabled
                      host.raspberrypi
                      		2022-06-03 08:58:57.148	info	stopInstance system.adapter.zigbee.0 send kill signal
                      host.raspberrypi
                      		2022-06-03 08:58:57.075	info	stopInstance system.adapter.zigbee.0 (force=false, process=true)
                      host.raspberrypi
                      		2022-06-03 08:58:56.777	info	instance system.adapter.zigbee.0 started with pid 7053
                      host.raspberrypi
                      		2022-06-03 08:58:54.713	info	instance system.adapter.zigbee.0 terminated with code null ()
                      host.raspberrypi
                      		2022-06-03 08:58:54.712	warn	instance system.adapter.zigbee.0 terminated due to SIGTERM
                      host.raspberrypi
                      		2022-06-03 08:58:54.607	info	stopInstance system.adapter.zigbee.0 killing pid 7046
                      host.raspberrypi
                      		2022-06-03 08:58:53.605	info	stopInstance system.adapter.zigbee.0 send kill signal
                      host.raspberrypi
                      		2022-06-03 08:58:53.592	info	stopInstance system.adapter.zigbee.0 (force=false, process=true)
                      host.raspberrypi
                      		2022-06-03 08:58:52.424	info	instance system.adapter.zigbee.0 started with pid 7046
                      host.raspberrypi
                      		2022-06-03 08:58:26.981	info	Restart adapter system.adapter.zigbee.0 because enabled
                      host.raspberrypi
                      		2022-06-03 08:58:26.980	error	instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
                      host.raspberrypi
                      		2022-06-03 08:58:26.979	error	Caught by controller[0]: at /opt/iobroker/node_modules/@serialport/stream/lib/index.js:242:12
                      host.raspberrypi
                      		2022-06-03 08:58:26.979	error	Caught by controller[0]: at SerialPort._error (/opt/iobroker/node_modules/@serialport/stream/lib/index.js:198:14)
                      host.raspberrypi
                      		2022-06-03 08:58:26.978	error	Caught by controller[0]: at SerialPort.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/deconz/driver/driver.ts:182:28)
                      host.raspberrypi
                      		2022-06-03 08:58:26.977	error	Caught by controller[0]: Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0'
                      host.raspberrypi
                      		2022-06-03 08:58:26.976	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
                      	7029	2022-06-03 08:58:26.300	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
                      zigbee.0
                      	7029	2022-06-03 08:58:26.297	info	terminating
                      zigbee.0
                      	7029	2022-06-03 08:58:26.278	info	Zigbee: disabling joining new devices.
                      zigbee.0
                      	7029	2022-06-03 08:58:26.116	info	cleaned everything up...
                      zigbee.0
                      	7029	2022-06-03 08:58:26.097	error	Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0'
                      zigbee.0
                      	7029	2022-06-03 08:58:26.096	error	Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0' at SerialPort.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/deconz/driver/driver.ts:182:28) at SerialPort._error (/opt/iobroker/node_modules/@serialport/stream/lib/index.js:198:14) at /opt/iobroker/node_modules/@serialport/stream/lib/index.js:242:12
                      zigbee.0
                      	7029	2022-06-03 08:58:26.093	error	unhandled promise rejection: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0'
                      zigbee.0
                      	7029	2022-06-03 08:58:26.091	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().
                      host.raspberrypi
                      		2022-06-03 08:58:13.379	error	instance system.adapter.daswetter.0 terminated with code 15 (UNKNOWN_ERROR)
                      daswetter.0
                      	7013	2022-06-03 08:58:13.348	error	Cannot check object existence of "daswetter.0.NextHours2.Location_1.Day_1.Hour_3.symbol": Connection is closed.
                      daswetter.0
                      	7013	2022-06-03 08:58:13.345	error	exception in await insertIntoList [Error: Could not check object existence of daswetter.0.NextHours2.Location_1.Day_1.current.temp: Cannot check object existence of "daswetter.0.NextHours2.Location_1.Day_1.current.temp": Connection is closed.]
                      daswetter.0
                      	7013	2022-06-03 08:58:13.343	error	Cannot check object existence of "daswetter.0.NextHours2.Location_1.Day_1.current.temp": Connection is closed.
                      daswetter.0
                      	7013	2022-06-03 08:58:13.340	error	exception in await insertIntoList [Error: Could not check object existence of daswetter.0.NextHours2.Location_1.Day_1.Hour_3.temp: Cannot check object existence of "daswetter.0.NextHours2.Location_1.Day_1.Hour_3.temp": Connection is closed.]
                      daswetter.0
                      	7013	2022-06-03 08:58:13.338	error	Cannot check object existence of "daswetter.0.NextHours2.Location_1.Day_1.Hour_3.temp": Connection is closed.
                      daswetter.0
                      	7013	2022-06-03 08:58:13.336	error	exception in await insertIntoList [Error: Could not check object existence of daswetter.0.NextHours2.Location_1.Day_1.current.hour: Cannot check object existence of "daswetter.0.NextHours2.Location_1.Day_1.current.hour": Connection is closed.]
                      daswetter.0
                      	7013	2022-06-03 08:58:13.333	error	Cannot check object existence of "daswetter.0.NextHours2.Location_1.Day_1.current.hour": Connection is closed.
                      daswetter.0
                      	7013	2022-06-03 08:58:13.329	error	exception in await insertIntoList [Error: DB closed]
                      daswetter.0
                      	7013	2022-06-03 08:58:13.325	warn	get state error: Connection is closed.
                      daswetter.0
                      	7013	2022-06-03 08:58:12.808	warn	Terminated (UNKNOWN_ERROR): Without reason
                      daswetter.0
                      	7013	2022-06-03 08:58:12.805	error	force terminate
                      daswetter.0
                      	7013	2022-06-03 08:58:12.738	info	still wrong data structure from server received! repaired...
                      zigbee.0
                      	7029	2022-06-03 08:58:06.750	error	Error herdsman start
                      zigbee.0
                      	7029	2022-06-03 08:58:06.749	error	Failed to start Zigbee
                      zigbee.0
                      	7029	2022-06-03 08:58:06.745	error	Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0'"
                      zigbee.0
                      	7029	2022-06-03 08:58:06.424	info	Installed Version: iobroker.zigbee@1.7.5
                      zigbee.0
                      	7029	2022-06-03 08:58:06.386	info	Starting Zigbee npm ...
                      zigbee.0
                      	7029	2022-06-03 08:58:06.384	info	Try to reconnect. 1 attempts left
                      zigbee.0
                      	7029	2022-06-03 08:57:56.384	info	Installed Version: iobroker.zigbee@1.7.5
                      zigbee.0
                      	7029	2022-06-03 08:57:56.378	error	Error herdsman start
                      zigbee.0
                      	7029	2022-06-03 08:57:56.377	error	Failed to start Zigbee
                      zigbee.0
                      	7029	2022-06-03 08:57:56.375	error	Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0'"
                      zigbee.0
                      	7029	2022-06-03 08:57:54.880	info	Starting Zigbee npm ...
                      zigbee.0
                      	7029	2022-06-03 08:57:54.873	info	delete old Backup files. keep only last 10
                      zigbee.0
                      	7029	2022-06-03 08:57:54.612	info	starting. Version 1.7.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v14.19.3, js-controller: 4.0.23
                      host.raspberrypi
                      		2022-06-03 08:57:44.648	info	instance system.adapter.zigbee.0 started with pid 7029
                      daswetter.0
                      	7013	2022-06-03 08:57:12.755	info	starting. Version 3.1.2 in /opt/iobroker/node_modules/iobroker.daswetter, node: v14.19.3, js-controller: 4.0.23
                      web.0
                      	2689	2022-06-03 08:57:09.172	info	==> Connected system.user.admin from ::ffff:192.168.178.40
                      iot.2
                      	983	2022-06-03 08:57:07.961	info	Connection changed: connect
                      host.raspberrypi
                      		2022-06-03 08:57:06.801	info	instance system.adapter.daswetter.0 started with pid 7013
                      host.raspberrypi
                      		2022-06-03 08:57:06.681	info	Restart adapter system.adapter.zigbee.0 because enabled
                      host.raspberrypi
                      		2022-06-03 08:57:06.674	info	instance system.adapter.zigbee.0 terminated with code NaN ()
                      host.raspberrypi
                      	
                      
                      arteckA Offline
                      arteckA Offline
                      arteck
                      Developer Most Active
                      schrieb am zuletzt editiert von
                      #49

                      @klaris ist halt conbee.. firmware mal updaten vielleicht

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

                      K 1 Antwort Letzte Antwort
                      0
                      • K klaris

                        @klaris heute morgen ..leider das gleiche ...

                        daswetter.0
                        	7089	2022-06-03 09:00:35.846	info	Terminated (ADAPTER_REQUESTED_TERMINATION): All data handled, adapter stopped until next scheduled moment
                        daswetter.0
                        	7089	2022-06-03 09:00:29.165	info	still wrong data structure from server received! repaired...
                        daswetter.0
                        	7089	2022-06-03 09:00:03.641	info	starting. Version 3.1.2 in /opt/iobroker/node_modules/iobroker.daswetter, node: v14.19.3, js-controller: 4.0.23
                        host.raspberrypi
                        		2022-06-03 09:00:00.150	info	instance system.adapter.daswetter.0 started with pid 7089
                        host.raspberrypi
                        		2022-06-03 08:59:39.971	warn	Do not restart adapter system.adapter.zigbee.0 because restart loop detected
                        host.raspberrypi
                        		2022-06-03 08:59:39.970	info	Restart adapter system.adapter.zigbee.0 because enabled
                        host.raspberrypi
                        		2022-06-03 08:59:39.969	error	instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
                        host.raspberrypi
                        		2022-06-03 08:59:39.968	info	Restart adapter system.adapter.zigbee.0 because enabled
                        host.raspberrypi
                        		2022-06-03 08:59:39.967	error	instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
                        host.raspberrypi
                        		2022-06-03 08:59:39.967	error	Caught by controller[3]: at /opt/iobroker/node_modules/@serialport/stream/lib/index.js:242:12
                        host.raspberrypi
                        		2022-06-03 08:59:39.967	error	Caught by controller[3]: at SerialPort._error (/opt/iobroker/node_modules/@serialport/stream/lib/index.js:198:14)
                        host.raspberrypi
                        		2022-06-03 08:59:39.966	error	Caught by controller[3]: at SerialPort.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/deconz/driver/driver.ts:182:28)
                        host.raspberrypi
                        		2022-06-03 08:59:39.966	error	Caught by controller[3]: Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0'
                        host.raspberrypi
                        		2022-06-03 08:59:39.965	error	Caught by controller[2]: at /opt/iobroker/node_modules/@serialport/stream/lib/index.js:242:12
                        host.raspberrypi
                        		2022-06-03 08:59:39.965	error	Caught by controller[2]: at SerialPort._error (/opt/iobroker/node_modules/@serialport/stream/lib/index.js:198:14)
                        host.raspberrypi
                        		2022-06-03 08:59:39.965	error	Caught by controller[2]: at SerialPort.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/deconz/driver/driver.ts:182:28)
                        host.raspberrypi
                        		2022-06-03 08:59:39.964	error	Caught by controller[2]: Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0'
                        host.raspberrypi
                        		2022-06-03 08:59:39.964	error	Caught by controller[1]: 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:
                        host.raspberrypi
                        		2022-06-03 08:59:39.963	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
                        	7060	2022-06-03 08:59:39.207	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
                        zigbee.0
                        	7060	2022-06-03 08:59:39.204	info	terminating
                        zigbee.0
                        	7060	2022-06-03 08:59:39.195	info	Zigbee: disabling joining new devices.
                        zigbee.0
                        	7060	2022-06-03 08:59:39.064	info	cleaned everything up...
                        zigbee.0
                        	7060	2022-06-03 08:59:39.050	error	Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0'
                        zigbee.0
                        	7060	2022-06-03 08:59:39.050	error	Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0' at SerialPort.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/deconz/driver/driver.ts:182:28) at SerialPort._error (/opt/iobroker/node_modules/@serialport/stream/lib/index.js:198:14) at /opt/iobroker/node_modules/@serialport/stream/lib/index.js:242:12
                        zigbee.0
                        	7060	2022-06-03 08:59:39.048	error	unhandled promise rejection: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0'
                        zigbee.0
                        	7060	2022-06-03 08:59:39.047	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().
                        web.0
                        	2689	2022-06-03 08:59:33.060	info	<== Disconnect system.user.admin from ::ffff:192.168.178.40
                        zigbee.0
                        	7060	2022-06-03 08:59:19.680	error	Error herdsman start
                        zigbee.0
                        	7060	2022-06-03 08:59:19.679	error	Failed to start Zigbee
                        zigbee.0
                        	7060	2022-06-03 08:59:19.676	error	Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0'"
                        zigbee.0
                        	7060	2022-06-03 08:59:19.393	info	Installed Version: iobroker.zigbee@1.7.5
                        zigbee.0
                        	7060	2022-06-03 08:59:19.367	info	Starting Zigbee npm ...
                        zigbee.0
                        	7060	2022-06-03 08:59:19.365	info	Try to reconnect. 1 attempts left
                        zigbee.0
                        	7060	2022-06-03 08:59:09.371	info	Installed Version: iobroker.zigbee@1.7.5
                        zigbee.0
                        	7060	2022-06-03 08:59:09.359	error	Error herdsman start
                        zigbee.0
                        	7060	2022-06-03 08:59:09.357	error	Failed to start Zigbee
                        zigbee.0
                        	7060	2022-06-03 08:59:09.355	error	Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0'"
                        zigbee.0
                        	7060	2022-06-03 08:59:08.095	info	Starting Zigbee npm ...
                        zigbee.0
                        	7060	2022-06-03 08:59:08.090	info	delete old Backup files. keep only last 10
                        zigbee.0
                        	7060	2022-06-03 08:59:07.908	info	starting. Version 1.7.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v14.19.3, js-controller: 4.0.23
                        host.raspberrypi
                        		2022-06-03 08:59:00.487	info	instance system.adapter.zigbee.0 started with pid 7060
                        host.raspberrypi
                        		2022-06-03 08:59:00.484	info	instance system.adapter.zigbee.0 started with pid 7060
                        host.raspberrypi
                        		2022-06-03 08:59:00.173	info	"system.adapter.zigbee.0" enabled
                        host.raspberrypi
                        		2022-06-03 08:58:59.002	info	instance system.adapter.zigbee.0 terminated with code null ()
                        host.raspberrypi
                        		2022-06-03 08:58:59.001	warn	instance system.adapter.zigbee.0 terminated due to SIGTERM
                        host.raspberrypi
                        		2022-06-03 08:58:58.900	info	stopInstance system.adapter.zigbee.0 killing pid 7053
                        host.raspberrypi
                        		2022-06-03 08:58:57.898	info	stopInstance system.adapter.zigbee.0 send kill signal
                        host.raspberrypi
                        		2022-06-03 08:58:57.822	info	stopInstance system.adapter.zigbee.0 (force=false, process=true)
                        host.raspberrypi
                        		2022-06-03 08:58:57.821	info	"system.adapter.zigbee.0" disabled
                        host.raspberrypi
                        		2022-06-03 08:58:57.148	info	stopInstance system.adapter.zigbee.0 send kill signal
                        host.raspberrypi
                        		2022-06-03 08:58:57.075	info	stopInstance system.adapter.zigbee.0 (force=false, process=true)
                        host.raspberrypi
                        		2022-06-03 08:58:56.777	info	instance system.adapter.zigbee.0 started with pid 7053
                        host.raspberrypi
                        		2022-06-03 08:58:54.713	info	instance system.adapter.zigbee.0 terminated with code null ()
                        host.raspberrypi
                        		2022-06-03 08:58:54.712	warn	instance system.adapter.zigbee.0 terminated due to SIGTERM
                        host.raspberrypi
                        		2022-06-03 08:58:54.607	info	stopInstance system.adapter.zigbee.0 killing pid 7046
                        host.raspberrypi
                        		2022-06-03 08:58:53.605	info	stopInstance system.adapter.zigbee.0 send kill signal
                        host.raspberrypi
                        		2022-06-03 08:58:53.592	info	stopInstance system.adapter.zigbee.0 (force=false, process=true)
                        host.raspberrypi
                        		2022-06-03 08:58:52.424	info	instance system.adapter.zigbee.0 started with pid 7046
                        host.raspberrypi
                        		2022-06-03 08:58:26.981	info	Restart adapter system.adapter.zigbee.0 because enabled
                        host.raspberrypi
                        		2022-06-03 08:58:26.980	error	instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
                        host.raspberrypi
                        		2022-06-03 08:58:26.979	error	Caught by controller[0]: at /opt/iobroker/node_modules/@serialport/stream/lib/index.js:242:12
                        host.raspberrypi
                        		2022-06-03 08:58:26.979	error	Caught by controller[0]: at SerialPort._error (/opt/iobroker/node_modules/@serialport/stream/lib/index.js:198:14)
                        host.raspberrypi
                        		2022-06-03 08:58:26.978	error	Caught by controller[0]: at SerialPort.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/deconz/driver/driver.ts:182:28)
                        host.raspberrypi
                        		2022-06-03 08:58:26.977	error	Caught by controller[0]: Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0'
                        host.raspberrypi
                        		2022-06-03 08:58:26.976	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
                        	7029	2022-06-03 08:58:26.300	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
                        zigbee.0
                        	7029	2022-06-03 08:58:26.297	info	terminating
                        zigbee.0
                        	7029	2022-06-03 08:58:26.278	info	Zigbee: disabling joining new devices.
                        zigbee.0
                        	7029	2022-06-03 08:58:26.116	info	cleaned everything up...
                        zigbee.0
                        	7029	2022-06-03 08:58:26.097	error	Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0'
                        zigbee.0
                        	7029	2022-06-03 08:58:26.096	error	Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0' at SerialPort.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/deconz/driver/driver.ts:182:28) at SerialPort._error (/opt/iobroker/node_modules/@serialport/stream/lib/index.js:198:14) at /opt/iobroker/node_modules/@serialport/stream/lib/index.js:242:12
                        zigbee.0
                        	7029	2022-06-03 08:58:26.093	error	unhandled promise rejection: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0'
                        zigbee.0
                        	7029	2022-06-03 08:58:26.091	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().
                        host.raspberrypi
                        		2022-06-03 08:58:13.379	error	instance system.adapter.daswetter.0 terminated with code 15 (UNKNOWN_ERROR)
                        daswetter.0
                        	7013	2022-06-03 08:58:13.348	error	Cannot check object existence of "daswetter.0.NextHours2.Location_1.Day_1.Hour_3.symbol": Connection is closed.
                        daswetter.0
                        	7013	2022-06-03 08:58:13.345	error	exception in await insertIntoList [Error: Could not check object existence of daswetter.0.NextHours2.Location_1.Day_1.current.temp: Cannot check object existence of "daswetter.0.NextHours2.Location_1.Day_1.current.temp": Connection is closed.]
                        daswetter.0
                        	7013	2022-06-03 08:58:13.343	error	Cannot check object existence of "daswetter.0.NextHours2.Location_1.Day_1.current.temp": Connection is closed.
                        daswetter.0
                        	7013	2022-06-03 08:58:13.340	error	exception in await insertIntoList [Error: Could not check object existence of daswetter.0.NextHours2.Location_1.Day_1.Hour_3.temp: Cannot check object existence of "daswetter.0.NextHours2.Location_1.Day_1.Hour_3.temp": Connection is closed.]
                        daswetter.0
                        	7013	2022-06-03 08:58:13.338	error	Cannot check object existence of "daswetter.0.NextHours2.Location_1.Day_1.Hour_3.temp": Connection is closed.
                        daswetter.0
                        	7013	2022-06-03 08:58:13.336	error	exception in await insertIntoList [Error: Could not check object existence of daswetter.0.NextHours2.Location_1.Day_1.current.hour: Cannot check object existence of "daswetter.0.NextHours2.Location_1.Day_1.current.hour": Connection is closed.]
                        daswetter.0
                        	7013	2022-06-03 08:58:13.333	error	Cannot check object existence of "daswetter.0.NextHours2.Location_1.Day_1.current.hour": Connection is closed.
                        daswetter.0
                        	7013	2022-06-03 08:58:13.329	error	exception in await insertIntoList [Error: DB closed]
                        daswetter.0
                        	7013	2022-06-03 08:58:13.325	warn	get state error: Connection is closed.
                        daswetter.0
                        	7013	2022-06-03 08:58:12.808	warn	Terminated (UNKNOWN_ERROR): Without reason
                        daswetter.0
                        	7013	2022-06-03 08:58:12.805	error	force terminate
                        daswetter.0
                        	7013	2022-06-03 08:58:12.738	info	still wrong data structure from server received! repaired...
                        zigbee.0
                        	7029	2022-06-03 08:58:06.750	error	Error herdsman start
                        zigbee.0
                        	7029	2022-06-03 08:58:06.749	error	Failed to start Zigbee
                        zigbee.0
                        	7029	2022-06-03 08:58:06.745	error	Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0'"
                        zigbee.0
                        	7029	2022-06-03 08:58:06.424	info	Installed Version: iobroker.zigbee@1.7.5
                        zigbee.0
                        	7029	2022-06-03 08:58:06.386	info	Starting Zigbee npm ...
                        zigbee.0
                        	7029	2022-06-03 08:58:06.384	info	Try to reconnect. 1 attempts left
                        zigbee.0
                        	7029	2022-06-03 08:57:56.384	info	Installed Version: iobroker.zigbee@1.7.5
                        zigbee.0
                        	7029	2022-06-03 08:57:56.378	error	Error herdsman start
                        zigbee.0
                        	7029	2022-06-03 08:57:56.377	error	Failed to start Zigbee
                        zigbee.0
                        	7029	2022-06-03 08:57:56.375	error	Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0'"
                        zigbee.0
                        	7029	2022-06-03 08:57:54.880	info	Starting Zigbee npm ...
                        zigbee.0
                        	7029	2022-06-03 08:57:54.873	info	delete old Backup files. keep only last 10
                        zigbee.0
                        	7029	2022-06-03 08:57:54.612	info	starting. Version 1.7.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v14.19.3, js-controller: 4.0.23
                        host.raspberrypi
                        		2022-06-03 08:57:44.648	info	instance system.adapter.zigbee.0 started with pid 7029
                        daswetter.0
                        	7013	2022-06-03 08:57:12.755	info	starting. Version 3.1.2 in /opt/iobroker/node_modules/iobroker.daswetter, node: v14.19.3, js-controller: 4.0.23
                        web.0
                        	2689	2022-06-03 08:57:09.172	info	==> Connected system.user.admin from ::ffff:192.168.178.40
                        iot.2
                        	983	2022-06-03 08:57:07.961	info	Connection changed: connect
                        host.raspberrypi
                        		2022-06-03 08:57:06.801	info	instance system.adapter.daswetter.0 started with pid 7013
                        host.raspberrypi
                        		2022-06-03 08:57:06.681	info	Restart adapter system.adapter.zigbee.0 because enabled
                        host.raspberrypi
                        		2022-06-03 08:57:06.674	info	instance system.adapter.zigbee.0 terminated with code NaN ()
                        host.raspberrypi
                        	
                        
                        Thomas BraunT Online
                        Thomas BraunT Online
                        Thomas Braun
                        Most Active
                        schrieb am zuletzt editiert von
                        #50

                        @klaris

                        dmesg -wT
                        

                        anschauen, mit dem Stick hantieren (Ausstöpseln, etwas warten, Einstöpseln)

                        Linux-Werkzeugkasten:
                        https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                        NodeJS Fixer Skript:
                        https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                        iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                        1 Antwort Letzte Antwort
                        0
                        • arteckA arteck

                          @klaris ist halt conbee.. firmware mal updaten vielleicht

                          K Offline
                          K Offline
                          klaris
                          schrieb am zuletzt editiert von klaris
                          #51

                          @arteck die deconz software hatte ich am anfang instaliert und dann von iobroker komplett geloscht und zigbee adapter instaliert finde ich besser ..
                          kann ich trotzdem die Firmware von ConBee II unter iobroker aktualisieren ?

                          arteckA mickymM 2 Antworten Letzte Antwort
                          0
                          • K klaris

                            @arteck die deconz software hatte ich am anfang instaliert und dann von iobroker komplett geloscht und zigbee adapter instaliert finde ich besser ..
                            kann ich trotzdem die Firmware von ConBee II unter iobroker aktualisieren ?

                            arteckA Offline
                            arteckA Offline
                            arteck
                            Developer Most Active
                            schrieb am zuletzt editiert von
                            #52

                            @klaris kein plan wie das mit dem conbee läuft..

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

                            1 Antwort Letzte Antwort
                            0
                            • K klaris

                              @arteck die deconz software hatte ich am anfang instaliert und dann von iobroker komplett geloscht und zigbee adapter instaliert finde ich besser ..
                              kann ich trotzdem die Firmware von ConBee II unter iobroker aktualisieren ?

                              mickymM Offline
                              mickymM Offline
                              mickym
                              Most Active
                              schrieb am zuletzt editiert von mickym
                              #53

                              @klaris Du kannst die Firmware mit dem GCFlasher aktualisieren.

                              https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/Update-deCONZ-manually#update-in-windows

                              Das geht dann auch ohne die deconz Software. Inzwischen soll ja der conbee vom Zigbee Adapter lt. Beschreibung vollumfänglich unterstützt werden. Falls Du jedoch Alternativen suchst, kann ich Dir das zigbee2mqtt mit dem mqtt-Adapter wärmstens empfehlen, funktioniert bei mir nun seit ein paar Monaten sehr zuverlässig. Lediglich die Karte wird bei mir nicht angezeigt. Dafür gibts aber teilweise sehr nützliche Einstellungen, wie das Einschaltverhalten von Geräten, die Du anscheinend bei dem Zigbee adapter nur über SendTo Befehle realisieren kannst. Es gibt auch einen Client als GUI für das zigbee2mqtt, das auch die Kacheldarstellung verwendet.

                              Ich habe die 26700700 drauf, mit der funktioniert es soweit alles gut. Habe gesehen, dass es seit 15.Mai sogar noch eine neue Version gibt.

                              Hab gerade mal die neueste Version (also 26780700) drauf gemacht - war in ein paar Sekunden erledigt:

                              GCFFlasher -d COM3 -t 60 -f ..\deCONZ_ConBeeII_0x26780700.bin.GCF
                              GCFFlasher V3_17 (c) dresden elektronik ingenieurtechnik gmbh
                              Reboot device COM3 (ConBee II)
                              deCONZ firmware version 26700700
                              R21B18 Bootloader
                              Vers: 2.07
                              build: Jun 17 2019
                              flashing 163230 bytes: |==============================|
                              verify: .
                              SUCCESS
                              Wait 10 seconds until application starts
                              

                              Bei der Kartendarstellung schweben die am Koordinator selbst verbundenen Geräte noch im freien Raum, ansonsten schaut alles gut aus:

                              Die rot eingezeichneten Linien - fehlen halt:

                              246070d8-c468-4e95-9cfa-b4c2ae7d5942-image.png

                              Jeder Flow bzw. jedes Script, das ich hier poste implementiert jeder auf eigene Gefahr. Flows und Scripts können Fehler aufweisen und weder der Seitenbetreiber noch ich persönlich können hierfür haftbar gemacht werden. Das gleiche gilt für Empfehlungen aller Art.

                              K 1 Antwort Letzte Antwort
                              0
                              • mickymM mickym

                                @klaris Du kannst die Firmware mit dem GCFlasher aktualisieren.

                                https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/Update-deCONZ-manually#update-in-windows

                                Das geht dann auch ohne die deconz Software. Inzwischen soll ja der conbee vom Zigbee Adapter lt. Beschreibung vollumfänglich unterstützt werden. Falls Du jedoch Alternativen suchst, kann ich Dir das zigbee2mqtt mit dem mqtt-Adapter wärmstens empfehlen, funktioniert bei mir nun seit ein paar Monaten sehr zuverlässig. Lediglich die Karte wird bei mir nicht angezeigt. Dafür gibts aber teilweise sehr nützliche Einstellungen, wie das Einschaltverhalten von Geräten, die Du anscheinend bei dem Zigbee adapter nur über SendTo Befehle realisieren kannst. Es gibt auch einen Client als GUI für das zigbee2mqtt, das auch die Kacheldarstellung verwendet.

                                Ich habe die 26700700 drauf, mit der funktioniert es soweit alles gut. Habe gesehen, dass es seit 15.Mai sogar noch eine neue Version gibt.

                                Hab gerade mal die neueste Version (also 26780700) drauf gemacht - war in ein paar Sekunden erledigt:

                                GCFFlasher -d COM3 -t 60 -f ..\deCONZ_ConBeeII_0x26780700.bin.GCF
                                GCFFlasher V3_17 (c) dresden elektronik ingenieurtechnik gmbh
                                Reboot device COM3 (ConBee II)
                                deCONZ firmware version 26700700
                                R21B18 Bootloader
                                Vers: 2.07
                                build: Jun 17 2019
                                flashing 163230 bytes: |==============================|
                                verify: .
                                SUCCESS
                                Wait 10 seconds until application starts
                                

                                Bei der Kartendarstellung schweben die am Koordinator selbst verbundenen Geräte noch im freien Raum, ansonsten schaut alles gut aus:

                                Die rot eingezeichneten Linien - fehlen halt:

                                246070d8-c468-4e95-9cfa-b4c2ae7d5942-image.png

                                K Offline
                                K Offline
                                klaris
                                schrieb am zuletzt editiert von klaris
                                #54

                                @mickym wenn man(n) weiß wie es geht ….
                                Ich habe wieder aus Verzweiflung die deconz Software installiert auf iobroker und den zigbee Adapter deaktiviert … Teste die Stabilität der zigbee Geräte …. Aber eine kleine Anleitung zum Update des ConBee sticks würde mich schon interessieren…habe die Version 26700700 .
                                Ehrlich gesagt gefällt mir der zigbee Adapter sehr gut leider läuft er nicht stabil. Ständig Probleme mit den Com Port ….und der Adapter Stürzt zweimal am Tag ab…
                                Vielen Dank für deine Hinweise

                                mickymM 1 Antwort Letzte Antwort
                                0
                                • K klaris

                                  @mickym wenn man(n) weiß wie es geht ….
                                  Ich habe wieder aus Verzweiflung die deconz Software installiert auf iobroker und den zigbee Adapter deaktiviert … Teste die Stabilität der zigbee Geräte …. Aber eine kleine Anleitung zum Update des ConBee sticks würde mich schon interessieren…habe die Version 26700700 .
                                  Ehrlich gesagt gefällt mir der zigbee Adapter sehr gut leider läuft er nicht stabil. Ständig Probleme mit den Com Port ….und der Adapter Stürzt zweimal am Tag ab…
                                  Vielen Dank für deine Hinweise

                                  mickymM Offline
                                  mickymM Offline
                                  mickym
                                  Most Active
                                  schrieb am zuletzt editiert von mickym
                                  #55

                                  @klaris Nun den Link zum Flashen des Sticks habe ich Dir doch im vorherigen Post beschrieben.

                                  Auf welchem System läuft denn Dein iobroker?

                                  Und wie gesagt, mit dem zigbee2mqtt musst Du halt über mqtt kommunizieren. Für mich hat die Umstellung ca. 1-2 Tage benötigt, aber ich bin sehr zufrieden. Ich hatte lediglich eine Fehlfunktion und im Vergleich zum zigbee Adapter finde ich persönlich die Stabilität um einiges besser. Ich habe damals aber eigentlich nur umgestellt, weil damals der conbee nicht vollständig unterstützt wurde und habe mich deshalb nach Alternativen umgeschaut und was ich von dem deconz gesehen habe, das hat mir halt gar nicht gefallen.

                                  Jeder Flow bzw. jedes Script, das ich hier poste implementiert jeder auf eigene Gefahr. Flows und Scripts können Fehler aufweisen und weder der Seitenbetreiber noch ich persönlich können hierfür haftbar gemacht werden. Das gleiche gilt für Empfehlungen aller Art.

                                  K 1 Antwort Letzte Antwort
                                  0
                                  • mickymM mickym

                                    @klaris Nun den Link zum Flashen des Sticks habe ich Dir doch im vorherigen Post beschrieben.

                                    Auf welchem System läuft denn Dein iobroker?

                                    Und wie gesagt, mit dem zigbee2mqtt musst Du halt über mqtt kommunizieren. Für mich hat die Umstellung ca. 1-2 Tage benötigt, aber ich bin sehr zufrieden. Ich hatte lediglich eine Fehlfunktion und im Vergleich zum zigbee Adapter finde ich persönlich die Stabilität um einiges besser. Ich habe damals aber eigentlich nur umgestellt, weil damals der conbee nicht vollständig unterstützt wurde und habe mich deshalb nach Alternativen umgeschaut und was ich von dem deconz gesehen habe, das hat mir halt gar nicht gefallen.

                                    K Offline
                                    K Offline
                                    klaris
                                    schrieb am zuletzt editiert von klaris
                                    #56

                                    @mickym raspberry pi 3+
                                    Ja Deconz ist sehr spartanisch aufgebaut

                                    mickymM 2 Antworten Letzte Antwort
                                    0
                                    • K klaris

                                      @mickym raspberry pi 3+
                                      Ja Deconz ist sehr spartanisch aufgebaut

                                      mickymM Offline
                                      mickymM Offline
                                      mickym
                                      Most Active
                                      schrieb am zuletzt editiert von
                                      #57

                                      @klaris Wie gesagt das Flashen habe ich Dir ja schon gepostet und falls Du auf mqtt und zigbee umsteigen willst, dann kann ich Dir mit den Links schon etwas aus meiner Erfahrung helfen.

                                      Jeder Flow bzw. jedes Script, das ich hier poste implementiert jeder auf eigene Gefahr. Flows und Scripts können Fehler aufweisen und weder der Seitenbetreiber noch ich persönlich können hierfür haftbar gemacht werden. Das gleiche gilt für Empfehlungen aller Art.

                                      1 Antwort Letzte Antwort
                                      0
                                      • K klaris

                                        @mickym raspberry pi 3+
                                        Ja Deconz ist sehr spartanisch aufgebaut

                                        mickymM Offline
                                        mickymM Offline
                                        mickym
                                        Most Active
                                        schrieb am zuletzt editiert von mickym
                                        #58

                                        @klaris Wie gesagt, falls du es mal probieren willst, das zigbee2mqtt - brauchst halt den mqtt Adapter und einen mqtt Broker.

                                        Eine grafische Oberfläche bringt das Tool auch mit:

                                        250cc3c8-f8c8-40cf-8a08-6c501b7aafb6-image.png

                                        so dass es auch in Deine VIS (als iFrame) oder bei mir in das NodeRed Dashboard einbinden kannst.

                                        Ich würde halt an deiner Stelle ein Image von Deiner SD Karte ziehen und das System parallel aufbauen, damit Du wenn Du nicht dazu kommst, halt Dein jetziges System am Laufen hast und parallel das Neue ans Laufen bringst.

                                        Jeder Flow bzw. jedes Script, das ich hier poste implementiert jeder auf eigene Gefahr. Flows und Scripts können Fehler aufweisen und weder der Seitenbetreiber noch ich persönlich können hierfür haftbar gemacht werden. Das gleiche gilt für Empfehlungen aller Art.

                                        K 1 Antwort Letzte Antwort
                                        0
                                        • mickymM mickym

                                          @klaris Wie gesagt, falls du es mal probieren willst, das zigbee2mqtt - brauchst halt den mqtt Adapter und einen mqtt Broker.

                                          Eine grafische Oberfläche bringt das Tool auch mit:

                                          250cc3c8-f8c8-40cf-8a08-6c501b7aafb6-image.png

                                          so dass es auch in Deine VIS (als iFrame) oder bei mir in das NodeRed Dashboard einbinden kannst.

                                          Ich würde halt an deiner Stelle ein Image von Deiner SD Karte ziehen und das System parallel aufbauen, damit Du wenn Du nicht dazu kommst, halt Dein jetziges System am Laufen hast und parallel das Neue ans Laufen bringst.

                                          K Offline
                                          K Offline
                                          klaris
                                          schrieb am zuletzt editiert von
                                          #59

                                          @mickym Das sieht ja vielversprechend aus…. Ja so hab ich es mir auch gedacht dass man zwei Parallelsysteme startet für alle Fälle …Aber schade dass die einfache Installation zigbee Adapter und ConBee so anfällig ist….

                                          mickymM 1 Antwort Letzte Antwort
                                          0
                                          Antworten
                                          • In einem neuen Thema antworten
                                          Anmelden zum Antworten
                                          • Älteste zuerst
                                          • Neuste zuerst
                                          • Meiste Stimmen


                                          Support us

                                          ioBroker
                                          Community Adapters
                                          Donate

                                          629

                                          Online

                                          32.5k

                                          Benutzer

                                          81.6k

                                          Themen

                                          1.3m

                                          Beiträge
                                          Community
                                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                                          ioBroker Community 2014-2025
                                          logo
                                          • Anmelden

                                          • Du hast noch kein Konto? Registrieren

                                          • Anmelden oder registrieren, um zu suchen
                                          • Erster Beitrag
                                            Letzter Beitrag
                                          0
                                          • Home
                                          • Aktuell
                                          • Tags
                                          • Ungelesen 0
                                          • Kategorien
                                          • Unreplied
                                          • Beliebt
                                          • GitHub
                                          • Docu
                                          • Hilfe