Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Error/Bug
    4. ZigBee Adapter/TI Board steigt immer wieder mal aus

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    ZigBee Adapter/TI Board steigt immer wieder mal aus

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

      @asgothian said in ZigBee Adapter/TI Board steigt immer wieder mal aus:

      Die Debug Meldungen bringen an dieser Stelle nichts. Wichtig sind die debug Meldungen der letzten 2 bis 3 Minuten bevor der Adapter neu gestartet werden soll. Gegebenenfalls ist an diesen Meldungen zu erkennen warum der Neustart notwendig wurde und was genau passiert ist.
      A.

      Ah dann hab ich dich falsch verstanden. Was meinst du denn mit "bevor der Adapter neu gestartet werden soll" ?

      Der Neustart geschieht ja nicht automatisch. Irgendwann verlieren mehr und mehr Sensoren die Verbindung. Ich bekomme das mit weil ich mich über Telegram darüber informieren lasse wenn Sensoren nicht mehr erreichbar sind. Die Liste wird dann länger und länger und dann weiß ich das was nicht stimmt. Wenn ich selber einen Neustart mache kommen die Meldungen von oben.

      Bin mir nicht ganz sicher wie ich dir die debug Meldungen liefern kann die du bräuchtest.

      Asgothian 1 Reply Last reply Reply Quote 0
      • M
        martinschm last edited by martinschm

        @thomas-braun said in ZigBee Adapter/TI Board steigt immer wieder mal aus:

        @martinschm sagte in ZigBee Adapter/TI Board steigt immer wieder mal aus:

        Hab jetzt mal geschaut, da sind dutzende Einträge aber welchen davon muß ich nehmen?

        Keinen.

        Man schaut in /dev/serial/by-id nach dem Gerät und gibt dann dessen Link an.

        Hi, sorry bin kein Linux-Experte. Hab jetzt mal nach der Seite die du gepostet hast den Befehl hier ausgeführt. Das Gerät läuft auf ttyACM0.

        martin@smarthome:~$  ls -l /dev/serial/by-id
        total 0
        lrwxrwxrwx 1 root root 13 Jul 31 13:46 usb-Texas_Instruments_XDS110__03.00.00.13                                               __Embed_with_CMSIS-DAP_L1100FA9-if00 -> ../../ttyACM0
        lrwxrwxrwx 1 root root 13 Jul 31 13:46 usb-Texas_Instruments_XDS110__03.00.00.13                                               __Embed_with_CMSIS-DAP_L1100FA9-if03 -> ../../ttyACM1
        

        Ich habe auch mal versucht mittels "ls -l /proc/[0-9]/fd/ |grep /dev/ttyACM0" raus zu bekommen was den Port verwendet, allerdings kommt da keinerlei Ausgabe wenn ich den Befehl ausführe. Weder in der iobroker VM noch auf dem proxmox System.

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

          @martinschm sagte in ZigBee Adapter/TI Board steigt immer wieder mal aus:

          Das Gerät läuft auf ttyACM0.

          Auch. Genauer: Eines der beiden Interfaces läuft auf ttyACM0.
          Das andere (vmtl. der Debugger) läuft auf ttyACM1

          Das kann sich aber auch ändern, daher nimmt man den Link auf die Gerätedatei, der passt immer.

          /dev/serial/by-id/usb-Texas_Instruments_XDS110__03.00.00.13__Embed_with_CMSIS-DAP_L1100FA9-if00
          

          dann wohl.

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

            @martinschm sagte in ZigBee Adapter/TI Board steigt immer wieder mal aus:

            Bin mir nicht ganz sicher wie ich dir die debug Meldungen liefern kann die du bräuchtest.

            Du musst den Adapter im Debug mit laufen lassen, bis der Effekt mit den ausfallenden Sensoren auftritt. Wenn du dich entscheidest den Adapter neu zu starten kannst du nach dem Neustart das Log herunterladen und die Einträge des Zigbee-Adapters der 5 Minuten aus dem Log posten kopieren und posten.

            Nebenbei: wenn nur einige Sensoren die Verbindung verlieren aber andere Geräte weiter funktionieren dann gibt es kein Problem mit dem USB / Seriellen Port, da ansonsten die Kommunikation zu ALLEN Sensoren abbrechen muss.

            A.

            M 1 Reply Last reply Reply Quote 0
            • M
              martinschm @Asgothian last edited by martinschm

              @asgothian said in ZigBee Adapter/TI Board steigt immer wieder mal aus:

              @martinschm sagte in ZigBee Adapter/TI Board steigt immer wieder mal aus:

              Bin mir nicht ganz sicher wie ich dir die debug Meldungen liefern kann die du bräuchtest.

              Du musst den Adapter im Debug mit laufen lassen, bis der Effekt mit den ausfallenden Sensoren auftritt. Wenn du dich entscheidest den Adapter neu zu starten kannst du nach dem Neustart das Log herunterladen und die Einträge des Zigbee-Adapters der 5 Minuten aus dem Log posten kopieren und posten.

              Nebenbei: wenn nur einige Sensoren die Verbindung verlieren aber andere Geräte weiter funktionieren dann gibt es kein Problem mit dem USB / Seriellen Port, da ansonsten die Kommunikation zu ALLEN Sensoren abbrechen muss.

              A.

              Hi,

              Dienstag sind wieder alle Sensoren rausgeflogen. Bin leider erst jetzt dazu gekommen den Adapter mal neu zu starten. Hier sind die Logs:

              2022-08-06 15:15:13.121 - info: host.smarthome instance system.adapter.daswetter.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
              2022-08-06 15:15:15.331 - info: admin.0 (967) failed connection to socket.io from ::ffff:192.168.1.33:
              2022-08-06 15:15:15.339 - error: admin.0 (967) Error: "error"
              2022-08-06 15:18:36.848 - error: zigbee.0 (528791) getGroups: caught error: TypeError: Cannot read properties of undefined (reading 'getGroups')
              2022-08-06 15:18:37.164 - debug: zigbee.0 (528791) List of ports: [{"comName":"/dev/ttyACM0"},{"comName":"/dev/ttyACM1"},{"comName":"/dev/ttyS0"},{"comName":"/dev/ttyS1"},{"comName":"/dev/ttyS10"},{"comName":"/dev/ttyS11"},{"comName":"/dev/ttyS12"},{"comName":"/dev/ttyS13"},{"comName":"/dev/ttyS14"},{"comName":"/dev/ttyS15"},{"comName":"/dev/ttyS16"},{"comName":"/dev/ttyS17"},{"comName":"/dev/ttyS18"},{"comName":"/dev/ttyS19"},{"comName":"/dev/ttyS2"},{"comName":"/dev/ttyS20"},{"comName":"/dev/ttyS21"},{"comName":"/dev/ttyS22"},{"comName":"/dev/ttyS23"},{"comName":"/dev/ttyS24"},{"comName":"/dev/ttyS25"},{"comName":"/dev/ttyS26"},{"comName":"/dev/ttyS27"},{"comName":"/dev/ttyS28"},{"comName":"/dev/ttyS29"},{"comName":"/dev/ttyS3"},{"comName":"/dev/ttyS30"},{"comName":"/dev/ttyS31"},{"comName":"/dev/ttyS4"},{"comName":"/dev/ttyS5"},{"comName":"/dev/ttyS6"},{"comName":"/dev/ttyS7"},{"comName":"/dev/ttyS8"},{"comName":"/dev/ttyS9"}]
              2022-08-06 15:18:47.804 - info: host.smarthome stopInstance system.adapter.zigbee.0 (force=false, process=true)
              2022-08-06 15:18:47.814 - info: zigbee.0 (528791) Got terminate signal TERMINATE_YOURSELF
              2022-08-06 15:18:47.821 - info: host.smarthome stopInstance system.adapter.zigbee.0 send kill signal
              2022-08-06 15:18:47.817 - info: zigbee.0 (528791) cleaned everything up...
              2022-08-06 15:18:47.834 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x00158d00033ad77d = false
              2022-08-06 15:18:47.843 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x00158d00033ad77d = 0
              2022-08-06 15:18:47.850 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x00158d0004b487d4 = false
              2022-08-06 15:18:47.867 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x00158d0004b487d4 = 0
              2022-08-06 15:18:47.871 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x00158d0004465ea3 = false
              2022-08-06 15:18:47.874 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x00158d0004465ea3 = 0
              2022-08-06 15:18:47.878 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x00158d0001b7ba2f = false
              2022-08-06 15:18:47.881 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x00158d0001b7ba2f = 0
              2022-08-06 15:18:47.886 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x00158d00044de796 = false
              2022-08-06 15:18:47.890 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x00158d00044de796 = 0
              2022-08-06 15:18:47.893 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x00158d0004460639 = false
              2022-08-06 15:18:47.897 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x00158d0004460639 = 0
              2022-08-06 15:18:47.900 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x00158d000485431c = false
              2022-08-06 15:18:47.904 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x00158d000485431c = 0
              2022-08-06 15:18:47.907 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x00158d0004462707 = false
              2022-08-06 15:18:47.910 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x00158d0004462707 = 0
              2022-08-06 15:18:47.914 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x00158d000420b185 = false
              2022-08-06 15:18:47.918 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x00158d000420b185 = 0
              2022-08-06 15:18:47.922 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x00158d000223a209 = false
              2022-08-06 15:18:47.925 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x00158d000223a209 = 0
              2022-08-06 15:18:47.928 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x00158d0004fcf82a = false
              2022-08-06 15:18:47.932 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x00158d0004fcf82a = 0
              2022-08-06 15:18:47.935 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x00158d0004fcf946 = false
              2022-08-06 15:18:47.939 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x00158d0004fcf946 = 0
              2022-08-06 15:18:47.942 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x00158d0004b487e0 = false
              2022-08-06 15:18:47.945 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x00158d0004b487e0 = 0
              2022-08-06 15:18:47.949 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x00158d0004fc9476 = false
              2022-08-06 15:18:47.952 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x00158d0004fc9476 = 0
              2022-08-06 15:18:47.955 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x14b457fffe72bcba = false
              2022-08-06 15:18:47.958 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x14b457fffe72bcba = 0
              2022-08-06 15:18:47.961 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x04cf8cdf3c7db935 = false
              2022-08-06 15:18:47.966 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x04cf8cdf3c7db935 = 0
              2022-08-06 15:18:47.970 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x14b457fffe2ea155 = false
              2022-08-06 15:18:47.973 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x14b457fffe2ea155 = 0
              2022-08-06 15:18:47.976 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x00158d00041cc7da = false
              2022-08-06 15:18:47.979 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x00158d00041cc7da = 0
              2022-08-06 15:18:47.983 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x00158d00031b35bf = false
              2022-08-06 15:18:47.985 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x00158d00031b35bf = 0
              2022-08-06 15:18:47.988 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x00158d0001b95a50 = false
              2022-08-06 15:18:47.990 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x00158d0001b95a50 = 0
              2022-08-06 15:18:47.992 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x00158d000201b693 = false
              2022-08-06 15:18:47.996 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x00158d000201b693 = 0
              2022-08-06 15:18:47.999 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x00158d00022b39fa = false
              2022-08-06 15:18:48.001 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x00158d00022b39fa = 0
              2022-08-06 15:18:48.003 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x00158d0001de8f8a = false
              2022-08-06 15:18:48.005 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x00158d0001de8f8a = 0
              2022-08-06 15:18:48.010 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x00158d0001fa5cab = false
              2022-08-06 15:18:48.014 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x00158d0001fa5cab = 0
              2022-08-06 15:18:48.018 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x00158d0001b7a818 = false
              2022-08-06 15:18:48.021 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x00158d0001b7a818 = 0
              2022-08-06 15:18:48.023 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x00158d0002235296 = false
              2022-08-06 15:18:48.026 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x00158d0002235296 = 0
              2022-08-06 15:18:48.029 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x00158d0001e459f9 = false
              2022-08-06 15:18:48.031 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x00158d0001e459f9 = 0
              2022-08-06 15:18:48.033 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x00158d0001de8c5e = false
              2022-08-06 15:18:48.035 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x00158d0001de8c5e = 0
              2022-08-06 15:18:48.039 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x00158d0001fd6f2f = false
              2022-08-06 15:18:48.041 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x00158d0001fd6f2f = 0
              2022-08-06 15:18:48.044 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x00158d0001de89bc = false
              2022-08-06 15:18:48.046 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x00158d0001de89bc = 0
              2022-08-06 15:18:48.048 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x00158d0001b7b572 = false
              2022-08-06 15:18:48.052 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x00158d0001b7b572 = 0
              2022-08-06 15:18:48.054 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x00158d0001b7ace5 = false
              2022-08-06 15:18:48.056 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x00158d0001b7ace5 = 0
              2022-08-06 15:18:48.058 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x00158d00022cb2d5 = false
              2022-08-06 15:18:48.061 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x00158d00022cb2d5 = 0
              2022-08-06 15:18:48.064 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x00158d0001de6190 = false
              2022-08-06 15:18:48.066 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x00158d0001de6190 = 0
              2022-08-06 15:18:48.069 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x00158d0004fcf923 = false
              2022-08-06 15:18:48.071 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x00158d0004fcf923 = 0
              2022-08-06 15:18:48.073 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x00158d0001e48a72 = false
              2022-08-06 15:18:48.076 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x00158d0001e48a72 = 0
              2022-08-06 15:18:48.079 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x00158d0001e489c1 = false
              2022-08-06 15:18:48.081 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x00158d0001e489c1 = 0
              2022-08-06 15:18:48.083 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x00158d0001b9589f = false
              2022-08-06 15:18:48.086 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x00158d0001b9589f = 0
              2022-08-06 15:18:48.089 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x00158d0002019669 = false
              2022-08-06 15:18:48.091 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x00158d0002019669 = 0
              2022-08-06 15:18:48.093 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x00158d0001b7b481 = false
              2022-08-06 15:18:48.095 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x00158d0001b7b481 = 0
              2022-08-06 15:18:48.097 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x04cd15fffe02d9f3 = false
              2022-08-06 15:18:48.100 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x04cd15fffe02d9f3 = 0
              2022-08-06 15:18:48.102 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x00158d0001b7a88a = false
              2022-08-06 15:18:48.104 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x00158d0001b7a88a = 0
              2022-08-06 15:18:48.106 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x00158d00027051c6 = false
              2022-08-06 15:18:48.108 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x00158d00027051c6 = 0
              2022-08-06 15:18:48.111 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x00158d00041cc629 = false
              2022-08-06 15:18:48.113 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x00158d00041cc629 = 0
              2022-08-06 15:18:48.115 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x04cd15fffe02d085 = false
              2022-08-06 15:18:48.117 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x04cd15fffe02d085 = 0
              2022-08-06 15:18:48.119 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x00158d0001e42cf4 = false
              2022-08-06 15:18:48.122 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x00158d0001e42cf4 = 0
              2022-08-06 15:18:48.124 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x00158d0002271d3f = false
              2022-08-06 15:18:48.126 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x00158d0002271d3f = 0
              2022-08-06 15:18:48.128 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x00158d0002f90eff = false
              2022-08-06 15:18:48.130 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x00158d0002f90eff = 0
              2022-08-06 15:18:48.133 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x00158d0002f3c080 = false
              2022-08-06 15:18:48.135 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x00158d0002f3c080 = 0
              2022-08-06 15:18:48.137 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x00158d0002f39851 = false
              2022-08-06 15:18:48.139 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x00158d0002f39851 = 0
              2022-08-06 15:18:48.141 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x00158d00053fbd6f = false
              2022-08-06 15:18:48.144 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x00158d00053fbd6f = 0
              2022-08-06 15:18:48.146 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x00158d0001de72f5 = false
              2022-08-06 15:18:48.148 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x00158d0001de72f5 = 0
              2022-08-06 15:18:48.150 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x00158d0002f39894 = false
              2022-08-06 15:18:48.152 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x00158d0002f39894 = 0
              2022-08-06 15:18:48.155 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x00158d00033a4347 = false
              2022-08-06 15:18:48.157 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x00158d00033a4347 = 0
              2022-08-06 15:18:48.159 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x00158d0001ddab4c = false
              2022-08-06 15:18:48.161 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x00158d0001ddab4c = 0
              2022-08-06 15:18:48.163 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x00158d0004fd0fd7 = false
              2022-08-06 15:18:48.166 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x00158d0004fd0fd7 = 0
              2022-08-06 15:18:48.168 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x00158d00048605a0 = false
              2022-08-06 15:18:48.170 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x00158d00048605a0 = 0
              2022-08-06 15:18:48.172 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x842e14fffe1262bf = false
              2022-08-06 15:18:48.174 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x842e14fffe1262bf = 0
              2022-08-06 15:18:48.178 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x588e81fffedbcfe2 = false
              2022-08-06 15:18:48.180 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x588e81fffedbcfe2 = 0
              2022-08-06 15:18:48.182 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x842e14fffe35a210 = false
              2022-08-06 15:18:48.184 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x842e14fffe35a210 = 0
              2022-08-06 15:18:48.186 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x00158d000485f414 = false
              2022-08-06 15:18:48.190 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x00158d000485f414 = 0
              2022-08-06 15:18:48.192 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x00158d000482d34e = false
              2022-08-06 15:18:48.194 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x00158d000482d34e = 0
              2022-08-06 15:18:48.196 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x00158d0001e7a0d0 = false
              2022-08-06 15:18:48.199 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x00158d0001e7a0d0 = 0
              2022-08-06 15:18:48.203 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x04cd15fffe067cd7 = false
              2022-08-06 15:18:48.206 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x04cd15fffe067cd7 = 0
              2022-08-06 15:18:48.211 - debug: zigbee.0 (528791) DeviceAvailability:Publish available for 0x04cd15fffe02dd9b = false
              2022-08-06 15:18:48.215 - debug: zigbee.0 (528791) DeviceAvailability:Publish LQ for 0x04cd15fffe02dd9b = 0
              2022-08-06 15:18:48.254 - info: zigbee.0 (528791) Zigbee: disabling joining new devices.
              2022-08-06 15:18:48.293 - warn: zigbee.0 (528791) Failed to stop zigbee during startup
              2022-08-06 15:18:48.296 - info: zigbee.0 (528791) terminating
              2022-08-06 15:18:48.301 - debug: zigbee.0 (528791) Plugin sentry destroyed
              2022-08-06 15:18:48.303 - info: zigbee.0 (528791) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
              2022-08-06 15:18:48.824 - info: host.smarthome stopInstance system.adapter.zigbee.0 killing pid 528791
              2022-08-06 15:18:49.258 - info: iqontrol.0 (1391) COUNTER Adapter-Monitor Red: 1 of 41
              2022-08-06 15:18:49.357 - info: host.smarthome instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
              2022-08-06 15:18:51.210 - info: host.smarthome instance system.adapter.zigbee.0 started with pid 2507142
              2022-08-06 15:18:56.556 - debug: zigbee.0 (2507142) Redis Objects: Use Redis connection: 0.0.0.0:9001
              2022-08-06 15:18:56.733 - debug: zigbee.0 (2507142) Objects client ready ... initialize now
              2022-08-06 15:18:56.742 - debug: zigbee.0 (2507142) Objects create System PubSub Client
              2022-08-06 15:18:56.744 - debug: zigbee.0 (2507142) Objects create User PubSub Client
              2022-08-06 15:18:56.959 - debug: zigbee.0 (2507142) Objects client initialize lua scripts
              2022-08-06 15:18:56.985 - debug: zigbee.0 (2507142) Objects connected to redis: 0.0.0.0:9001
              2022-08-06 15:18:57.055 - debug: zigbee.0 (2507142) Redis States: Use Redis connection: 0.0.0.0:6379
              2022-08-06 15:18:57.065 - debug: zigbee.0 (2507142) States create System PubSub Client
              2022-08-06 15:18:57.067 - debug: zigbee.0 (2507142) States create User PubSub Client
              2022-08-06 15:18:57.080 - debug: zigbee.0 (2507142) States connected to redis: 0.0.0.0:6379
              2022-08-06 15:18:57.171 - debug: zigbee.0 (2507142) Plugin sentry Initialize Plugin (enabled=true)
              2022-08-06 15:18:57.182 - info: zigbee.0 (2507142) Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system
              2022-08-06 15:18:57.759 - info: zigbee.0 (2507142) starting. Version 1.7.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v16.16.0, js-controller: 4.0.23
              2022-08-06 15:18:57.810 - debug: zigbee.0 (2507142) Using zigbee-herdsman with settings: {"network":{"panID":6760,"extendedPanID":[221,221,221,221,221,221,221,221],"channelList":[20],"networkKey":[65,13,71,170,250,97,77,91,118,169,226,122,181,218,124,204]},"databasePath":"/opt/iobroker/iobroker-data/zigbee_0/shepherd.db","backupPath":"/opt/iobroker/iobroker-data/zigbee_0/nvbackup.json","serialPort":{"baudRate":115200,"rtscts":false,"path":"/dev/ttyACM0","adapter":"zstack"},"adapter":{"forceStartWithInconsistentAdapterConfiguration":false}}
              2022-08-06 15:18:57.889 - info: zigbee.0 (2507142) delete old Backup files. keep only last 10
              2022-08-06 15:18:57.891 - info: zigbee.0 (2507142) Starting Zigbee npm ...
              2022-08-06 15:18:57.893 - debug: zigbee.0 (2507142) Starting zigbee-herdsman...
              2022-08-06 15:18:58.612 - debug: zigbee.0 (2507142) zigbee-herdsman:adapter Path '/dev/ttyACM0' is valid for 'ZStackAdapter'
              2022-08-06 15:18:58.616 - debug: zigbee.0 (2507142) zigbee-herdsman:controller:log Starting with options '{"network":{"networkKeyDistribute":false,"networkKey":[65,13,71,170,250,97,77,91,118,169,226,122,181,218,124,204],"panID":6760,"extendedPanID":[221,221,221,221,221,221,221,221],"channelList":[20]},"serialPort":{"baudRate":115200,"rtscts":false,"path":"/dev/ttyACM0","adapter":"zstack"},"databasePath":"/opt/iobroker/iobroker-data/zigbee_0/shepherd.db","databaseBackupPath":null,"backupPath":"/opt/iobroker/iobroker-data/zigbee_0/nvbackup.json","adapter":{"disableLED":false,"forceStartWithInconsistentAdapterConfiguration":false},"acceptJoiningDeviceHandler":null}'
              2022-08-06 15:18:58.617 - debug: zigbee.0 (2507142) zigbee-herdsman:adapter:zStack:znp:log Opening SerialPort with /dev/ttyACM0 and {"baudRate":115200,"rtscts":false,"autoOpen":false}
              2022-08-06 15:18:58.641 - debug: zigbee.0 (2507142) zigbee-herdsman:adapter:zStack:znp:log Serialport opened
              2022-08-06 15:18:58.646 - debug: zigbee.0 (2507142) zigbee-herdsman:adapter:zStack:znp:SREQ --> SYS - ping - {"capabilities":1}
              2022-08-06 15:18:58.650 - debug: zigbee.0 (2507142) zigbee-herdsman:adapter:zStack:unpi:writer --> frame [254,0,33,1,32]
              2022-08-06 15:18:58.656 - info: zigbee.0 (2507142) Installed Version: iobroker.zigbee@1.7.5
              2022-08-06 15:18:58.681 - debug: zigbee.0 (2507142) Backup /opt/iobroker/iobroker-data/zigbee_0/backup_2022_08_06-15_18_57.tar.gz success
              2022-08-06 15:18:58.757 - info: iqontrol.0 (1391) COUNTER Adapter-Monitor Red: 0 of 41
              2022-08-06 15:18:58.893 - info: iqontrol.0 (1391) COUNTER Adapter-Monitor Yellow: 1 of 41
              2022-08-06 15:18:58.907 - debug: zigbee.0 (2507142) zigbee-herdsman:adapter:zStack:znp:log Writing CC2530/CC2531 skip bootloader payload
              2022-08-06 15:18:58.908 - debug: zigbee.0 (2507142) zigbee-herdsman:adapter:zStack:unpi:writer --> buffer [239]
              2022-08-06 15:18:58.948 - info: iqontrol.0 (1391) COUNTER Adapter-Monitor Green: 40 of 41
              2022-08-06 15:18:58.968 - info: iqontrol.0 (1391) CALCULATION Adapter-Monitor Red+Yellow has changed
              2022-08-06 15:18:58.970 - info: iqontrol.0 (1391) COMBINATION Adapter-Monitor HTML has changed
              2022-08-06 15:18:58.973 - info: iqontrol.0 (1391) CALCULATION Adapter-Monitor Red+Yellow_LIST has changed
              2022-08-06 15:18:58.981 - info: iqontrol.0 (1391) CALCULATION Adapter-Monitor Red+Yellow_LIST_JSON has changed
              2022-08-06 15:18:58.987 - info: iqontrol.0 (1391) CALCULATION Adapter-Monitor Red+Yellow_NAMES_LIST has changed
              2022-08-06 15:18:59.911 - debug: zigbee.0 (2507142) zigbee-herdsman:adapter:zStack:znp:SREQ --> SYS - ping - {"capabilities":1}
              2022-08-06 15:18:59.912 - debug: zigbee.0 (2507142) zigbee-herdsman:adapter:zStack:unpi:writer --> frame [254,0,33,1,32]
              2022-08-06 15:19:00.163 - debug: zigbee.0 (2507142) zigbee-herdsman:adapter:zStack:znp:log Skip bootloader for CC2652/CC1352
              2022-08-06 15:19:00.660 - debug: zigbee.0 (2507142) zigbee-herdsman:adapter:zStack:znp:SREQ --> SYS - ping - {"capabilities":1}
              2022-08-06 15:19:00.662 - debug: zigbee.0 (2507142) zigbee-herdsman:adapter:zStack:unpi:writer --> frame [254,0,33,1,32]
              2022-08-06 15:19:06.664 - debug: zigbee.0 (2507142) zigbee-herdsman:adapter:zStack:znp:SREQ --> SYS - ping - {"capabilities":1}
              2022-08-06 15:19:06.665 - debug: zigbee.0 (2507142) zigbee-herdsman:adapter:zStack:unpi:writer --> frame [254,0,33,1,32]
              2022-08-06 15:19:12.667 - debug: zigbee.0 (2507142) zigbee-herdsman:adapter:zStack:znp:SREQ --> SYS - ping - {"capabilities":1}
              2022-08-06 15:19:12.669 - debug: zigbee.0 (2507142) zigbee-herdsman:adapter:zStack:unpi:writer --> frame [254,0,33,1,32]
              2022-08-06 15:19:18.672 - error: zigbee.0 (2507142) Starting zigbee-herdsman problem : "Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)"
              2022-08-06 15:19:18.673 - error: zigbee.0 (2507142) Failed to start Zigbee
              2022-08-06 15:19:18.673 - error: zigbee.0 (2507142) Error herdsman start
              2022-08-06 15:19:28.675 - info: zigbee.0 (2507142) Try to reconnect. 1 attempts left
              2022-08-06 15:19:28.677 - info: zigbee.0 (2507142) Starting Zigbee npm ...
              2022-08-06 15:19:28.678 - debug: zigbee.0 (2507142) Starting zigbee-herdsman...
              2022-08-06 15:19:28.711 - info: zigbee.0 (2507142) Installed Version: iobroker.zigbee@1.7.5
              2022-08-06 15:19:28.928 - debug: zigbee.0 (2507142) zigbee-herdsman:adapter Path '/dev/ttyACM0' is valid for 'ZStackAdapter'
              2022-08-06 15:19:28.929 - debug: zigbee.0 (2507142) zigbee-herdsman:controller:log Starting with options '{"network":{"networkKeyDistribute":false,"networkKey":[65,13,71,170,250,97,77,91,118,169,226,122,181,218,124,204],"panID":6760,"extendedPanID":[221,221,221,221,221,221,221,221],"channelList":[20]},"serialPort":{"baudRate":115200,"rtscts":false,"path":"/dev/ttyACM0","adapter":"zstack"},"databasePath":"/opt/iobroker/iobroker-data/zigbee_0/shepherd.db","databaseBackupPath":null,"backupPath":"/opt/iobroker/iobroker-data/zigbee_0/nvbackup.json","adapter":{"disableLED":false,"forceStartWithInconsistentAdapterConfiguration":false},"acceptJoiningDeviceHandler":null}'
              2022-08-06 15:19:28.930 - debug: zigbee.0 (2507142) zigbee-herdsman:adapter:zStack:znp:log Opening SerialPort with /dev/ttyACM0 and {"baudRate":115200,"rtscts":false,"autoOpen":false}
              2022-08-06 15:19:28.984 - error: zigbee.0 (2507142) Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'"
              2022-08-06 15:19:28.985 - error: zigbee.0 (2507142) Failed to start Zigbee
              2022-08-06 15:19:28.986 - error: zigbee.0 (2507142) Error herdsman start
              2022-08-06 15:19:42.833 - info: web-speedy.0 (1994) Execute timer with : 1800000 Currently running : false
              2022-08-06 15:19:42.835 - info: web-speedy.0 (1994) Run test on on Best Server found
              2022-08-06 15:19:42.839 - info: web-speedy.0 (1994) The speed test has been started and will take at maximum 5 seconds for a single test run
              2022-08-06 15:19:43.324 - info: web-speedy.0 (1994) Closest server found, running test
              

              und hier noch die Logs von Dienstag rund um die Zeit wo die Sensoren ausgestiegen sind:

              2022-08-02 11:12:06.517 - info: zigbee.0 (1286) Zigbee: allowing new devices to join.
              2022-08-02 11:12:24.869 - error: zigbee.0 (1286) Failed to open the network: Error: SRSP - ZDO - mgmtPermitJoinReq after 6000ms
              at Timeout._onTimeout (/opt/iobroker/node_modules/zigbee-herdsman/dist/utils/waitress.js:37:35)
              at listOnTimeout (node:internal/timers:559:17)
              at processTimers (node:internal/timers:502:7)
              2022-08-02 11:12:54.560 - info: iqontrol.0 (1391) COUNTER Adapter-Monitor Red: 0 of 41
              2022-08-02 11:12:54.711 - info: iqontrol.0 (1391) COUNTER Adapter-Monitor Yellow: 1 of 41
              2022-08-02 11:12:54.754 - info: iqontrol.0 (1391) COUNTER Adapter-Monitor Green: 40 of 41
              2022-08-02 11:13:15.108 - info: host.smarthome stopInstance system.adapter.zigbee.0 (force=false, process=true)
              2022-08-02 11:13:15.114 - info: zigbee.0 (1286) Got terminate signal TERMINATE_YOURSELF
              2022-08-02 11:13:15.394 - info: host.smarthome stopInstance system.adapter.zigbee.0 send kill signal
              2022-08-02 11:13:15.117 - info: zigbee.0 (1286) cleaned everything up...
              2022-08-02 11:13:15.412 - info: zigbee.0 (1286) Zigbee: disabling joining new devices.
              2022-08-02 11:13:15.619 - info: zigbee.0 (1286) terminating
              2022-08-02 11:13:15.621 - info: zigbee.0 (1286) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
              2022-08-02 11:13:16.623 - info: zigbee.0 (1286) terminating with timeout
              2022-08-02 11:13:17.101 - info: host.smarthome stopInstance system.adapter.zigbee.0 killing pid 1286
              2022-08-02 11:13:18.678 - info: iqontrol.0 (1391) COUNTER Adapter-Monitor Red: 1 of 41
              2022-08-02 11:13:18.868 - info: iqontrol.0 (1391) COUNTER Adapter-Monitor Yellow: 1 of 41
              2022-08-02 11:13:18.902 - info: host.smarthome instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
              2022-08-02 11:13:24.435 - debug: zigbee.0 (518638) Redis Objects: Use Redis connection: 0.0.0.0:9001
              2022-08-02 11:13:24.533 - debug: zigbee.0 (518638) Objects client ready ... initialize now
              2022-08-02 11:13:24.536 - debug: zigbee.0 (518638) Objects create System PubSub Client
              2022-08-02 11:13:24.538 - debug: zigbee.0 (518638) Objects create User PubSub Client
              2022-08-02 11:13:24.657 - debug: zigbee.0 (518638) Objects client initialize lua scripts
              2022-08-02 11:13:24.668 - debug: zigbee.0 (518638) Objects connected to redis: 0.0.0.0:9001
              2022-08-02 11:13:24.728 - debug: zigbee.0 (518638) Redis States: Use Redis connection: 0.0.0.0:6379
              2022-08-02 11:13:24.739 - debug: zigbee.0 (518638) States create System PubSub Client
              2022-08-02 11:13:24.741 - debug: zigbee.0 (518638) States create User PubSub Client
              2022-08-02 11:13:24.756 - debug: zigbee.0 (518638) States connected to redis: 0.0.0.0:6379
              2022-08-02 11:13:24.832 - debug: zigbee.0 (518638) Plugin sentry Initialize Plugin (enabled=true)
              2022-08-02 11:13:24.839 - info: zigbee.0 (518638) Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system
              2022-08-02 11:13:25.349 - info: zigbee.0 (518638) starting. Version 1.7.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v16.16.0, js-controller: 4.0.23
              2022-08-02 11:13:25.400 - debug: zigbee.0 (518638) Using zigbee-herdsman with settings: {"network":{"panID":6760,"extendedPanID":[221,221,221,221,221,221,221,221],"channelList":[20],"networkKey":[65,13,71,170,250,97,77,91,118,169,226,122,181,218,124,204]},"databasePath":"/opt/iobroker/iobroker-data/zigbee_0/shepherd.db","backupPath":"/opt/iobroker/iobroker-data/zigbee_0/nvbackup.json","serialPort":{"baudRate":115200,"rtscts":false,"path":"/dev/ttyACM0","adapter":"zstack"},"adapter":{"forceStartWithInconsistentAdapterConfiguration":false}}
              2022-08-02 11:13:25.474 - info: zigbee.0 (518638) delete old Backup files. keep only last 10
              2022-08-02 11:13:25.476 - info: zigbee.0 (518638) Starting Zigbee npm ...
              2022-08-02 11:13:25.478 - debug: zigbee.0 (518638) Starting zigbee-herdsman...
              2022-08-02 11:13:26.286 - info: zigbee.0 (518638) Installed Version: iobroker.zigbee@1.7.5
              2022-08-02 11:13:26.305 - debug: zigbee.0 (518638) Backup /opt/iobroker/iobroker-data/zigbee_0/backup_2022_08_02-11_13_25.tar.gz success
              2022-08-02 11:13:46.280 - error: zigbee.0 (518638) Starting zigbee-herdsman problem : "Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)"
              2022-08-02 11:13:46.281 - error: zigbee.0 (518638) Failed to start Zigbee
              2022-08-02 11:13:46.282 - error: zigbee.0 (518638) Error herdsman start
              2022-08-02 11:13:56.284 - info: zigbee.0 (518638) Try to reconnect. 1 attempts left
              2022-08-02 11:13:56.285 - info: zigbee.0 (518638) Starting Zigbee npm ...
              2022-08-02 11:13:56.286 - debug: zigbee.0 (518638) Starting zigbee-herdsman...
              2022-08-02 11:13:56.323 - info: zigbee.0 (518638) Installed Version: iobroker.zigbee@1.7.5
              2022-08-02 11:13:56.584 - error: zigbee.0 (518638) Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'"
              2022-08-02 11:13:56.587 - error: zigbee.0 (518638) Failed to start Zigbee
              2022-08-02 11:13:56.587 - error: zigbee.0 (518638) Error herdsman start
              2022-08-02 11:14:00.053 - info: host.smarthome instance system.adapter.sma-speedwire.0 started with pid 519800
              2022-08-02 11:14:02.642 - info: sma-speedwire.0 (519800) starting. Version 0.6.6 (non-npm: https://github.com/AttackStrawbery/ioBroker.sma-speedwire/tarball/b81e43b5de4409beff5ecdc1fe4be714ab4bbfbd) in /opt/iobroker/node_modules/iobroker.sma-speedwire, node: v16.16.0, js-controller: 4.0.23
              2022-08-02 11:14:03.749 - info: host.smarthome instance system.adapter.sma-speedwire.0 terminated with code 0 (NO_ERROR)
              2022-08-02 11:15:00.118 - info: host.smarthome instance system.adapter.daswetter.0 started with pid 521618
              2022-08-02 11:15:02.305 - info: daswetter.0 (521618) Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system
              2022-08-02 11:15:02.680 - info: daswetter.0 (521618) starting. Version 3.1.2 in /opt/iobroker/node_modules/iobroker.daswetter, node: v16.16.0, js-controller: 4.0.23
              2022-08-02 11:15:04.219 - info: iqontrol.0 (1391) COUNTER SABOTAGE ACTUAL: 0 of 292
              2022-08-02 11:15:04.591 - info: iqontrol.0 (1391) COUNTER ERROR ACTUAL: 2 of 292
              2022-08-02 11:15:12.364 - info: daswetter.0 (521618) Terminated (ADAPTER_REQUESTED_TERMINATION): All data handled, adapter stopped until next scheduled moment
              2022-08-02 11:15:12.887 - info: daswetter.0 (521618) cleaned everything up...
              2022-08-02 11:15:12.902 - info: host.smarthome instance system.adapter.daswetter.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
              2022-08-02 11:16:00.068 - info: host.smarthome instance system.adapter.sma-speedwire.0 started with pid 523268
              2022-08-02 11:16:02.594 - info: sma-speedwire.0 (523268) starting. Version 0.6.6 (non-npm: https://github.com/AttackStrawbery/ioBroker.sma-speedwire/tarball/b81e43b5de4409beff5ecdc1fe4be714ab4bbfbd) in /opt/iobroker/node_modules/iobroker.sma-speedwire, node: v16.16.0, js-controller: 4.0.23
              2022-08-02 11:16:03.698 - info: host.smarthome instance system.adapter.sma-speedwire.0 terminated with code 0 (NO_ERROR)
              2022-08-02 11:17:31.614 - info: host.smarthome "system.adapter.zigbee.0" disabled
              2022-08-02 11:17:31.616 - info: host.smarthome stopInstance system.adapter.zigbee.0 (force=false, process=true)
              2022-08-02 11:17:31.621 - info: zigbee.0 (518638) Got terminate signal TERMINATE_YOURSELF
              2022-08-02 11:17:31.623 - info: zigbee.0 (518638) cleaned everything up...
              2022-08-02 11:17:31.635 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x00158d00033ad77d = false
              2022-08-02 11:17:31.642 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x00158d00033ad77d = 0
              2022-08-02 11:17:31.649 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x00158d0004b487d4 = false
              2022-08-02 11:17:31.667 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x00158d0004b487d4 = 0
              2022-08-02 11:17:31.671 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x00158d0004465ea3 = false
              2022-08-02 11:17:31.675 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x00158d0004465ea3 = 0
              2022-08-02 11:17:31.679 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x00158d0001b7ba2f = false
              2022-08-02 11:17:31.683 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x00158d0001b7ba2f = 0
              2022-08-02 11:17:31.687 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x00158d00044de796 = false
              2022-08-02 11:17:31.690 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x00158d00044de796 = 0
              2022-08-02 11:17:31.695 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x00158d0004460639 = false
              2022-08-02 11:17:31.698 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x00158d0004460639 = 0
              2022-08-02 11:17:31.705 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x00158d000485431c = false
              2022-08-02 11:17:31.708 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x00158d000485431c = 0
              2022-08-02 11:17:31.711 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x00158d0004462707 = false
              2022-08-02 11:17:31.716 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x00158d0004462707 = 0
              2022-08-02 11:17:31.722 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x00158d000420b185 = false
              2022-08-02 11:17:31.728 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x00158d000420b185 = 0
              2022-08-02 11:17:31.732 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x00158d000223a209 = false
              2022-08-02 11:17:31.735 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x00158d000223a209 = 0
              2022-08-02 11:17:31.739 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x00158d0004fcf82a = false
              2022-08-02 11:17:31.742 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x00158d0004fcf82a = 0
              2022-08-02 11:17:31.745 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x00158d0004fcf946 = false
              2022-08-02 11:17:31.748 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x00158d0004fcf946 = 0
              2022-08-02 11:17:31.751 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x00158d0004b487e0 = false
              2022-08-02 11:17:31.754 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x00158d0004b487e0 = 0
              2022-08-02 11:17:31.757 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x00158d0004fc9476 = false
              2022-08-02 11:17:31.760 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x00158d0004fc9476 = 0
              2022-08-02 11:17:31.763 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x14b457fffe72bcba = false
              2022-08-02 11:17:31.766 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x14b457fffe72bcba = 0
              2022-08-02 11:17:31.769 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x04cf8cdf3c7db935 = false
              2022-08-02 11:17:31.771 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x04cf8cdf3c7db935 = 0
              2022-08-02 11:17:31.775 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x14b457fffe2ea155 = false
              2022-08-02 11:17:31.777 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x14b457fffe2ea155 = 0
              2022-08-02 11:17:31.780 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x00158d00041cc7da = false
              2022-08-02 11:17:31.783 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x00158d00041cc7da = 0
              2022-08-02 11:17:31.789 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x00158d00031b35bf = false
              2022-08-02 11:17:31.794 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x00158d00031b35bf = 0
              2022-08-02 11:17:31.796 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x00158d0001b95a50 = false
              2022-08-02 11:17:31.799 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x00158d0001b95a50 = 0
              2022-08-02 11:17:31.802 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x00158d000201b693 = false
              2022-08-02 11:17:31.804 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x00158d000201b693 = 0
              2022-08-02 11:17:31.810 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x00158d00022b39fa = false
              2022-08-02 11:17:31.814 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x00158d00022b39fa = 0
              2022-08-02 11:17:31.819 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x00158d0001de8f8a = false
              2022-08-02 11:17:31.824 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x00158d0001de8f8a = 0
              2022-08-02 11:17:31.829 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x00158d0001fa5cab = false
              2022-08-02 11:17:31.834 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x00158d0001fa5cab = 0
              2022-08-02 11:17:31.839 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x00158d0001b7a818 = false
              2022-08-02 11:17:31.844 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x00158d0001b7a818 = 0
              2022-08-02 11:17:31.850 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x00158d0002235296 = false
              2022-08-02 11:17:31.854 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x00158d0002235296 = 0
              2022-08-02 11:17:31.859 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x00158d0001e459f9 = false
              2022-08-02 11:17:31.862 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x00158d0001e459f9 = 0
              2022-08-02 11:17:31.864 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x00158d0001de8c5e = false
              2022-08-02 11:17:31.868 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x00158d0001de8c5e = 0
              2022-08-02 11:17:31.871 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x00158d0001fd6f2f = false
              2022-08-02 11:17:31.875 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x00158d0001fd6f2f = 0
              2022-08-02 11:17:31.878 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x00158d0001de89bc = false
              2022-08-02 11:17:31.880 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x00158d0001de89bc = 0
              2022-08-02 11:17:31.883 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x00158d0001b7b572 = false
              2022-08-02 11:17:31.886 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x00158d0001b7b572 = 0
              2022-08-02 11:17:31.889 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x00158d0001b7ace5 = false
              2022-08-02 11:17:31.892 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x00158d0001b7ace5 = 0
              2022-08-02 11:17:31.895 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x00158d00022cb2d5 = false
              2022-08-02 11:17:31.897 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x00158d00022cb2d5 = 0
              2022-08-02 11:17:31.900 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x00158d0001de6190 = false
              2022-08-02 11:17:31.903 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x00158d0001de6190 = 0
              2022-08-02 11:17:31.906 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x00158d0004fcf923 = false
              2022-08-02 11:17:31.909 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x00158d0004fcf923 = 0
              2022-08-02 11:17:31.911 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x00158d0001e48a72 = false
              2022-08-02 11:17:31.913 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x00158d0001e48a72 = 0
              2022-08-02 11:17:31.918 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x00158d0001e489c1 = false
              2022-08-02 11:17:31.921 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x00158d0001e489c1 = 0
              2022-08-02 11:17:31.932 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x00158d0001b9589f = false
              2022-08-02 11:17:31.935 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x00158d0001b9589f = 0
              2022-08-02 11:17:31.937 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x00158d0002019669 = false
              2022-08-02 11:17:31.941 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x00158d0002019669 = 0
              2022-08-02 11:17:31.944 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x00158d0001b7b481 = false
              2022-08-02 11:17:31.946 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x00158d0001b7b481 = 0
              2022-08-02 11:17:31.949 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x04cd15fffe02d9f3 = false
              2022-08-02 11:17:31.951 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x04cd15fffe02d9f3 = 0
              2022-08-02 11:17:31.956 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x00158d0001b7a88a = false
              2022-08-02 11:17:31.958 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x00158d0001b7a88a = 0
              2022-08-02 11:17:31.961 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x00158d00027051c6 = false
              2022-08-02 11:17:31.964 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x00158d00027051c6 = 0
              2022-08-02 11:17:31.966 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x00158d00041cc629 = false
              2022-08-02 11:17:31.971 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x00158d00041cc629 = 0
              2022-08-02 11:17:31.974 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x04cd15fffe02d085 = false
              2022-08-02 11:17:31.976 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x04cd15fffe02d085 = 0
              2022-08-02 11:17:31.979 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x00158d0001e42cf4 = false
              2022-08-02 11:17:31.981 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x00158d0001e42cf4 = 0
              2022-08-02 11:17:31.985 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x00158d0002271d3f = false
              2022-08-02 11:17:31.987 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x00158d0002271d3f = 0
              2022-08-02 11:17:31.990 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x00158d0002f90eff = false
              2022-08-02 11:17:31.992 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x00158d0002f90eff = 0
              2022-08-02 11:17:31.995 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x00158d0002f3c080 = false
              2022-08-02 11:17:31.998 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x00158d0002f3c080 = 0
              2022-08-02 11:17:32.000 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x00158d0002f39851 = false
              2022-08-02 11:17:32.003 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x00158d0002f39851 = 0
              2022-08-02 11:17:32.005 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x00158d00053fbd6f = false
              2022-08-02 11:17:32.008 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x00158d00053fbd6f = 0
              2022-08-02 11:17:32.026 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x00158d0001de72f5 = false
              2022-08-02 11:17:32.030 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x00158d0001de72f5 = 0
              2022-08-02 11:17:32.034 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x00158d0002f39894 = false
              2022-08-02 11:17:32.037 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x00158d0002f39894 = 0
              2022-08-02 11:17:32.040 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x00158d00033a4347 = false
              2022-08-02 11:17:32.045 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x00158d00033a4347 = 0
              2022-08-02 11:17:32.047 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x00158d0001ddab4c = false
              2022-08-02 11:17:32.050 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x00158d0001ddab4c = 0
              2022-08-02 11:17:32.054 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x00158d0004fd0fd7 = false
              2022-08-02 11:17:32.059 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x00158d0004fd0fd7 = 0
              2022-08-02 11:17:32.063 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x00158d00048605a0 = false
              2022-08-02 11:17:32.068 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x00158d00048605a0 = 0
              2022-08-02 11:17:32.073 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x842e14fffe1262bf = false
              2022-08-02 11:17:32.077 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x842e14fffe1262bf = 0
              2022-08-02 11:17:32.080 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x588e81fffedbcfe2 = false
              2022-08-02 11:17:32.090 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x588e81fffedbcfe2 = 0
              2022-08-02 11:17:32.098 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x842e14fffe35a210 = false
              2022-08-02 11:17:32.100 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x842e14fffe35a210 = 0
              2022-08-02 11:17:32.103 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x00158d000485f414 = false
              2022-08-02 11:17:32.107 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x00158d000485f414 = 0
              2022-08-02 11:17:32.114 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x00158d000482d34e = false
              2022-08-02 11:17:32.132 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x00158d000482d34e = 0
              2022-08-02 11:17:32.166 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x00158d0001e7a0d0 = false
              2022-08-02 11:17:32.170 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x00158d0001e7a0d0 = 0
              2022-08-02 11:17:32.177 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x04cd15fffe067cd7 = false
              2022-08-02 11:17:32.193 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x04cd15fffe067cd7 = 0
              2022-08-02 11:17:32.196 - debug: zigbee.0 (518638) DeviceAvailability:Publish available for 0x04cd15fffe02dd9b = false
              2022-08-02 11:17:32.207 - debug: zigbee.0 (518638) DeviceAvailability:Publish LQ for 0x04cd15fffe02dd9b = 0
              2022-08-02 11:17:32.269 - info: zigbee.0 (518638) Zigbee: disabling joining new devices.
              2022-08-02 11:17:32.326 - warn: zigbee.0 (518638) Failed to stop zigbee during startup
              2022-08-02 11:17:32.327 - info: zigbee.0 (518638) terminating
              2022-08-02 11:17:32.328 - debug: zigbee.0 (518638) Plugin sentry destroyed
              2022-08-02 11:17:32.329 - info: zigbee.0 (518638) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
              2022-08-02 11:17:32.459 - info: host.smarthome stopInstance system.adapter.zigbee.0 send kill signal
              
              Asgothian 1 Reply Last reply Reply Quote 0
              • Asgothian
                Asgothian Developer @martinschm last edited by

                @martinschm Leider fehlt mal wieder das wonach ich gefragt hab. Um 11.13 wurde der Adapter neu gestartet. Ich wollte die 4 bis 5 Minuten davor sehen. Du hast aber nur ab 11.12 gepostet. Was ist davor ?

                A.

                M 2 Replies Last reply Reply Quote 0
                • M
                  martinschm @Asgothian last edited by

                  @asgothian said in ZigBee Adapter/TI Board steigt immer wieder mal aus:

                  @martinschm Leider fehlt mal wieder das wonach ich gefragt hab. Um 11.13 wurde der Adapter neu gestartet. Ich wollte die 4 bis 5 Minuten davor sehen. Du hast aber nur ab 11.12 gepostet. Was ist davor ?

                  A.

                  Hi,

                  ich hab alles gepostet was den zigbee Adapter betrifft. In den Logs findet sich davor nichts. Da sind nur Meldungen von iQontrol, web-speedy und sma-speedwire

                  Viele Grüße
                  Martin

                  Homoran 1 Reply Last reply Reply Quote 0
                  • Homoran
                    Homoran Global Moderator Administrators @martinschm last edited by

                    @martinschm sagte in ZigBee Adapter/TI Board steigt immer wieder mal aus:

                    In den Logs findet sich davor nichts. Da sind nur Meldungen von iQontrol, web-speedy und sma-speedwire

                    auch nichts vom host?

                    M 1 Reply Last reply Reply Quote 0
                    • M
                      martinschm @Homoran last edited by

                      @homoran said in ZigBee Adapter/TI Board steigt immer wieder mal aus:

                      @martinschm sagte in ZigBee Adapter/TI Board steigt immer wieder mal aus:

                      In den Logs findet sich davor nichts. Da sind nur Meldungen von iQontrol, web-speedy und sma-speedwire

                      auch nichts vom host?

                      Auch nicht vom host.

                      Das ist alles von Mitternacht bis zu den Logs die ich oben gepostet habe.
                      iobroker log.txt

                      1 Reply Last reply Reply Quote 0
                      • M
                        martinschm @Asgothian last edited by

                        @asgothian said in ZigBee Adapter/TI Board steigt immer wieder mal aus:

                        @martinschm Leider fehlt mal wieder das wonach ich gefragt hab. Um 11.13 wurde der Adapter neu gestartet. Ich wollte die 4 bis 5 Minuten davor sehen. Du hast aber nur ab 11.12 gepostet. Was ist davor ?

                        A.

                        Ich habe gerade mal im proxmox meine raspberrymatic VM gestoppt, die greift auch per USB auf das HM Funkmodul zu. Vor dem Stoppen ließ sich zigbee nicht Verbinden mit der Fehlermeldung von oben, nach dem Stoppen ging es sofort.

                        Vielleicht wird raspberrymatic da "übergriffig" und sperrt den anderen USB Port?

                        arteck Asgothian 2 Replies Last reply Reply Quote 0
                        • arteck
                          arteck Developer Most Active @martinschm last edited by

                          @martinschm ich vermute eher das proxmox den Port nicht freigegeben hat nachdem es sich die VM den gekrallt hat..

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

                            @arteck said in ZigBee Adapter/TI Board steigt immer wieder mal aus:

                            @martinschm ich vermute eher das proxmox den Port nicht freigegeben hat nachdem es sich die VM den gekrallt hat..

                            Kann sein. Komisch ist nur, das im laufenden Betrieb auf einen anderen USB Port zu gegriffen wird.

                            Die iobroker VM hat den einen Port mit dem Zigbee Board dran und die Raspberrymativ VM den anderen Port.

                            Ist wohl wie bei meinen Kids, die VMs wollen immer den Usb Port den sie gerade nicht haben 🙂

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

                              @martinschm sagte in ZigBee Adapter/TI Board steigt immer wieder mal aus:

                              Ich habe gerade mal im proxmox meine raspberrymatic VM gestoppt, die greift auch per USB auf das HM Funkmodul zu. Vor dem Stoppen ließ sich zigbee nicht Verbinden mit der Fehlermeldung von oben, nach dem Stoppen ging es sofort.
                              Vielleicht wird raspberrymatic da "übergriffig" und sperrt den anderen USB Port?

                              Bei den VM bin ich raus. Ich trau dem Braten nicht und nutze das nicht.

                              A.

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

                              Support us

                              ioBroker
                              Community Adapters
                              Donate

                              657
                              Online

                              31.8k
                              Users

                              80.0k
                              Topics

                              1.3m
                              Posts

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