Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Error/Bug
    4. Unerklärliche ZigBee Abstürze

    NEWS

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    UNSOLVED Unerklärliche ZigBee Abstürze

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

      Systemdata Bitte Ausfüllen
      Hardwaresystem: Raspberry Pi 4.
      Arbeitsspeicher:

      /proc/meminfo
      MemTotal: 1911988 kB
      MemFree: 1200444 kB
      MemAvailable: 1423992 kB

      |Festplattenart:| SD-Karte
      df
      Filesystem 1K-blocks Used Available Use% Mounted on
      /dev/root 30481844 4043088 25168128 14% /
      devtmpfs 823896 0 823896 0% /dev
      tmpfs 955992 0 955992 0% /dev/shm
      tmpfs 955992 8648 947344 1% /run
      tmpfs 5120 4 5116 1% /run/lock
      tmpfs 955992 0 955992 0% /sys/fs/cgroup
      /dev/mmcblk0p1 258095 55053 203043 22% /boot
      tmpfs 191196 0 191196 0% /run/user/0

      |Betriebssystem:| Raspberry minimal / light|
      |Node-Version:| frisch aufgesetzt - alles up to date (5 tage alt)|
      |Nodejs-Version:| -,,- |
      |NPM-Version:| -,,- |
      |Installationsart:| Skript|
      |Image genutzt:| Nein |

      Ich habe zwei ioBroker auf Raspberry Basis
      Der alte ist zum Master hochgestuft, der neue - der die Probleme macht - ist als Slave gejoined und dann konfiguriert worden.

      Beide wurden wie in der Anleitung vorher auf letztstand gepatcht und dann joined.

      Ich habe auf beiden einen CC2531 als Zigbee Adapter mit ettlichen Geräten.
      Der einzige Unterschied, am neuen gibt es am CC2531 eine Antenne und es gibt ein Gerät, welches ich in den Devices selbst hinzugefügt habe.
      Um Gleichheit zu haben, ist der Ausschnitt in den Devices.js aber auf beiden Geräten derselbe.

      Ich bekomme nun ca 1x am Tag folgenden Log, der dann dazu führt, dass ich den Adapter weder durch neustarten oder manuell stop start wieder ins laufen bekomme.
      ich muss den raspberry dafür komplett durchstarten, damit es wieder klappt (iobroker restart hilft also auch nicht)

      interessant finde ich, dass vorher auch der Fritzbox adapter Probleme macht?
      Den gab es vorher auf dem Master, wegen der Auslastung am Master, habe ich den allerdings nun auf den Slave verschoben / neu konfiguriert.

      zigbee.1	2020-12-29 17:46:40.857	info	(8043) cleaned everything up...
      zigbee.1	2020-12-29 17:42:06.719	error	at binding.open.then.err (/opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/stream/lib/index.js:242:12)
      zigbee.1	2020-12-29 17:42:06.719	error	at SerialPort._error (/opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/stream/lib/index.js:198:14)
      zigbee.1	2020-12-29 17:42:06.719	error	at SerialPort.serialPort.open (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:134:49)
      zigbee.1	2020-12-29 17:42:06.719	error	at __awaiter (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:23:12)
      zigbee.1	2020-12-29 17:42:06.719	error	at new Promise (<anonymous>)
      zigbee.1	2020-12-29 17:42:06.719	error	at /opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:27:71
      zigbee.1	2020-12-29 17:42:06.719	error	at Generator.next (<anonymous>)
      zigbee.1	2020-12-29 17:42:06.719	error	at Znp.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:136:32)
      zigbee.1	2020-12-29 17:42:06.719	error	(8043) Error: Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'
      zigbee.1	2020-12-29 17:42:06.718	error	(8043) Failed to start Zigbee
      zigbee.1	2020-12-29 17:42:06.489	info	(8043) Starting Zigbee npm ...
      zigbee.1	2020-12-29 17:42:06.488	info	(8043) Try to reconnect. 1 attempts left
      zigbee.1	2020-12-29 17:41:56.486	error	at rejected (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:25:65)
      zigbee.1	2020-12-29 17:41:56.486	error	at Generator.throw (<anonymous>)
      zigbee.1	2020-12-29 17:41:56.486	error	at ZStackAdapter.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:94:31)
      zigbee.1	2020-12-29 17:41:56.486	error	(8043) Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
      zigbee.1	2020-12-29 17:41:56.485	error	(8043) Failed to start Zigbee
      zigbee.1	2020-12-29 17:41:36.622	info	(8043) Starting Zigbee npm ...
      zigbee.1	2020-12-29 17:41:36.497	info	(8043) starting. Version 1.3.1 in /opt/iobroker/node_modules/iobroker.zigbee, node: v10.23.0, js-controller: 3.1.6
      host.iobroker86	2020-12-29 17:41:32.250	info	instance system.adapter.zigbee.1 started with pid 8043
      tr-064.1	2020-12-29 17:41:08.519	info	(8028) starting. Version 4.2.1 in /opt/iobroker/node_modules/iobroker.tr-064, node: v10.23.0, js-controller: 3.1.6
      tr-064.1	2020-12-29 17:41:07.370	warn	(8028) slow connection to states DB. Still waiting ...
      host.iobroker86	2020-12-29 17:41:02.479	info	instance system.adapter.tr-064.1 started with pid 8028
      host.iobroker86	2020-12-29 17:38:53.355	info	Do not restart adapter system.adapter.zigbee.1 because desired by instance
      host.iobroker86	2020-12-29 17:38:53.353	error	instance system.adapter.zigbee.1 terminated by request of the instance itself and will not be restarted, before user restarts it.
      zigbee.1	2020-12-29 17:38:52.143	error	at stop (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:8270:22)
      zigbee.1	2020-12-29 17:38:52.143	error	at Zigbee.emit (events.js:198:13)
      zigbee.1	2020-12-29 17:38:52.143	error	at Zigbee.onUnload (/opt/iobroker/node_modules/iobroker.zigbee/main.js:450:41)
      zigbee.1	2020-12-29 17:38:52.143	error	at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:304:20)
      zigbee.1	2020-12-29 17:38:52.143	error	at ZigbeeController.callExtensionMethod (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:187:42)
      zigbee.1	2020-12-29 17:38:52.143	error	at DeviceAvailability.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zbDeviceAvailability.js:120:43)
      zigbee.1	2020-12-29 17:38:52.143	error	at ZigbeeController.getClients (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:201:49)
      zigbee.1	2020-12-29 17:38:52.143	error	at Controller.getDevices (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:252:31)
      zigbee.1	2020-12-29 17:38:52.143	error	at Function.all (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/device.js:236:16)
      zigbee.1	2020-12-29 17:38:52.143	error	at Function.loadFromDatabaseIfNecessary (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/device.js:216:55)
      zigbee.1	2020-12-29 17:38:52.143	error	(7926) TypeError: Cannot read property 'getEntries' of null
      zigbee.1	2020-12-29 17:38:52.140	error	(7926) unhandled promise rejection: Cannot read property 'getEntries' of null
      Unhandled	2020-12-29 17:38:52.140	error	promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
      zigbee.1	2020-12-29 17:38:52.138	info	(7926) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
      zigbee.1	2020-12-29 17:38:52.137	info	(7926) terminating
      zigbee.1	2020-12-29 17:38:52.137	error	at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:308:33))
      zigbee.1	2020-12-29 17:38:52.137	error	at Controller.stop (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:199:16)
      zigbee.1	2020-12-29 17:38:52.137	error	at __awaiter (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:23:12)
      zigbee.1	2020-12-29 17:38:52.137	error	at new Promise (<anonymous>)
      zigbee.1	2020-12-29 17:38:52.137	error	at /opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:27:71
      zigbee.1	2020-12-29 17:38:52.137	error	at Generator.next (<anonymous>)
      zigbee.1	2020-12-29 17:38:52.137	error	at Controller.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:200:18)
      zigbee.1	2020-12-29 17:38:52.137	error	at Controller.databaseSave (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:219:45)
      zigbee.1	2020-12-29 17:38:52.137	error	at Function.all (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/group.js:88:15)
      zigbee.1	2020-12-29 17:38:52.137	error	at Function.loadFromDatabaseIfNecessary (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/group.js:76:55)
      zigbee.1	2020-12-29 17:38:52.137	error	(7926) Failed to stop zigbee (TypeError: Cannot read property 'getEntries' of null
      zigbee.1	2020-12-29 17:38:52.134	info	(7926) Zigbee: disabling joining new devices.
      zigbee.1	2020-12-29 17:38:52.129	info	(7926) cleaned everything up...
      zigbee.1	2020-12-29 17:38:52.127	warn	(7926) Got terminate signal. Checking desired PID: 0 vs own PID 7926
      host.iobroker86	2020-12-29 17:38:47.041	info	Restart adapter system.adapter.zigbee.1 because enabled
      host.iobroker86	2020-12-29 17:38:47.039	error	instance system.adapter.zigbee.1 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
      zigbee.1	2020-12-29 17:38:45.160	warn	(8010) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
      zigbee.1	2020-12-29 17:38:45.157	error	(8010) zigbee.1 already running
      host.iobroker86	2020-12-29 17:38:43.121	info	instance system.adapter.zigbee.1 started with pid 8010
      host.iobroker86	2020-12-29 17:38:42.105	info	Do not restart adapter system.adapter.tr-064.1 because desired by instance
      host.iobroker86	2020-12-29 17:38:42.104	error	instance system.adapter.tr-064.1 terminated by request of the instance itself and will not be restarted, before user restarts it.
      host.iobroker86	2020-12-29 17:38:40.145	info	Restart adapter system.adapter.tr-064.1 because enabled
      host.iobroker86	2020-12-29 17:38:40.144	error	instance system.adapter.tr-064.1 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
      tr-064.1	2020-12-29 17:38:39.695	info	(7911) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
      

      die Änderung in den Devices.js war übrigens das hinzufügen von

      {
          models: ['HGZB-04D / HGZB-4D-UK'],
          icon: 'img/iluminize_511_040.png', 
          states: lightStates,
      },
      

      werde nicht wirklich schlau daraus, irgendwelche ideen woran das liegen kann?

      hatte in all den Jahren noch nie solche Probleme

      Thomas Braun mickym 3 Replies Last reply Reply Quote 0
      • Thomas Braun
        Thomas Braun Most Active @Highpressure last edited by

        @Highpressure
        Ich hätte ja im Vorfeld die node-Version beider Systeme auf node12 gehoben.

        Hast du es mal mit zigbee 1.4.0 probiert? Die Developer waren da ziemlich fleißig in den letzten Wochen.

        1 Reply Last reply Reply Quote 0
        • mickym
          mickym Most Active @Highpressure last edited by mickym

          @Highpressure Bei mir hat nach 1 Jahr ein CC2531 den Geist aufgegeben - ich denke mal, dass es ein thermisches Problem war. Ich habe dann einen neuen Stick gekauft und hatte den an einem USB Hub angeschlossen und bekam auch permanent (1-2 mal am Tag das Problem). Dachte es läge am Adapter - war aber auch Hardware. Nachdem ich den Stick wieder an den Raspberry gesteckt habe, geht der neue jetzt. Statt einem kompletten Restart - hilft auch manchmal Stick abziehen und Adapter starten.
          In Summe denke ich aber, dass nach meinen Erfahrungen ein HW Problem vorliegt oder sich ankündigt.

          Wenn der Adapter mit dem seriellen Port nicht kommunizieren kann - ist es meiner Erfahrung nicht mehr zielführend an der Konfig zu drehen. Du kannst noch einen anderen USB Port probieren.

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

            @Highpressure
            Wenn da die Hardware mucken sollte, könnte es auch entsprechende Einträge in

            dmesg
            

            geben.

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

              @Thomas-Braun sagte in Unerklärliche ZigBee Abstürze:

              @Highpressure
              Wenn da die Hardware mucken sollte, könnte es auch entsprechende Einträge in

              dmesg
              

              geben.

              Diese Aussage kann ich für den Zigbee Stick so nicht bestätigen. Wenn da die Hardware nicht geht dann ist oft die Firmware betroffen, die erst angesprochen wird wenn versucht wird per serieller Kommunikation auf den Stick zuzugreifen. Das wird in dmesg nicht auftauchen.

              A

              H 1 Reply Last reply Reply Quote 0
              • H
                Highpressure @Asgothian last edited by

                das einzige in dmesg was auffällig ist, aber auch nur vom boot war zu brcmfmac

                
                [    4.504768] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
                [    4.504781] [drm] No driver support for vblank timestamp query.
                [    4.504794] [drm] Setting vblank_disable_immediate to false because get_vblank_timestamp == NULL
                [    4.505226] [drm] Initialized vc4 0.0.0 20140616 for gpu on minor 1
                [    4.518008] brcmfmac: F1 signature read @0x18000000=0x15264345
                [    4.529864] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
                [    4.530296] usbcore: registered new interface driver brcmfmac
                [    4.558432] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt failed with error -2
                [    4.605436] cdc_acm 1-1.4:1.0: ttyACM0: USB ACM device
                [    4.608192] usbcore: registered new interface driver cdc_acm
                [    4.608206] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
                [    4.802263] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
                [    4.812906] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Mar 23 2020 02:19:54 version 7.45.206 (r725000 CY) FWID 01-88ee44ea
                [    6.193838] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
                [    6.652176] random: crng init done
                [    6.652194] random: 7 urandom warning(s) missed due to ratelimiting
                
                

                das seltsame ist ja auch dass ich es nicht nachstellen kann, oder forcieren.
                Es passiert halt irgendwann. hab schon alternativ überlegt ein reboot script zu machen, als dirty workaround lol..
                aber eigentlich will ich es ja gefixed haben

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

                  @Highpressure
                  Zeig mal die komplette Ausgabe.

                  H 1 Reply Last reply Reply Quote 0
                  • H
                    Highpressure @mickym last edited by

                    @mickym

                    der raspberry als auch der stick sind komplett neu.
                    wäre in dem fall gleich mal dead on delivery 😞

                    aber gute idee, ich werde noch einen anderen port probieren.

                    eigentlich sollten die sticks unter dem selben port wieder auftauchen, wenn ich die zwischen den rapsberrys mal austausche, oder?
                    also stick von raspbi#1 abziehen und mit stick von raspbi#2 tauschen?

                    so könnte ich kreuztesten ob es am stick oder der config des raspberry/iobroker liegt

                    mickym 1 Reply Last reply Reply Quote 0
                    • H
                      Highpressure @Thomas Braun last edited by

                      @Thomas-Braun

                      findest du hier 🙂
                      https://pastebin.com/QPgivnVw

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

                        @Highpressure Komm ich nicht drauf.

                        H 1 Reply Last reply Reply Quote 0
                        • mickym
                          mickym Most Active @Highpressure last edited by

                          @Highpressure sagte in Unerklärliche ZigBee Abstürze:

                          @mickym

                          der raspberry als auch der stick sind komplett neu.
                          wäre in dem fall gleich mal dead on delivery 😞

                          aber gute idee, ich werde noch einen anderen port probieren.

                          eigentlich sollten die sticks unter dem selben port wieder auftauchen, wenn ich die zwischen den rapsberrys mal austausche, oder?
                          also stick von raspbi#1 abziehen und mit stick von raspbi#2 tauschen?

                          so könnte ich kreuztesten ob es am stick oder der config des raspberry/iobroker liegt

                          Ja am Port sollte sich gar nichts ändern.

                          1 Reply Last reply Reply Quote 0
                          • H
                            Highpressure @Thomas Braun last edited by

                            @Thomas-Braun

                            komisch, hatte ich öffentlich und anonym geposted.
                            egal, dann halt so:

                            [    0.000000] Booting Linux on physical CPU 0x0
                            [    0.000000] Linux version 5.4.79-v7l+ (dom@buildbot) (gcc version 8.4.0 (Ubuntu/Linaro 8.4.0-3ubuntu1)) #1373 SMP Mon Nov 23 13:27:40 GMT 2020
                            [    0.000000] CPU: ARMv7 Processor [410fd083] revision 3 (ARMv7), cr=30c5383d
                            [    0.000000] CPU: div instructions available: patching division code
                            [    0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
                            [    0.000000] OF: fdt: Machine model: Raspberry Pi 4 Model B Rev 1.2
                            [    0.000000] Memory policy: Data cache writealloc
                            [    0.000000] Reserved memory: created CMA memory pool at 0x000000001ec00000, size 256 MiB
                            [    0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool
                            [    0.000000] On node 0 totalpages: 504832
                            [    0.000000]   DMA zone: 2304 pages used for memmap
                            [    0.000000]   DMA zone: 0 pages reserved
                            [    0.000000]   DMA zone: 196608 pages, LIFO batch:63
                            [    0.000000]   HighMem zone: 308224 pages, LIFO batch:63
                            [    0.000000] percpu: Embedded 20 pages/cpu s49804 r8192 d23924 u81920
                            [    0.000000] pcpu-alloc: s49804 r8192 d23924 u81920 alloc=20*4096
                            [    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
                            [    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 502528
                            [    0.000000] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1  smsc95xx.macaddr=DC:A6:32:CA:D4:23 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000  console=ttyS0,115200 console=tty1 root=PARTUUID=9cf86426-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait
                            [    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes, linear)
                            [    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes, linear)
                            [    0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
                            [    0.000000] software IO TLB: mapped [mem 0x19400000-0x1d400000] (64MB)
                            [    0.000000] Memory: 1647796K/2019328K available (10240K kernel code, 739K rwdata, 2816K rodata, 2048K init, 854K bss, 109388K reserved, 262144K cma-reserved, 1232896K highmem)
                            [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
                            [    0.000000] ftrace: allocating 31111 entries in 61 pages
                            [    0.000000] rcu: Hierarchical RCU implementation.
                            [    0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
                            [    0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
                            [    0.000000] GIC: Using split EOI/Deactivate mode
                            [    0.000000] random: get_random_bytes called from start_kernel+0x344/0x518 with crng_init=0
                            [    0.000007] sched_clock: 32 bits at 1000kHz, resolution 1000ns, wraps every 2147483647500ns
                            [    0.000030] clocksource: timer: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1911260446275 ns
                            [    0.000109] bcm2835: system timer (irq = 17)
                            [    0.000756] arch_timer: cp15 timer(s) running at 54.00MHz (phys).
                            [    0.000776] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0xc743ce346, max_idle_ns: 440795203123 ns
                            [    0.000796] sched_clock: 56 bits at 54MHz, resolution 18ns, wraps every 4398046511102ns
                            [    0.000812] Switching to timer-based delay loop, resolution 18ns
                            [    0.001052] Console: colour dummy device 80x30
                            [    0.001550] printk: console [tty1] enabled
                            [    0.001614] Calibrating delay loop (skipped), value calculated using timer frequency.. 108.00 BogoMIPS (lpj=540000)
                            [    0.001657] pid_max: default: 32768 minimum: 301
                            [    0.001819] LSM: Security Framework initializing
                            [    0.002024] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes, linear)
                            [    0.002067] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes, linear)
                            [    0.003432] Disabling memory control group subsystem
                            [    0.003569] CPU: Testing write buffer coherency: ok
                            [    0.004085] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
                            [    0.005010] Setting up static identity map for 0x200000 - 0x20003c
                            [    0.005235] rcu: Hierarchical SRCU implementation.
                            [    0.005934] smp: Bringing up secondary CPUs ...
                            [    0.007137] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
                            [    0.008458] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
                            [    0.009722] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
                            [    0.009879] smp: Brought up 1 node, 4 CPUs
                            [    0.009950] SMP: Total of 4 processors activated (432.00 BogoMIPS).
                            [    0.009977] CPU: All CPU(s) started in HYP mode.
                            [    0.010002] CPU: Virtualization extensions available.
                            [    0.010836] devtmpfs: initialized
                            [    0.024404] VFP support v0.3: implementor 41 architecture 3 part 40 variant 8 rev 0
                            [    0.024684] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
                            [    0.024736] futex hash table entries: 1024 (order: 4, 65536 bytes, linear)
                            [    0.031549] pinctrl core: initialized pinctrl subsystem
                            [    0.032569] NET: Registered protocol family 16
                            [    0.036393] DMA: preallocated 1024 KiB pool for atomic coherent allocations
                            [    0.036980] audit: initializing netlink subsys (disabled)
                            [    0.037243] audit: type=2000 audit(0.030:1): state=initialized audit_enabled=0 res=1
                            [    0.038312] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
                            [    0.038349] hw-breakpoint: maximum watchpoint size is 8 bytes.
                            [    0.038681] Serial: AMBA PL011 UART driver
                            [    0.042206] bcm2835-mbox fe00b880.mailbox: mailbox enabled
                            [    0.060830] raspberrypi-firmware soc:firmware: Attached to firmware from 2020-11-30 22:12, variant start
                            [    0.070846] raspberrypi-firmware soc:firmware: Firmware hash is ab1181cc0cb6df52bfae3b1d3fef0ce7c325166c
                            [    0.126218] bcm2835-dma fe007000.dma: DMA legacy API manager, dmachans=0x1
                            [    0.131353] vgaarb: loaded
                            [    0.131836] SCSI subsystem initialized
                            [    0.132076] usbcore: registered new interface driver usbfs
                            [    0.132148] usbcore: registered new interface driver hub
                            [    0.132296] usbcore: registered new device driver usb
                            [    0.132645] usb_phy_generic phy: phy supply vcc not found, using dummy regulator
                            [    0.134436] clocksource: Switched to clocksource arch_sys_counter
                            [    0.894638] VFS: Disk quotas dquot_6.6.0
                            [    0.894763] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
                            [    0.894944] FS-Cache: Loaded
                            [    0.895163] CacheFiles: Loaded
                            [    0.905786] thermal_sys: Registered thermal governor 'step_wise'
                            [    0.906152] NET: Registered protocol family 2
                            [    0.906911] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes, linear)
                            [    0.906964] TCP established hash table entries: 8192 (order: 3, 32768 bytes, linear)
                            [    0.907041] TCP bind hash table entries: 8192 (order: 4, 65536 bytes, linear)
                            [    0.907123] TCP: Hash tables configured (established 8192 bind 8192)
                            [    0.907286] UDP hash table entries: 512 (order: 2, 16384 bytes, linear)
                            [    0.907337] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes, linear)
                            [    0.907611] NET: Registered protocol family 1
                            [    0.908354] RPC: Registered named UNIX socket transport module.
                            [    0.908384] RPC: Registered udp transport module.
                            [    0.908410] RPC: Registered tcp transport module.
                            [    0.908435] RPC: Registered tcp NFSv4.1 backchannel transport module.
                            [    0.908470] PCI: CLS 0 bytes, default 64
                            [    0.910322] hw perfevents: enabled with armv7_cortex_a15 PMU driver, 7 counters available
                            [    0.912559] Initialise system trusted keyrings
                            [    0.912805] workingset: timestamp_bits=14 max_order=19 bucket_order=5
                            [    0.923739] FS-Cache: Netfs 'nfs' registered for caching
                            [    0.924519] NFS: Registering the id_resolver key type
                            [    0.924567] Key type id_resolver registered
                            [    0.924593] Key type id_legacy registered
                            [    0.924628] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
                            [    0.925748] Key type asymmetric registered
                            [    0.925777] Asymmetric key parser 'x509' registered
                            [    0.925983] bounce: pool size: 64 pages
                            [    0.926037] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249)
                            [    0.926294] io scheduler mq-deadline registered
                            [    0.926323] io scheduler kyber registered
                            [    0.930296] brcm-pcie fd500000.pcie: host bridge /scb/pcie@7d500000 ranges:
                            [    0.930338] brcm-pcie fd500000.pcie:   No bus range found for /scb/pcie@7d500000, using [bus 00-ff]
                            [    0.930444] brcm-pcie fd500000.pcie:      MEM 0x0600000000..0x0603ffffff -> 0x00f8000000
                            [    0.930534] brcm-pcie fd500000.pcie:   IB MEM 0x0000000000..0x007fffffff -> 0x0000000000
                            [    0.986586] brcm-pcie fd500000.pcie: link up, 5 GT/s x1 (SSC)
                            [    0.986924] brcm-pcie fd500000.pcie: PCI host bridge to bus 0000:00
                            [    0.986959] pci_bus 0000:00: root bus resource [bus 00-ff]
                            [    0.986993] pci_bus 0000:00: root bus resource [mem 0x600000000-0x603ffffff] (bus address [0xf8000000-0xfbffffff])
                            [    0.987071] pci 0000:00:00.0: [14e4:2711] type 01 class 0x060400
                            [    0.987358] pci 0000:00:00.0: PME# supported from D0 D3hot
                            [    0.990654] PCI: bus0: Fast back to back transfers disabled
                            [    0.990900] pci 0000:01:00.0: [1106:3483] type 00 class 0x0c0330
                            [    0.991062] pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x00000fff 64bit]
                            [    0.991510] pci 0000:01:00.0: PME# supported from D0 D3cold
                            [    0.994839] PCI: bus1: Fast back to back transfers disabled
                            [    0.994913] pci 0000:00:00.0: BAR 8: assigned [mem 0x600000000-0x6000fffff]
                            [    0.994952] pci 0000:01:00.0: BAR 0: assigned [mem 0x600000000-0x600000fff 64bit]
                            [    0.995052] pci 0000:00:00.0: PCI bridge to [bus 01]
                            [    0.995090] pci 0000:00:00.0:   bridge window [mem 0x600000000-0x6000fffff]
                            [    0.995418] pcieport 0000:00:00.0: enabling device (0140 -> 0142)
                            [    0.995677] pcieport 0000:00:00.0: PME: Signaling with IRQ 55
                            [    0.996096] pcieport 0000:00:00.0: AER: enabled with IRQ 55
                            [    0.996455] pci 0000:01:00.0: enabling device (0140 -> 0142)
                            [    1.003422] iproc-rng200 fe104000.rng: hwrng registered
                            [    1.003774] vc-mem: phys_addr:0x00000000 mem_base=0x3ec00000 mem_size:0x40000000(1024 MiB)
                            [    1.004509] vc-sm: Videocore shared memory driver
                            [    1.005120] gpiomem-bcm2835 fe200000.gpiomem: Initialised: Registers at 0xfe200000
                            [    1.017368] brd: module loaded
                            [    1.029868] loop: module loaded
                            [    1.031306] Loading iSCSI transport class v2.0-870.
                            [    1.033343] libphy: Fixed MDIO Bus: probed
                            [    1.033981] bcmgenet fd580000.ethernet: failed to get enet clock
                            [    1.034017] bcmgenet fd580000.ethernet: GENET 5.0 EPHY: 0x0000
                            [    1.034054] bcmgenet fd580000.ethernet: failed to get enet-wol clock
                            [    1.034090] bcmgenet fd580000.ethernet: failed to get enet-eee clock
                            [    1.034132] bcmgenet: Skipping UMAC reset
                            [    1.054518] libphy: bcmgenet MII bus: probed
                            [    1.144627] unimac-mdio unimac-mdio.-19: Broadcom UniMAC MDIO bus
                            [    1.145774] usbcore: registered new interface driver r8152
                            [    1.145856] usbcore: registered new interface driver lan78xx
                            [    1.145932] usbcore: registered new interface driver smsc95xx
                            [    1.146440] xhci_hcd 0000:01:00.0: xHCI Host Controller
                            [    1.146489] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 1
                            [    1.148911] xhci_hcd 0000:01:00.0: hcc params 0x002841eb hci version 0x100 quirks 0x0000003000000890
                            [    1.150245] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.04
                            [    1.150284] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
                            [    1.150318] usb usb1: Product: xHCI Host Controller
                            [    1.150346] usb usb1: Manufacturer: Linux 5.4.79-v7l+ xhci-hcd
                            [    1.150375] usb usb1: SerialNumber: 0000:01:00.0
                            [    1.151001] hub 1-0:1.0: USB hub found
                            [    1.151111] hub 1-0:1.0: 1 port detected
                            [    1.151686] xhci_hcd 0000:01:00.0: xHCI Host Controller
                            [    1.151727] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 2
                            [    1.151770] xhci_hcd 0000:01:00.0: Host supports USB 3.0 SuperSpeed
                            [    1.152269] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.04
                            [    1.152305] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
                            [    1.152339] usb usb2: Product: xHCI Host Controller
                            [    1.152367] usb usb2: Manufacturer: Linux 5.4.79-v7l+ xhci-hcd
                            [    1.152395] usb usb2: SerialNumber: 0000:01:00.0
                            [    1.153020] hub 2-0:1.0: USB hub found
                            [    1.153119] hub 2-0:1.0: 4 ports detected
                            [    1.154642] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
                            [    1.154949] dwc_otg: FIQ enabled
                            [    1.154962] dwc_otg: NAK holdoff enabled
                            [    1.154974] dwc_otg: FIQ split-transaction FSM enabled
                            [    1.155002] Module dwc_common_port init
                            [    1.155466] usbcore: registered new interface driver uas
                            [    1.155588] usbcore: registered new interface driver usb-storage
                            [    1.155802] mousedev: PS/2 mouse device common for all mice
                            [    1.157675] bcm2835-wdt bcm2835-wdt: Broadcom BCM2835 watchdog timer
                            [    1.161072] sdhci: Secure Digital Host Controller Interface driver
                            [    1.161102] sdhci: Copyright(c) Pierre Ossman
                            [    1.161748] mmc-bcm2835 fe300000.mmcnr: could not get clk, deferring probe
                            [    1.162359] sdhci-pltfm: SDHCI platform and OF driver helper
                            [    1.166248] ledtrig-cpu: registered to indicate activity on CPUs
                            [    1.166577] hidraw: raw HID events driver (C) Jiri Kosina
                            [    1.166776] usbcore: registered new interface driver usbhid
                            [    1.166803] usbhid: USB HID core driver
                            [    1.167853] vchiq: vchiq_init_state: slot_zero = (ptrval)
                            [    1.169791] [vc_sm_connected_init]: start
                            [    1.178713] [vc_sm_connected_init]: end - returning 0
                            [    1.180976] Initializing XFRM netlink socket
                            [    1.181030] NET: Registered protocol family 17
                            [    1.181180] Key type dns_resolver registered
                            [    1.181536] Registering SWP/SWPB emulation handler
                            [    1.181874] registered taskstats version 1
                            [    1.181908] Loading compiled-in X.509 certificates
                            [    1.182464] Key type ._fscrypt registered
                            [    1.182492] Key type .fscrypt registered
                            [    1.193180] uart-pl011 fe201000.serial: cts_event_workaround enabled
                            [    1.193274] fe201000.serial: ttyAMA0 at MMIO 0xfe201000 (irq = 29, base_baud = 0) is a PL011 rev2
                            [    1.199434] bcm2835-power bcm2835-power: Broadcom BCM2835 power domains driver
                            [    1.200425] mmc-bcm2835 fe300000.mmcnr: mmc_debug:0 mmc_debug2:0
                            [    1.200457] mmc-bcm2835 fe300000.mmcnr: DMA channel allocated
                            [    1.248001] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
                            [    1.249690] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
                            [    1.251436] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
                            [    1.254471] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
                            [    1.256232] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
                            [    1.263973] mmc0: SDHCI controller on fe340000.emmc2 [fe340000.emmc2] using ADMA
                            [    1.266953] of_cfs_init
                            [    1.267086] of_cfs_init: OK
                            [    1.268146] Waiting for root device PARTUUID=9cf86426-02...
                            [    1.307074] random: fast init done
                            [    1.367524] mmc0: new ultra high speed DDR50 SDHC card at address 0001
                            [    1.370538] mmcblk0: mmc0:0001 EB1QT 29.8 GiB
                            [    1.373167] mmc1: new high speed SDIO card at address 0001
                            [    1.373956]  mmcblk0: p1 p2
                            [    1.394243] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
                            [    1.394340] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
                            [    1.399990] devtmpfs: mounted
                            [    1.408704] Freeing unused kernel memory: 2048K
                            [    1.424750] Run /sbin/init as init process
                            [    1.514504] usb 1-1: new high-speed USB device number 2 using xhci_hcd
                            [    1.697175] usb 1-1: New USB device found, idVendor=2109, idProduct=3431, bcdDevice= 4.21
                            [    1.697218] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
                            [    1.697250] usb 1-1: Product: USB2.0 Hub
                            [    1.699267] hub 1-1:1.0: USB hub found
                            [    1.699560] hub 1-1:1.0: 4 ports detected
                            [    1.852726] systemd[1]: System time before build time, advancing clock.
                            [    1.957936] NET: Registered protocol family 10
                            [    1.959291] Segment Routing with IPv6
                            [    1.981407] systemd[1]: systemd 241 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid)
                            [    1.982223] systemd[1]: Detected architecture arm.
                            [    2.024498] usb 1-1.4: new full-speed USB device number 3 using xhci_hcd
                            [    2.041641] systemd[1]: Set hostname to <iobroker86>.
                            [    2.163855] usb 1-1.4: New USB device found, idVendor=0451, idProduct=16a8, bcdDevice= 0.09
                            [    2.163904] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
                            [    2.163941] usb 1-1.4: Product: TI CC2531 USB CDC
                            [    2.163970] usb 1-1.4: Manufacturer: Texas Instruments
                            [    2.163999] usb 1-1.4: SerialNumber: __0X00124B0014D9E31C
                            [    2.728612] random: systemd: uninitialized urandom read (16 bytes read)
                            [    2.738623] random: systemd: uninitialized urandom read (16 bytes read)
                            [    2.739055] systemd[1]: Listening on initctl Compatibility Named Pipe.
                            [    2.740373] random: systemd: uninitialized urandom read (16 bytes read)
                            [    2.745415] systemd[1]: Listening on Journal Audit Socket.
                            [    2.746594] systemd[1]: Listening on udev Kernel Socket.
                            [    2.747451] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
                            [    2.748028] systemd[1]: Reached target Swap.
                            [    2.751577] systemd[1]: Created slice system-getty.slice.
                            [    2.752465] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
                            [    3.344995] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
                            [    3.460283] systemd-journald[116]: Received request to flush runtime journal from PID 1
                            [    3.957195] rpivid-mem feb00000.hevc-decoder: rpivid-hevcmem initialised: Registers at 0xfeb00000 length 0x00010000
                            [    3.957790] rpivid-mem feb10000.rpivid-local-intc: rpivid-intcmem initialised: Registers at 0xfeb10000 length 0x00001000
                            [    3.958234] rpivid-mem feb20000.h264-decoder: rpivid-h264mem initialised: Registers at 0xfeb20000 length 0x00010000
                            [    3.958682] rpivid-mem feb30000.vp9-decoder: rpivid-vp9mem initialised: Registers at 0xfeb30000 length 0x00010000
                            [    4.016500] vc_sm_cma: module is from the staging directory, the quality is unknown, you have been warned.
                            [    4.018715] bcm2835_vc_sm_cma_probe: Videocore shared memory driver
                            [    4.018737] [vc_sm_connected_init]: start
                            [    4.025636] [vc_sm_connected_init]: installed successfully
                            [    4.031827] mc: Linux media interface: v0.10
                            [    4.032366] snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned.
                            [    4.088255] videodev: Linux video capture interface: v2.00
                            [    4.089583] bcm2835_audio bcm2835_audio: card created with 8 channels
                            [    4.137133] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
                            [    4.137138] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
                            [    4.177380] bcm2835_v4l2: module is from the staging directory, the quality is unknown, you have been warned.
                            [    4.178090] bcm2835_isp: module is from the staging directory, the quality is unknown, you have been warned.
                            [    4.196437] bcm2835-isp bcm2835-isp: Device node output[0] registered as /dev/video13
                            [    4.197461] bcm2835-isp bcm2835-isp: Device node capture[0] registered as /dev/video14
                            [    4.198972] bcm2835-isp bcm2835-isp: Device node capture[1] registered as /dev/video15
                            [    4.200115] bcm2835-isp bcm2835-isp: Device node stats[2] registered as /dev/video16
                            [    4.200177] bcm2835-isp bcm2835-isp: Register output node 0 with media controller
                            [    4.200240] bcm2835-isp bcm2835-isp: Register capture node 1 with media controller
                            [    4.200297] bcm2835-isp bcm2835-isp: Register capture node 2 with media controller
                            [    4.200356] bcm2835-isp bcm2835-isp: Register capture node 3 with media controller
                            [    4.201111] bcm2835-isp bcm2835-isp: Loaded V4L2 bcm2835-isp
                            [    4.204070] bcm2835_codec: module is from the staging directory, the quality is unknown, you have been warned.
                            [    4.221759] bcm2835-codec bcm2835-codec: Device registered as /dev/video10
                            [    4.221805] bcm2835-codec bcm2835-codec: Loaded V4L2 decode
                            [    4.228248] bcm2835-codec bcm2835-codec: Device registered as /dev/video11
                            [    4.228290] bcm2835-codec bcm2835-codec: Loaded V4L2 encode
                            [    4.253249] bcm2835-codec bcm2835-codec: Device registered as /dev/video12
                            [    4.253291] bcm2835-codec bcm2835-codec: Loaded V4L2 isp
                            [    4.320178] cfg80211: Loading compiled-in X.509 certificates for regulatory database
                            [    4.383225] [drm] Initialized v3d 1.0.0 20180419 for fec00000.v3d on minor 0
                            [    4.464784] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
                            [    4.504628] [drm] No displays found. Consider forcing hotplug if HDMI is attached
                            [    4.504745] vc4-drm gpu: bound fe600000.firmwarekms (ops vc4_fkms_ops [vc4])
                            [    4.504768] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
                            [    4.504781] [drm] No driver support for vblank timestamp query.
                            [    4.504794] [drm] Setting vblank_disable_immediate to false because get_vblank_timestamp == NULL
                            [    4.505226] [drm] Initialized vc4 0.0.0 20140616 for gpu on minor 1
                            [    4.518008] brcmfmac: F1 signature read @0x18000000=0x15264345
                            [    4.529864] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
                            [    4.530296] usbcore: registered new interface driver brcmfmac
                            [    4.558432] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt failed with error -2
                            [    4.605436] cdc_acm 1-1.4:1.0: ttyACM0: USB ACM device
                            [    4.608192] usbcore: registered new interface driver cdc_acm
                            [    4.608206] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
                            [    4.802263] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
                            [    4.812906] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Mar 23 2020 02:19:54 version 7.45.206 (r725000 CY) FWID 01-88ee44ea
                            [    6.193838] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
                            [    6.652176] random: crng init done
                            [    6.652194] random: 7 urandom warning(s) missed due to ratelimiting
                            [    6.799733] uart-pl011 fe201000.serial: no DMA platform data
                            [    6.914750] Adding 102396k swap on /var/swap.  Priority:-2 extents:1 across:102396k SSFS
                            [    7.466039] capability: warning: `jsvc' uses 32-bit capabilities (legacy support in use)
                            [   12.348893] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
                            [   14.089104] Bluetooth: Core ver 2.22
                            [   14.089148] NET: Registered protocol family 31
                            [   14.089154] Bluetooth: HCI device and connection manager initialized
                            [   14.089167] Bluetooth: HCI socket layer initialized
                            [   14.089177] Bluetooth: L2CAP socket layer initialized
                            [   14.089193] Bluetooth: SCO socket layer initialized
                            [   14.098769] Bluetooth: HCI UART driver ver 2.3
                            [   14.098778] Bluetooth: HCI UART protocol H4 registered
                            [   14.098816] Bluetooth: HCI UART protocol Three-wire (H5) registered
                            [   14.098959] Bluetooth: HCI UART protocol Broadcom registered
                            [   14.293635] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
                            [   14.293643] Bluetooth: BNEP filters: protocol multicast
                            [   14.293659] Bluetooth: BNEP socket layer initialized
                            
                            H 1 Reply Last reply Reply Quote 0
                            • H
                              Highpressure @Highpressure last edited by Highpressure

                              @Highpressure

                              bin zwar der lösung oder dem stick tausch noch nicht näher, aber jetzt war es wieder soweit, dass er abgeschmiert ist

                              im log steht dann

                              zigbee.1	2020-12-30 17:37:33.213	error	at Timer.processTimers (timers.js:223:10)
                              zigbee.1	2020-12-30 17:37:33.213	error	at listOnTimeout (timers.js:263:5)
                              zigbee.1	2020-12-30 17:37:33.213	error	at tryOnTimeout (timers.js:300:5)
                              zigbee.1	2020-12-30 17:37:33.213	error	at ontimeout (timers.js:436:11)
                              zigbee.1	2020-12-30 17:37:33.213	error	at Timeout.waiter.timer.setTimeout [as _onTimeout] (/opt/iobroker/node_modules/zigbee-herdsman/dist/utils/waitress.js:46:35)
                              zigbee.1	2020-12-30 17:37:33.213	error	(886) Error on send command to 0x086bd7fffe3f9fae. Error: Error: Command 0x086bd7fffe3f9fae/1 genLevelCtrl.moveToLevelWithOnOff({"level":76,"transtime":0}, {"timeout":10000,"disableResponse":false,"d
                              zigbee.1	2020-12-30 17:37:10.158	error	at Timer.processTimers (timers.js:223:10)
                              zigbee.1	2020-12-30 17:37:10.158	error	at listOnTimeout (timers.js:263:5)
                              zigbee.1	2020-12-30 17:37:10.158	error	at tryOnTimeout (timers.js:300:5)
                              zigbee.1	2020-12-30 17:37:10.158	error	at ontimeout (timers.js:436:11)
                              zigbee.1	2020-12-30 17:37:10.158	error	at Timeout.waiter.timer.setTimeout [as _onTimeout] (/opt/iobroker/node_modules/zigbee-herdsman/dist/utils/waitress.js:46:35)
                              zigbee.1	2020-12-30 17:37:10.158	error	(886) Error on send command to 0x086bd7fffe3f9fae. Error: Error: Command 0x086bd7fffe3f9fae/1 genOnOff.on({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse"
                              zigbee.1	2020-12-30 17:36:47.085	error	at Timer.processTimers (timers.js:223:10)
                              zigbee.1	2020-12-30 17:36:47.085	error	at listOnTimeout (timers.js:263:5)
                              zigbee.1	2020-12-30 17:36:47.085	error	at tryOnTimeout (timers.js:300:5)
                              zigbee.1	2020-12-30 17:36:47.085	error	at ontimeout (timers.js:436:11)
                              zigbee.1	2020-12-30 17:36:47.085	error	at Timeout.waiter.timer.setTimeout [as _onTimeout] (/opt/iobroker/node_modules/zigbee-herdsman/dist/utils/waitress.js:46:35)
                              zigbee.1	2020-12-30 17:36:47.085	error	(886) Error on send command to 0x086bd7fffe3f9fae. Error: Error: Command 0x086bd7fffe3f9fae/1 genOnOff.off({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse
                              zigbee.1	2020-12-30 17:36:24.046	error	at Timer.processTimers (timers.js:223:10)
                              zigbee.1	2020-12-30 17:36:24.046	error	at listOnTimeout (timers.js:263:5)
                              zigbee.1	2020-12-30 17:36:24.046	error	at tryOnTimeout (timers.js:300:5)
                              zigbee.1	2020-12-30 17:36:24.046	error	at ontimeout (timers.js:436:11)
                              zigbee.1	2020-12-30 17:36:24.046	error	at Timeout.waiter.timer.setTimeout [as _onTimeout] (/opt/iobroker/node_modules/zigbee-herdsman/dist/utils/waitress.js:46:35)
                              zigbee.1	2020-12-30 17:36:24.046	error	(886) Error on send command to 0x086bd7fffe5b77a5. Error: Error: Command 0x086bd7fffe5b77a5/1 genLevelCtrl.moveToLevelWithOnOff({"level":254,"transtime":0}, {"timeout":10000,"disableResponse":false,"
                              

                              der adapter ist zu dem zeitpunkt grün und alles sieht aus als würde es funktionieren
                              starte ich den adapter neu oder händisch, finde ich im log (hier stop und start manuell) folgendes

                              host.iobroker86	2020-12-30 23:41:54.027	info	Do not restart adapter system.adapter.zigbee.1 because desired by instance
                              host.iobroker86	2020-12-30 23:41:54.026	error	instance system.adapter.zigbee.1 terminated by request of the instance itself and will not be restarted, before user restarts it.
                              zigbee.1	2020-12-30 23:41:50.609	info	(4461) Starting Zigbee npm ...
                              zigbee.1	2020-12-30 23:41:50.516	info	(4461) starting. Version 1.3.1 in /opt/iobroker/node_modules/iobroker.zigbee, node: v10.23.0, js-controller: 3.1.6
                              host.iobroker86	2020-12-30 23:41:48.738	info	instance system.adapter.zigbee.1 started with pid 4461
                              host.iobroker86	2020-12-30 23:41:48.699	info	"system.adapter.zigbee.1" enabled
                              host.iobroker86	2020-12-30 23:41:18.384	info	stopInstance system.adapter.zigbee.1 killing pid 886
                              zigbee.1	2020-12-30 23:41:17.891	info	(886) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                              zigbee.1	2020-12-30 23:41:17.889	info	(886) terminating
                              zigbee.1	2020-12-30 23:41:17.390	info	(886) Zigbee: disabling joining new devices.
                              zigbee.1	2020-12-30 23:41:17.385	info	(886) cleaned everything up...
                              zigbee.1	2020-12-30 23:41:17.382	info	(886) Got terminate signal TERMINATE_YOURSELF
                              host.iobroker86	2020-12-30 23:41:17.380	info	stopInstance system.adapter.zigbee.1 send kill signal
                              host.iobroker86	2020-12-30 23:41:17.372	info	stopInstance system.adapter.zigbee.1 (force=false, process=true)
                              host.iobroker86	2020-12-30 23:41:17.356	info	"system.adapter.zigbee.1" disabled
                              

                              der adapter lässt sich nun wie gesagt nicht mehr starten, bis ich nicht den raspberry durchstarte

                              in dmesg (das ich zuvor mit dmesg -c) geleert habe finde ich nun

                              root@iobroker86:/var/log# dmesg
                              [105293.877554] cdc_acm 1-1.4:1.0: failed to set dtr/rts
                              [105298.917773] cdc_acm 1-1.4:1.0: failed to set dtr/rts
                              [105348.758906] cdc_acm 1-1.4:1.0: failed to set dtr/rts
                              
                              

                              ^^^das hier kann ich aber auch nicht durch adapter neustarts replizieren - könnte also auch zufall sein.

                              ich hab nun mal das debug logging aktiviert.
                              beim erneuten start versuch taucht nun im log folgendes auf

                              zigbee.1	2020-12-31 00:48:50.127	error	(4566) Error: Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port' at Znp.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/zn
                              zigbee.1	2020-12-31 00:48:50.125	error	(4566) Failed to start Zigbee
                              zigbee.1	2020-12-31 00:48:44.827	info	(4566) Starting Zigbee npm ...
                              zigbee.1	2020-12-31 00:48:44.826	info	(4566) Try to reconnect. 1 attempts left
                              zigbee.1	2020-12-31 00:48:34.824	error	(4566) Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms) at ZStackAdapter.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackA
                              zigbee.1	2020-12-31 00:48:34.822	error	(4566) Failed to start Zigbee
                              

                              ob zufall oder nicht, nun hab ich im dmesg auch mittlerweile 3 weitere

                              
                              [105655.486763] cdc_acm 1-1.4:1.0: failed to set dtr/rts
                              [105660.527003] cdc_acm 1-1.4:1.0: failed to set dtr/rts
                              [105710.448188] cdc_acm 1-1.4:1.0: failed to set dtr/rts
                              
                              

                              EDIT > https://forum.iobroker.net/topic/20154/cc2531-steigt-regelmässig-aus-nach-2-4-stunden/12
                              gut, stick oder firmware wohl schuld - hier hatte in 2019 jemand auch die set dtr/rts meldungen

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

                                @Highpressure Du solltest keine root shell haben.

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

                                  @Highpressure dein erstes log ist unnvollständig. Insbesondere fehlen bei den Fehlermeldungen die Ursachen weil die Zeilen abgeschnitten sind.

                                  Bitte poste die kompletten Zeilen.

                                  A.

                                  @Thomas-Braun sagte in Unerklärliche ZigBee Abstürze:

                                  @Highpressure Du solltest keine root shell haben.

                                  Das mag stimmen, hat aber mit deinem Fehler nichts zu tun.

                                  A.

                                  1 Reply Last reply Reply Quote 0
                                  • H
                                    Highpressure @Thomas Braun last edited by

                                    @Thomas-Braun

                                    log liefere ich nach

                                    ich turncat´e mal und flashe gerade den stick neu
                                    dann starte ich alles sauber neu und warte ob es wieder auftritt
                                    wenn ja, lade ich die ganzen logs rein

                                    ja, wegen root shell, weiss eh, ich finds aber angenehmer als dauernd sudo tippen zu müssen

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

                                      @Highpressure Dann aber nicht wundern wenn ganz angenehm ein Befehl im root -Kontext durchrasselt und ganz angenehm was unangenehmes anstellt. Das Konzept von sudo ist ja kein Designfehler sondern ganz bewusst so angelegt worden.
                                      Das kann nämlich dann auch zu 'unerklärlichen Fehlern' führen.

                                      H 1 Reply Last reply Reply Quote 0
                                      • H
                                        Highpressure @Thomas Braun last edited by

                                        @thomas-braun ich hab den anderen iobroker auch so aufgesetzt, ok,.. ist schon ein weilchen länger her, aber ich bin lazy und immer root.

                                        so, ich hab jetzt jedenfalls einen neuen Stick gekauft, geflashed, den ersetzt,.. alles wunderbar
                                        Tagelang alles gut und seit heute wieder dasselbe Fehlerbild.

                                        kern.log hat seit heute auch das erste mal wieder

                                        Jan 12 21:55:25 iobroker86 kernel: [369073.541152] cdc_acm 1-1.1:1.0: failed to set dtr/rts
                                        Jan 12 21:56:02 iobroker86 kernel: [369111.312079] cdc_acm 1-1.1:1.0: failed to set dtr/rts
                                        Jan 12 21:56:58 iobroker86 kernel: [369166.983335] cdc_acm 1-1.1:1.0: failed to set dtr/rts
                                        Jan 12 21:57:05 iobroker86 kernel: [369173.703547] cdc_acm 1-1.1:1.0: failed to set dtr/rts
                                        Jan 12 21:57:55 iobroker86 kernel: [369223.624750] cdc_acm 1-1.1:1.0: failed to set dtr/rts

                                        Kann doch nicht sein, dass mir die Hardware jedes mal sterben geht?
                                        Der erste kam von AliExpress den zweiten hab ich jetzt über Amazon bestellt, damit er schneller da ist.

                                        Wenns an der Software läge, dann hätte das ja sofort wieder passieren müssen, oder zumindest innerhalb von 24h.

                                        Es ist mir ein Rätsel!

                                        Nunja, ich werde den Raspberry wohl plätten und neuaufsetzen und schauen ob das was ändert - sudo ohne root
                                        Glaub zwar nicht dran, aber we´ll see

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

                                          @highpressure said in Unerklärliche ZigBee Abstürze:

                                          ist schon ein weilchen länger her, aber ich bin lazy und immer root.

                                          Ich bin nicht lazy und nie root.
                                          Meine Systeme laufen...

                                          H 1 Reply Last reply Reply Quote 0
                                          • H
                                            Highpressure @Thomas Braun last edited by

                                            @thomas-braun

                                            aa46a3c9-c218-4d9a-b13c-9c2ea7787a0b-image.png

                                            ist er zu stark, bist du zu schwach 🤣

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

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            598
                                            Online

                                            31.7k
                                            Users

                                            79.6k
                                            Topics

                                            1.3m
                                            Posts

                                            cc2531 crash reboot zigbee
                                            4
                                            21
                                            1056
                                            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