mit Charly kein Geräte anlernen möglich

Einrichtung, Nutzung und Hilfe zu RaspberryMatic (OCCU auf Raspberry Pi)

Moderatoren: jmaus, Co-Administratoren

Antworten
JochenV
Beiträge: 9
Registriert: 04.06.2021, 23:04
System: Alternative CCU (auf Basis OCCU)
Danksagung erhalten: 1 Mal

mit Charly kein Geräte anlernen möglich

Beitrag von JochenV » 05.06.2021, 00:28

Hallo Zusammen,

ich möchte gern von HM AccessPoint auf HM Zentrale Clarly um zu steigen.

Hardware:
Raspberry Pi 3+ (16GB Sd) RaspberryMatic-3.57.5.20210525-rpi3.img
RPI-RF-MOD Firmware 4.2.14
Netzteil 5V 3A
Steckdose HMIP-PSM
Temperaturanzeige HMIP-WTH-2
Fernbedienung HMIP-RC8
und Heizkörperthermostate und Fensterkontakte

Der Raspberry ist über LAN angeschlossen und kommt ins Internet.
Der Raspberry blinket Grüm. Das Modul leuchtet Blau.
Frage 1.
Kann man die Daten des AccessPoint irgendwie kopieren oder muss alles neu eingerichtet werden ?

Frage 2.
Ich bekomme die Meldung "WatchDog-Alarm - ausgelöst - under-voltage detected"
Wieso kommt diese Meldung ? Der Stromverbrauch liegt bei weniger 0,5 A und so sollte die gemessene Spannung von gering über 5V.

Frage 3 und wichtigste Frage.
ich kann keine Geräte anlernen. Ich habe es mit der Steckdose, mit der Fernbedienung und Temperaturanzeige probiert.
Die Temperaturanzeige (die ich jetzt als erstes anmelden möchte) habe ich auf Werkeinstellungen zurück gesetzt. Wenn ich die Batterien einsetzte leuchtet die grüne LED ein mal kurt auf und dann blinkt die LED alle 10 sec. Orange.
Bei RaspberryMatic - Software betätige den Button "HMIP Gerät anlernen". Es kommt keine Meldung im Posteingang. Auch "HMIP Gerät anlernen (lokal)" funktioniert nicht.
Mache ich eventuell etwas falsch. Kann jemand helfen ?

Anbei das Logfile

Code: Alles auswählen

***** messages *****
Jun  4 23:55:05 localhost syslog.info syslogd started: BusyBox v1.33.0
Jun  4 23:55:05 localhost user.notice kernel: klogd started: BusyBox v1.33.0 (2021-05-25 09:39:24 UTC)
Jun  4 23:55:05 localhost user.info kernel: [    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
Jun  4 23:55:05 localhost user.notice kernel: [    0.000000] Linux version 5.10.17 (builder@db5f100795dd) (aarch64-buildroot-linux-gnu-gcc.br_real (Buildroot -g6f08f9d) 9.3.0, GNU ld (GNU Binutils) 2.35.2) #1 SMP PREEMPT Tue May 25 10:15:23 UTC 2021
Jun  4 23:55:05 localhost user.info kernel: [    0.000000] Machine model: Raspberry Pi 3 Model B Plus Rev 1.3
Jun  4 23:55:05 localhost user.info kernel: [    0.000000] efi: UEFI not found.
Jun  4 23:55:05 localhost user.info kernel: [    0.000000] Reserved memory: created CMA memory pool at 0x000000003a000000, size 64 MiB
Jun  4 23:55:05 localhost user.info kernel: [    0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool
Jun  4 23:55:05 localhost user.info kernel: [    0.000000] Zone ranges:
Jun  4 23:55:05 localhost user.info kernel: [    0.000000]   DMA      [mem 0x0000000000000000-0x000000003dffffff]
Jun  4 23:55:05 localhost user.info kernel: [    0.000000]   DMA32    empty
Jun  4 23:55:05 localhost user.info kernel: [    0.000000]   Normal   empty
Jun  4 23:55:05 localhost user.info kernel: [    0.000000] Movable zone start for each node
Jun  4 23:55:05 localhost user.info kernel: [    0.000000] Early memory node ranges
Jun  4 23:55:05 localhost user.info kernel: [    0.000000]   node   0: [mem 0x0000000000000000-0x000000003dffffff]
Jun  4 23:55:05 localhost user.info kernel: [    0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x000000003dffffff]
Jun  4 23:55:05 localhost user.debug kernel: [    0.000000] On node 0 totalpages: 253952
Jun  4 23:55:05 localhost user.debug kernel: [    0.000000]   DMA zone: 3968 pages used for memmap
Jun  4 23:55:05 localhost user.debug kernel: [    0.000000]   DMA zone: 0 pages reserved
Jun  4 23:55:05 localhost user.debug kernel: [    0.000000]   DMA zone: 253952 pages, LIFO batch:63
Jun  4 23:55:05 localhost user.info kernel: [    0.000000] percpu: Embedded 30 pages/cpu s83224 r8192 d31464 u122880
Jun  4 23:55:05 localhost user.debug kernel: [    0.000000] pcpu-alloc: s83224 r8192 d31464 u122880 alloc=30*4096
Jun  4 23:55:05 localhost user.debug kernel: [    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 
Jun  4 23:55:05 localhost user.info kernel: [    0.000000] Detected VIPT I-cache on CPU0
Jun  4 23:55:05 localhost user.info kernel: [    0.000000] CPU features: detected: ARM erratum 845719
Jun  4 23:55:05 localhost user.info kernel: [    0.000000] CPU features: detected: ARM erratum 843419
Jun  4 23:55:05 localhost user.info kernel: [    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 249984
Jun  4 23:55:05 localhost user.notice kernel: [    0.000000] Kernel command line: dwc_otg.lpm_enable=0 sdhci_bcm2708.enable_llm=0 console=tty2 kgdboc=tty2 scandelay=5 root=PARTUUID=deedbeef-02 ro rootfstype=ext4 elevator=deadline fsck.repair=yes lapic rootwait rootdelay=5 consoleblank=120 logo.nologo quiet loglevel=0 init_on_alloc=1 init_on_free=1 slab_nomerge pti=on net.ifnames=0 usb-storage.quirks=  coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=720 bcm2708_fb.fbheight=480 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000  empty
Jun  4 23:55:05 localhost user.warn kernel: [    0.000000] Kernel parameter elevator= does not have any effect anymore.
Jun  4 23:55:05 localhost user.warn kernel: [    0.000000] Please use sysfs to set IO scheduler for individual devices.
Jun  4 23:55:05 localhost user.info kernel: [    0.000000] Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes, linear)
Jun  4 23:55:05 localhost user.info kernel: [    0.000000] Inode-cache hash table entries: 65536 (order: 7, 524288 bytes, linear)
Jun  4 23:55:05 localhost user.info kernel: [    0.000000] mem auto-init: stack:off, heap alloc:on, heap free:on
Jun  4 23:55:05 localhost user.info kernel: [    0.000000] mem auto-init: clearing system memory may take some time...
Jun  4 23:55:05 localhost user.info kernel: [    0.000000] Memory: 909856K/1015808K available (9984K kernel code, 1688K rwdata, 3452K rodata, 3328K init, 1233K bss, 40416K reserved, 65536K cma-reserved)
Jun  4 23:55:05 localhost user.info kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
Jun  4 23:55:05 localhost user.info kernel: [    0.000000] ftrace: allocating 32429 entries in 127 pages
Jun  4 23:55:05 localhost user.info kernel: [    0.000000] ftrace: allocated 127 pages with 7 groups
Jun  4 23:55:05 localhost user.info kernel: [    0.000000] rcu: Preemptible hierarchical RCU implementation.
Jun  4 23:55:05 localhost user.info kernel: [    0.000000] rcu: 	RCU event tracing is enabled.
Jun  4 23:55:05 localhost user.info kernel: [    0.000000] rcu: 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=4.
Jun  4 23:55:05 localhost user.info kernel: [    0.000000] 	Trampoline variant of Tasks RCU enabled.
Jun  4 23:55:05 localhost user.info kernel: [    0.000000] 	Rude variant of Tasks RCU enabled.
Jun  4 23:55:05 localhost user.info kernel: [    0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
Jun  4 23:55:05 localhost user.info kernel: [    0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
Jun  4 23:55:05 localhost user.info kernel: [    0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
Jun  4 23:55:05 localhost user.notice kernel: [    0.000000] random: get_random_bytes called from start_kernel+0x3b8/0x574 with crng_init=0
Jun  4 23:55:05 localhost user.info kernel: [    0.000000] arch_timer: cp15 timer(s) running at 19.20MHz (phys).
Jun  4 23:55:05 localhost user.info kernel: [    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns
Jun  4 23:55:05 localhost user.info kernel: [    0.000008] sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 4398046511078ns
Jun  4 23:55:05 localhost user.info kernel: [    0.000307] Console: colour dummy device 80x25
Jun  4 23:55:05 localhost user.info kernel: [    0.000377] printk: console [tty2] enabled
Jun  4 23:55:05 localhost user.info kernel: [    0.000441] Calibrating delay loop (skipped), value calculated using timer frequency.. 38.40 BogoMIPS (lpj=76800)
Jun  4 23:55:05 localhost user.info kernel: [    0.000476] pid_max: default: 32768 minimum: 301
Jun  4 23:55:05 localhost user.info kernel: [    0.000680] LSM: Security Framework initializing
Jun  4 23:55:05 localhost user.info kernel: [    0.000715] Yama: becoming mindful.
Jun  4 23:55:05 localhost user.info kernel: [    0.000994] Mount-cache hash table entries: 2048 (order: 2, 16384 bytes, linear)
Jun  4 23:55:05 localhost user.info kernel: [    0.001017] Mountpoint-cache hash table entries: 2048 (order: 2, 16384 bytes, linear)
Jun  4 23:55:05 localhost user.info kernel: [    0.002661] Disabling memory control group subsystem
Jun  4 23:55:05 localhost user.info kernel: [    0.005379] rcu: Hierarchical SRCU implementation.
Jun  4 23:55:05 localhost user.info kernel: [    0.006581] EFI services will not be available.
Jun  4 23:55:05 localhost user.info kernel: [    0.007240] smp: Bringing up secondary CPUs ...
Jun  4 23:55:05 localhost user.info kernel: [    0.008620] Detected VIPT I-cache on CPU1
Jun  4 23:55:05 localhost user.info kernel: [    0.008710] CPU1: Booted secondary processor 0x0000000001 [0x410fd034]
Jun  4 23:55:05 localhost user.info kernel: [    0.010252] Detected VIPT I-cache on CPU2
Jun  4 23:55:05 localhost user.info kernel: [    0.010312] CPU2: Booted secondary processor 0x0000000002 [0x410fd034]
Jun  4 23:55:05 localhost user.info kernel: [    0.011810] Detected VIPT I-cache on CPU3
Jun  4 23:55:05 localhost user.info kernel: [    0.011866] CPU3: Booted secondary processor 0x0000000003 [0x410fd034]
Jun  4 23:55:05 localhost user.info kernel: [    0.012082] smp: Brought up 1 node, 4 CPUs
Jun  4 23:55:05 localhost user.info kernel: [    0.012104] SMP: Total of 4 processors activated.
Jun  4 23:55:05 localhost user.info kernel: [    0.012123] CPU features: detected: 32-bit EL0 Support
Jun  4 23:55:05 localhost user.info kernel: [    0.012140] CPU features: detected: CRC32 instructions
Jun  4 23:55:05 localhost user.info kernel: [    0.047885] CPU: All CPU(s) started at EL2
Jun  4 23:55:05 localhost user.info kernel: [    0.047970] alternatives: patching kernel code
Jun  4 23:55:05 localhost user.info kernel: [    0.049809] devtmpfs: initialized
Jun  4 23:55:05 localhost user.notice kernel: [    0.072540] Enabled cp15_barrier support
Jun  4 23:55:05 localhost user.notice kernel: [    0.072590] Enabled setend support
Jun  4 23:55:05 localhost user.info kernel: [    0.072907] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
Jun  4 23:55:05 localhost user.info kernel: [    0.072943] futex hash table entries: 1024 (order: 4, 65536 bytes, linear)
Jun  4 23:55:05 localhost user.info kernel: [    0.138002] pinctrl core: initialized pinctrl subsystem
Jun  4 23:55:05 localhost user.info kernel: [    0.139217] DMI not present or invalid.
Jun  4 23:55:05 localhost user.info kernel: [    0.139738] NET: Registered protocol family 16
Jun  4 23:55:05 localhost user.info kernel: [    0.153679] DMA: preallocated 1024 KiB GFP_KERNEL pool for atomic allocations
Jun  4 23:55:05 localhost user.info kernel: [    0.154587] DMA: preallocated 1024 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations
Jun  4 23:55:05 localhost user.info kernel: [    0.157018] DMA: preallocated 1024 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations
Jun  4 23:55:05 localhost user.info kernel: [    0.157861] thermal_sys: Registered thermal governor 'step_wise'
Jun  4 23:55:05 localhost user.info kernel: [    0.158222] cpuidle: using governor ladder
Jun  4 23:55:05 localhost user.info kernel: [    0.158301] cpuidle: using governor menu
Jun  4 23:55:05 localhost user.info kernel: [    0.159356] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
Jun  4 23:55:05 localhost user.info kernel: [    0.159621] ASID allocator initialised with 65536 entries
Jun  4 23:55:05 localhost user.info kernel: [    0.188146] bcm2835-mbox 3f00b880.mailbox: mailbox enabled
Jun  4 23:55:05 localhost user.info kernel: [    0.197045] raspberrypi-firmware soc:firmware: Attached to firmware from 2021-04-30T13:47:07, variant start
Jun  4 23:55:05 localhost user.info kernel: [    0.201060] raspberrypi-firmware soc:firmware: Firmware hash is d7f29d96450abfc77cd6cf011af1faf1e03e5e56
Jun  4 23:55:05 localhost user.info kernel: [    0.247132] bcm2835-dma 3f007000.dma: DMA legacy API manager, dmachans=0x1
Jun  4 23:55:05 localhost user.notice kernel: [    0.250385] SCSI subsystem initialized
Jun  4 23:55:05 localhost user.debug kernel: [    0.250760] libata version 3.00 loaded.
Jun  4 23:55:05 localhost user.info kernel: [    0.251101] usbcore: registered new interface driver usbfs
Jun  4 23:55:05 localhost user.info kernel: [    0.251184] usbcore: registered new interface driver hub
Jun  4 23:55:05 localhost user.info kernel: [    0.251273] usbcore: registered new device driver usb
Jun  4 23:55:05 localhost user.info kernel: [    0.252508] NetLabel: Initializing
Jun  4 23:55:05 localhost user.info kernel: [    0.252526] NetLabel:  domain hash size = 128
Jun  4 23:55:05 localhost user.info kernel: [    0.252540] NetLabel:  protocols = UNLABELED CIPSOv4 CALIPSO
Jun  4 23:55:05 localhost user.info kernel: [    0.252691] NetLabel:  unlabeled traffic allowed by default
Jun  4 23:55:05 localhost user.info kernel: [    0.254210] clocksource: Switched to clocksource arch_sys_counter
Jun  4 23:55:05 localhost user.notice kernel: [    1.999024] VFS: Disk quotas dquot_6.6.0
Jun  4 23:55:05 localhost user.info kernel: [    1.999163] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Jun  4 23:55:05 localhost user.notice kernel: [    1.999428] FS-Cache: Loaded
Jun  4 23:55:05 localhost user.info kernel: [    1.999768] CacheFiles: Loaded
Jun  4 23:55:05 localhost user.info kernel: [    2.000047] simple-framebuffer 3eaa9000.framebuffer: framebuffer at 0x3eaa9000, 0x151800 bytes, mapped to 0x(____ptrval____)
Jun  4 23:55:05 localhost user.info kernel: [    2.000071] simple-framebuffer 3eaa9000.framebuffer: format=a8r8g8b8, mode=720x480x32, linelength=2880
Jun  4 23:55:05 localhost user.info kernel: [    2.000630] Console: switching to colour frame buffer device 90x30
Jun  4 23:55:05 localhost user.info kernel: [    2.006472] simple-framebuffer 3eaa9000.framebuffer: fb0: simplefb registered!
Jun  4 23:55:05 localhost user.info kernel: [    2.019821] NET: Registered protocol family 2
Jun  4 23:55:05 localhost user.info kernel: [    2.021117] tcp_listen_portaddr_hash hash table entries: 512 (order: 1, 8192 bytes, linear)
Jun  4 23:55:05 localhost user.info kernel: [    2.021176] TCP established hash table entries: 8192 (order: 4, 65536 bytes, linear)
Jun  4 23:55:05 localhost user.info kernel: [    2.021435] TCP bind hash table entries: 8192 (order: 5, 131072 bytes, linear)
Jun  4 23:55:05 localhost user.info kernel: [    2.021639] TCP: Hash tables configured (established 8192 bind 8192)
Jun  4 23:55:05 localhost user.info kernel: [    2.021812] UDP hash table entries: 512 (order: 2, 16384 bytes, linear)
Jun  4 23:55:05 localhost user.info kernel: [    2.021884] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes, linear)
Jun  4 23:55:05 localhost user.info kernel: [    2.022370] NET: Registered protocol family 1
Jun  4 23:55:05 localhost user.info kernel: [    2.023540] RPC: Registered named UNIX socket transport module.
Jun  4 23:55:05 localhost user.info kernel: [    2.023557] RPC: Registered udp transport module.
Jun  4 23:55:05 localhost user.info kernel: [    2.023571] RPC: Registered tcp transport module.
Jun  4 23:55:05 localhost user.info kernel: [    2.023586] RPC: Registered tcp NFSv4.1 backchannel transport module.
Jun  4 23:55:05 localhost user.info kernel: [    2.026641] hw perfevents: enabled with armv8_cortex_a53 PMU driver, 7 counters available
Jun  4 23:55:05 localhost user.notice kernel: [    2.032113] Initialise system trusted keyrings
Jun  4 23:55:05 localhost user.info kernel: [    2.032585] workingset: timestamp_bits=46 max_order=18 bucket_order=0
Jun  4 23:55:05 localhost user.info kernel: [    2.044769] zbud: loaded
Jun  4 23:55:05 localhost user.notice kernel: [    2.049247] FS-Cache: Netfs 'nfs' registered for caching
Jun  4 23:55:05 localhost user.notice kernel: [    2.050592] NFS: Registering the id_resolver key type
Jun  4 23:55:05 localhost user.notice kernel: [    2.050653] Key type id_resolver registered
Jun  4 23:55:05 localhost user.notice kernel: [    2.050669] Key type id_legacy registered
Jun  4 23:55:05 localhost user.info kernel: [    2.050844] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
Jun  4 23:55:05 localhost user.notice kernel: [    2.053750] Key type asymmetric registered
Jun  4 23:55:05 localhost user.notice kernel: [    2.053768] Asymmetric key parser 'x509' registered
Jun  4 23:55:05 localhost user.info kernel: [    2.053841] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251)
Jun  4 23:55:05 localhost user.info kernel: [    2.054244] io scheduler mq-deadline registered
Jun  4 23:55:05 localhost user.info kernel: [    2.054262] io scheduler kyber registered
Jun  4 23:55:05 localhost user.info kernel: [    2.064500] Serial: 8250/16550 driver, 1 ports, IRQ sharing enabled
Jun  4 23:55:05 localhost user.info kernel: [    2.068008] bcm2835-rng 3f104000.rng: hwrng registered
Jun  4 23:55:05 localhost user.info kernel: [    2.068637] vc-mem: phys_addr:0x00000000 mem_base=0x3ec00000 mem_size:0x40000000(1024 MiB)
Jun  4 23:55:05 localhost user.info kernel: [    2.069815] gpiomem-bcm2835 3f200000.gpiomem: Initialised: Registers at 0x3f200000
Jun  4 23:55:05 localhost user.warn kernel: [    2.070445] cacheinfo: Unable to detect cache hierarchy for CPU 0
Jun  4 23:55:05 localhost user.info kernel: [    2.087347] brd: module loaded
Jun  4 23:55:05 localhost user.info kernel: [    2.104440] loop: module loaded
Jun  4 23:55:05 localhost user.info kernel: [    2.106056] Loading iSCSI transport class v2.0-870.
Jun  4 23:55:05 localhost user.info kernel: [    2.108373] libphy: Fixed MDIO Bus: probed
Jun  4 23:55:05 localhost user.info kernel: [    2.108674] tun: Universal TUN/TAP device driver, 1.6
Jun  4 23:55:05 localhost user.info kernel: [    2.109077] usbcore: registered new interface driver lan78xx
Jun  4 23:55:05 localhost user.info kernel: [    2.109164] usbcore: registered new interface driver smsc95xx
Jun  4 23:55:05 localhost user.info kernel: [    2.109194] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
Jun  4 23:55:05 localhost user.warn kernel: [    2.310079] Core Release: 2.80a
Jun  4 23:55:05 localhost user.warn kernel: [    2.310100] Setting default values for core params
Jun  4 23:55:05 localhost user.warn kernel: [    2.310133] Finished setting default values for core params
Jun  4 23:55:05 localhost user.warn kernel: [    2.510625] Using Buffer DMA mode
Jun  4 23:55:05 localhost user.warn kernel: [    2.510642] Periodic Transfer Interrupt Enhancement - disabled
Jun  4 23:55:05 localhost user.warn kernel: [    2.510657] Multiprocessor Interrupt Enhancement - disabled
Jun  4 23:55:05 localhost user.warn kernel: [    2.510674] OTG VER PARAM: 0, OTG VER FLAG: 0
Jun  4 23:55:05 localhost user.warn kernel: [    2.510694] Dedicated Tx FIFOs mode
Jun  4 23:55:05 localhost user.warn kernel: [    2.518800] 
Jun  4 23:55:05 localhost user.warn kernel: [    2.518826] WARN::dwc_otg_hcd_init:1072: FIQ DMA bounce buffers: virt = ffffffc0117bb000 dma = 0x00000000fa400000 len=9024
Jun  4 23:55:05 localhost user.warn kernel: [    2.518864] FIQ FSM acceleration enabled for :
Jun  4 23:55:05 localhost user.warn kernel: [    2.518864] Non-periodic Split Transactions
Jun  4 23:55:05 localhost user.warn kernel: [    2.518864] Periodic Split Transactions
Jun  4 23:55:05 localhost user.warn kernel: [    2.518864] High-Speed Isochronous Endpoints
Jun  4 23:55:05 localhost user.warn kernel: [    2.518864] Interrupt/Control Split Transaction hack enabled
Jun  4 23:55:05 localhost user.debug kernel: [    2.518882] dwc_otg: Microframe scheduler enabled
Jun  4 23:55:05 localhost user.warn kernel: [    2.518932] 
Jun  4 23:55:05 localhost user.warn kernel: [    2.518949] WARN::hcd_init_fiq:496: MPHI regs_base at ffffffc0113bd000
Jun  4 23:55:05 localhost user.info kernel: [    2.519044] dwc_otg 3f980000.usb: DWC OTG Controller
Jun  4 23:55:05 localhost user.info kernel: [    2.519107] dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1
Jun  4 23:55:05 localhost user.info kernel: [    2.519175] dwc_otg 3f980000.usb: irq 74, io mem 0x00000000
Jun  4 23:55:05 localhost user.warn kernel: [    2.519231] Init: Port Power? op_state=1
Jun  4 23:55:05 localhost user.warn kernel: [    2.519246] Init: Power Port (0)
Jun  4 23:55:05 localhost user.info kernel: [    2.519755] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.10
Jun  4 23:55:05 localhost user.info kernel: [    2.519777] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jun  4 23:55:05 localhost user.info kernel: [    2.519795] usb usb1: Product: DWC OTG Controller
Jun  4 23:55:05 localhost user.info kernel: [    2.519813] usb usb1: Manufacturer: Linux 5.10.17 dwc_otg_hcd
Jun  4 23:55:05 localhost user.info kernel: [    2.519831] usb usb1: SerialNumber: 3f980000.usb
Jun  4 23:55:05 localhost user.info kernel: [    2.520829] hub 1-0:1.0: USB hub found
Jun  4 23:55:05 localhost user.info kernel: [    2.520919] hub 1-0:1.0: 1 port detected
Jun  4 23:55:05 localhost user.debug kernel: [    2.522391] dwc_otg: FIQ enabled
Jun  4 23:55:05 localhost user.debug kernel: [    2.522409] dwc_otg: NAK holdoff enabled
Jun  4 23:55:05 localhost user.debug kernel: [    2.522423] dwc_otg: FIQ split-transaction FSM enabled
Jun  4 23:55:05 localhost user.debug kernel: [    2.522445] Module dwc_common_port init
Jun  4 23:55:05 localhost user.info kernel: [    2.523750] usbcore: registered new interface driver uas
Jun  4 23:55:05 localhost user.info kernel: [    2.523877] usbcore: registered new interface driver usb-storage
Jun  4 23:55:05 localhost user.info kernel: [    2.524395] mousedev: PS/2 mouse device common for all mice
Jun  4 23:55:05 localhost user.info kernel: [    2.526482] bcm2835-wdt bcm2835-wdt: Broadcom BCM2835 watchdog timer
Jun  4 23:55:05 localhost user.info kernel: [    2.531299] sdhci: Secure Digital Host Controller Interface driver
Jun  4 23:55:05 localhost user.info kernel: [    2.531318] sdhci: Copyright(c) Pierre Ossman
Jun  4 23:55:05 localhost user.info kernel: [    2.532138] mmc-bcm2835 3f300000.mmcnr: could not get clk, deferring probe
Jun  4 23:55:05 localhost user.info kernel: [    2.533041] sdhost-bcm2835 3f202000.mmc: could not get clk, deferring probe
Jun  4 23:55:05 localhost user.info kernel: [    2.533393] sdhci-pltfm: SDHCI platform and OF driver helper
Jun  4 23:55:05 localhost user.info kernel: [    2.538063] ledtrig-cpu: registered to indicate activity on CPUs
Jun  4 23:55:05 localhost user.info kernel: [    2.538135] hid: raw HID events driver (C) Jiri Kosina
Jun  4 23:55:05 localhost user.info kernel: [    2.538345] usbcore: registered new interface driver usbhid
Jun  4 23:55:05 localhost user.info kernel: [    2.538352] usbhid: USB HID core driver
Jun  4 23:55:05 localhost user.info kernel: [    2.542738] NET: Registered protocol family 17
Jun  4 23:55:05 localhost user.notice kernel: [    2.543010] Key type dns_resolver registered
Jun  4 23:55:05 localhost user.info kernel: [    2.543697] registered taskstats version 1
Jun  4 23:55:05 localhost user.notice kernel: [    2.543714] Loading compiled-in X.509 certificates
Jun  4 23:55:05 localhost user.info kernel: [    2.557421] 3f215040.serial: ttyS0 at MMIO 0x3f215040 (irq = 71, base_baud = 31250000) is a 16550
Jun  4 23:55:05 localhost user.info kernel: [    2.558153] bcm2835-power bcm2835-power: Broadcom BCM2835 power domains driver
Jun  4 23:55:05 localhost user.info kernel: [    2.559423] mmc-bcm2835 3f300000.mmcnr: mmc_debug:0 mmc_debug2:0
Jun  4 23:55:05 localhost user.info kernel: [    2.559433] mmc-bcm2835 3f300000.mmcnr: DMA channel allocated
Jun  4 23:55:05 localhost user.info kernel: [    2.584405] sdhost: log_buf @ (____ptrval____) (c1bee000)
Jun  4 23:55:05 localhost user.warn kernel: [    2.601932] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
Jun  4 23:55:05 localhost user.warn kernel: [    2.603493] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
Jun  4 23:55:05 localhost user.warn kernel: [    2.605057] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
Jun  4 23:55:05 localhost user.warn kernel: [    2.607879] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
Jun  4 23:55:05 localhost user.info kernel: [    2.635006] mmc0: sdhost-bcm2835 loaded - DMA enabled (>1)
Jun  4 23:55:05 localhost user.info kernel: [    2.639451] of_cfs_init
Jun  4 23:55:05 localhost user.info kernel: [    2.639518] of_cfs_init: OK
Jun  4 23:55:05 localhost user.info kernel: [    2.659008] Waiting 5 sec before mounting root device...
Jun  4 23:55:05 localhost user.notice kernel: [    2.669605] random: fast init done
Jun  4 23:55:05 localhost user.info kernel: [    2.693086] mmc1: new high speed SDIO card at address 0001
Jun  4 23:55:05 localhost user.warn kernel: [    2.723435] mmc0: host does not support reading read-only switch, assuming write-enable
Jun  4 23:55:05 localhost user.warn kernel: [    2.726387] Indeed it is in host mode hprt0 = 00021501
Jun  4 23:55:05 localhost user.info kernel: [    2.747895] mmc0: new high speed SDHC card at address aaaa
Jun  4 23:55:05 localhost user.info kernel: [    2.749103] mmcblk0: mmc0:aaaa SC16G 14.8 GiB
Jun  4 23:55:05 localhost user.info kernel: [    2.793519]  mmcblk0: p1 p2 p3
Jun  4 23:55:05 localhost user.info kernel: [    2.914307] usb 1-1: new high-speed USB device number 2 using dwc_otg
Jun  4 23:55:05 localhost user.warn kernel: [    2.914531] Indeed it is in host mode hprt0 = 00001101
Jun  4 23:55:05 localhost user.info kernel: [    3.122850] usb 1-1: New USB device found, idVendor=0424, idProduct=2514, bcdDevice= b.b3
Jun  4 23:55:05 localhost user.info kernel: [    3.122869] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jun  4 23:55:05 localhost user.info kernel: [    3.123790] hub 1-1:1.0: USB hub found
Jun  4 23:55:05 localhost user.info kernel: [    3.123972] hub 1-1:1.0: 4 ports detected
Jun  4 23:55:05 localhost user.info kernel: [    3.410304] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
Jun  4 23:55:05 localhost user.info kernel: [    3.510796] usb 1-1.1: New USB device found, idVendor=0424, idProduct=2514, bcdDevice= b.b3
Jun  4 23:55:05 localhost user.info kernel: [    3.510819] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jun  4 23:55:05 localhost user.info kernel: [    3.511826] hub 1-1.1:1.0: USB hub found
Jun  4 23:55:05 localhost user.info kernel: [    3.511985] hub 1-1.1:1.0: 3 ports detected
Jun  4 23:55:05 localhost user.warn kernel: [    3.865435] dwc_otg_handle_wakeup_detected_intr lxstate = 2
Jun  4 23:55:05 localhost user.notice kernel: [    4.099518] random: crng init done
Jun  4 23:55:05 localhost user.info kernel: [    4.350281] usb 1-1.1.1: new high-speed USB device number 4 using dwc_otg
Jun  4 23:55:05 localhost user.info kernel: [    4.451054] usb 1-1.1.1: New USB device found, idVendor=0424, idProduct=7800, bcdDevice= 3.00
Jun  4 23:55:05 localhost user.info kernel: [    4.451077] usb 1-1.1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jun  4 23:55:05 localhost user.info kernel: [    4.715533] lan78xx 1-1.1.1:1.0 (unnamed net_device) (uninitialized): No External EEPROM. Setting MAC Speed
Jun  4 23:55:05 localhost user.info kernel: [    4.716749] libphy: lan78xx-mdiobus: probed
Jun  4 23:55:05 localhost user.notice kernel: [    4.723281] lan78xx 1-1.1.1:1.0 (unnamed net_device) (uninitialized): int urb period 64
Jun  4 23:55:05 localhost user.info kernel: [    7.918023] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
Jun  4 23:55:05 localhost user.info kernel: [    7.918128] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
Jun  4 23:55:05 localhost user.info kernel: [    7.919023] devtmpfs: mounted
Jun  4 23:55:05 localhost user.info kernel: [    7.928539] Freeing unused kernel memory: 3328K
Jun  4 23:55:05 localhost user.info kernel: [    7.928641] Run /sbin/init as init process
Jun  4 23:55:05 localhost user.debug kernel: [    7.928648]   with arguments:
Jun  4 23:55:05 localhost user.debug kernel: [    7.928655]     /sbin/init
Jun  4 23:55:05 localhost user.debug kernel: [    7.928662]     lapic
Jun  4 23:55:05 localhost user.debug kernel: [    7.928669]     empty
Jun  4 23:55:05 localhost user.debug kernel: [    7.928676]   with environment:
Jun  4 23:55:05 localhost user.debug kernel: [    7.928683]     HOME=/
Jun  4 23:55:05 localhost user.debug kernel: [    7.928690]     TERM=linux
Jun  4 23:55:05 localhost user.debug kernel: [    7.928698]     kgdboc=tty2
Jun  4 23:55:05 localhost user.debug kernel: [    7.928704]     scandelay=5
Jun  4 23:55:05 localhost user.debug kernel: [    7.928711]     pti=on
Jun  4 23:55:05 localhost user.warn kernel: [    8.560000] EXT4-fs: Warning: mounting with data=journal disables delayed allocation, dioread_nolock, O_DIRECT and fast_commit support!
Jun  4 23:55:05 localhost user.info kernel: [    8.566337] EXT4-fs (mmcblk0p3): mounted filesystem with journalled data mode. Opts: data=journal
Jun  4 23:55:05 localhost user.info kernel: [   10.035653] zram: Added device: zram0
Jun  4 23:55:05 localhost user.info kernel: [   10.076076] zram0: detected capacity change from 0 to 1052319744
Jun  4 23:55:05 localhost user.info kernel: [   10.142260] Adding 1027652k swap on /dev/zram0.  Priority:75 extents:1 across:1027652k SSFS
Jun  4 23:55:05 localhost user.info kernel: [   10.214514] i2c /dev entries driver
Jun  4 23:55:05 localhost user.info kernel: [   10.246684] rtc-ds1307 1-0032: registered as rtc0
Jun  4 23:55:05 localhost user.warn kernel: [   10.264107] dummy_rx8130: loading out-of-tree module taints kernel.
Jun  4 23:55:05 localhost daemon.info kernel: [   10.720722] udevd[279]: starting version 3.2.9
Jun  4 23:55:05 localhost daemon.info kernel: [   10.766308] udevd[280]: starting eudev-3.2.9
Jun  4 23:55:05 localhost user.info kernel: [   11.001181] pl011_raw_uart 3f201000.serial: there is not valid maps for state default
Jun  4 23:55:05 localhost user.info kernel: [   11.001510] pl011_raw_uart 3f201000.serial: Detected RPI-RF-MOD, using alternative reset pin
Jun  4 23:55:05 localhost user.info kernel: [   11.182706] pl011_raw_uart 3f201000.serial: Initialized pl011 device; mapbase=0x3f201000; irq=99; clockrate=47999625
Jun  4 23:55:05 localhost user.notice kernel: [   11.275014] cfg80211: Loading compiled-in X.509 certificates for regulatory database
Jun  4 23:55:06 localhost user.notice kernel: [   11.332564] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
Jun  4 23:55:06 localhost user.warn kernel: [   11.336407] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
Jun  4 23:55:06 localhost user.info kernel: [   11.336464] cfg80211: failed to load regulatory.db
Jun  4 23:55:06 localhost user.debug kernel: [   11.385585] brcmfmac: F1 signature read @0x18000000=0x15264345
Jun  4 23:55:06 localhost user.err kernel: [   11.398152] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
Jun  4 23:55:06 localhost user.info kernel: [   11.400004] usbcore: registered new interface driver brcmfmac
Jun  4 23:55:06 localhost user.warn kernel: [   11.432943] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt failed with error -2
Jun  4 23:55:06 localhost daemon.debug /usr/sbin/irqbalance: IRQ 3f00b880.mailbox(2) guessed as class 0
Jun  4 23:55:06 localhost daemon.debug /usr/sbin/irqbalance: IRQ doorbell(3) guessed as class 0
Jun  4 23:55:06 localhost daemon.debug /usr/sbin/irqbalance: IRQ dwc_otg_sim-fiq(51) guessed as class 0
Jun  4 23:55:06 localhost daemon.debug /usr/sbin/irqbalance: IRQ IRQ(60) guessed as class 0
Jun  4 23:55:06 localhost daemon.debug /usr/sbin/irqbalance: IRQ IRQ(62) guessed as class 0
Jun  4 23:55:06 localhost daemon.debug /usr/sbin/irqbalance: IRQ IRQ(63) guessed as class 0
Jun  4 23:55:06 localhost daemon.debug /usr/sbin/irqbalance: IRQ IRQ(66) guessed as class 0
Jun  4 23:55:06 localhost daemon.debug /usr/sbin/irqbalance: IRQ dwc_otg_hcd:usb1(74) guessed as class 0
Jun  4 23:55:06 localhost daemon.debug /usr/sbin/irqbalance: IRQ 3f804000.i2c(95) guessed as class 0
Jun  4 23:55:06 localhost daemon.debug /usr/sbin/irqbalance: IRQ 3f204000.spi(96) guessed as class 0
Jun  4 23:55:06 localhost daemon.debug /usr/sbin/irqbalance: IRQ mmc0(98) guessed as class 0
Jun  4 23:55:06 localhost daemon.debug /usr/sbin/irqbalance: IRQ mmc1(104) guessed as class 0
Jun  4 23:55:06 localhost daemon.debug /usr/sbin/irqbalance: IRQ arch_timer(180) guessed as class 0
Jun  4 23:55:06 localhost daemon.debug /usr/sbin/irqbalance: IRQ arm-pmu(183) guessed as class 0
Jun  4 23:55:06 localhost daemon.debug /usr/sbin/irqbalance: IRQ usb-001:004:01(184) guessed as class 0
Jun  4 23:55:06 localhost user.err kernel: [   11.658780] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
Jun  4 23:55:06 localhost user.err kernel: [   11.675766] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Mar 23 2020 02:19:54 version 7.45.206 (r725000 CY) FWID 01-88ee44ea
Jun  4 23:55:06 localhost user.notice rfkill: block set for type bluetooth
Jun  4 23:55:07 localhost user.crit kernel: [   13.022329] Under-voltage detected! (0x00050005)
Jun  4 23:55:08 localhost syslog.info syslogd exiting
Jun  4 23:55:08 homematic-raspi syslog.info syslogd started: BusyBox v1.33.0
Jun  4 23:55:08 homematic-raspi user.notice kernel: klogd started: BusyBox v1.33.0 (2021-05-25 09:39:24 UTC)
Jun  4 23:55:10 homematic-raspi user.info firewall: configuration set
Jun  4 23:55:11 homematic-raspi user.info kernel: [   16.335899] NET: Registered protocol family 10
Jun  4 23:55:11 homematic-raspi user.info kernel: [   16.343707] Segment Routing with IPv6
Jun  4 23:55:11 homematic-raspi user.notice rfkill: block set for type wlan
Jun  4 23:55:11 homematic-raspi daemon.info ifplugd(eth0)[477]: ifplugd 0.28 initializing.
Jun  4 23:55:11 homematic-raspi daemon.info ifplugd(eth0)[477]: Using interface eth0/B8:27:EB:13:50:4C with driver <lan78xx> (version: 5.10.17)
Jun  4 23:55:11 homematic-raspi daemon.info ifplugd(eth0)[477]: Using detection mode: SIOCETHTOOL
Jun  4 23:55:11 homematic-raspi daemon.info ifplugd(eth0)[477]: Initialization complete, link beat detected.
Jun  4 23:55:11 homematic-raspi daemon.info ifplugd(eth0)[477]: Executing '/etc/ifplugd/ifplugd.action eth0 up'.
Jun  4 23:55:11 homematic-raspi daemon.warn ifplugd(eth0)[477]: client: ifup: interface eth0 already configured
Jun  4 23:55:11 homematic-raspi daemon.info ifplugd(eth0)[477]: Program executed successfully.
Jun  4 23:55:11 homematic-raspi daemon.info ifplugd(wlan0)[482]: ifplugd 0.28 initializing.
Jun  4 23:55:11 homematic-raspi daemon.info ifplugd(wlan0)[482]: Using interface wlan0/B8:27:EB:46:05:19 with driver <brcmfmac> (version: 7.45.206)
Jun  4 23:55:11 homematic-raspi daemon.info ifplugd(wlan0)[482]: Using detection mode: IFF_RUNNING
Jun  4 23:55:11 homematic-raspi daemon.info ifplugd(wlan0)[482]: Initialization complete, link beat not detected.
Jun  4 23:55:22 homematic-raspi daemon.err ntpdate[487]: no server suitable for synchronization found
Jun  4 23:55:34 homematic-raspi daemon.err ntpdate[491]: no server suitable for synchronization found
Jun  4 23:55:34 homematic-raspi user.info kernel: [   39.963108] raw-uart raw-uart: Reset radio module
Jun  4 23:55:39 homematic-raspi daemon.err xinetd[576]: Unable to read included directory: /etc/config/xinetd.d [file=/etc/xinetd.conf] [line=14]
Jun  4 23:55:39 homematic-raspi daemon.crit xinetd[576]: 576 {init_services} no services. Exiting...
Jun  4 23:55:40 homematic-raspi auth.info sshd[611]: Server listening on 0.0.0.0 port 22.
Jun  4 23:55:40 homematic-raspi auth.info sshd[611]: Server listening on :: port 22.
Jun  4 23:55:40 homematic-raspi user.info root: Updating RF Lan Gateway Coprocessor Firmware
Jun  4 23:55:40 homematic-raspi user.debug update-coprocessor: firmware filename is: coprocessor_update_hm_only.eq3
Jun  4 23:55:40 homematic-raspi user.info root: Updating RF Lan Gateway Firmware
Jun  4 23:55:40 homematic-raspi user.info update-lgw-firmware: No gateway found in config file /etc/config/rfd.conf
Jun  4 23:55:40 homematic-raspi user.info kernel: [   46.202389] eq3loop: created slave mmd_hmip
Jun  4 23:55:40 homematic-raspi user.info kernel: [   46.204361] eq3loop: created slave mmd_bidcos
Jun  4 23:55:43 homematic-raspi user.info kernel: [   48.406678] eq3loop: eq3loop_open_slave() mmd_bidcos
Jun  4 23:55:46 homematic-raspi user.info kernel: [   51.326348] Voltage normalised (0x00000000)
Jun  4 23:55:46 homematic-raspi daemon.debug /usr/sbin/irqbalance: IRQ 3f00b880.mailbox(2) guessed as class 0
Jun  4 23:55:46 homematic-raspi daemon.debug /usr/sbin/irqbalance: IRQ doorbell(3) guessed as class 0
Jun  4 23:55:46 homematic-raspi daemon.debug /usr/sbin/irqbalance: IRQ dwc_otg_sim-fiq(51) guessed as class 0
Jun  4 23:55:46 homematic-raspi daemon.debug /usr/sbin/irqbalance: IRQ IRQ(60) guessed as class 0
Jun  4 23:55:46 homematic-raspi daemon.debug /usr/sbin/irqbalance: IRQ IRQ(62) guessed as class 0
Jun  4 23:55:46 homematic-raspi daemon.debug /usr/sbin/irqbalance: IRQ IRQ(63) guessed as class 0
Jun  4 23:55:46 homematic-raspi daemon.debug /usr/sbin/irqbalance: IRQ IRQ(66) guessed as class 0
Jun  4 23:55:46 homematic-raspi daemon.debug /usr/sbin/irqbalance: IRQ dwc_otg_hcd:usb1(74) guessed as class 0
Jun  4 23:55:46 homematic-raspi daemon.debug /usr/sbin/irqbalance: IRQ 3f804000.i2c(95) guessed as class 0
Jun  4 23:55:46 homematic-raspi daemon.debug /usr/sbin/irqbalance: IRQ 3f204000.spi(96) guessed as class 0
Jun  4 23:55:46 homematic-raspi daemon.debug /usr/sbin/irqbalance: IRQ mmc0(98) guessed as class 0
Jun  4 23:55:46 homematic-raspi daemon.debug /usr/sbin/irqbalance: IRQ 3f201000.serial(99) guessed as class 0
Jun  4 23:55:46 homematic-raspi daemon.debug /usr/sbin/irqbalance: IRQ mmc1(104) guessed as class 0
Jun  4 23:55:46 homematic-raspi daemon.debug /usr/sbin/irqbalance: IRQ arch_timer(180) guessed as class 0
Jun  4 23:55:46 homematic-raspi daemon.debug /usr/sbin/irqbalance: IRQ arm-pmu(183) guessed as class 0
Jun  4 23:55:46 homematic-raspi daemon.debug /usr/sbin/irqbalance: IRQ usb-001:004:01(184) guessed as class 0
Jun  4 23:55:50 homematic-raspi user.crit kernel: [   55.358387] Under-voltage detected! (0x00050005)
Jun  4 23:56:09 homematic-raspi user.info kernel: [   74.751811] eq3loop: eq3loop_open_slave() mmd_hmip
Jun  4 23:56:09 homematic-raspi user.info kernel: [   74.752391] eq3loop: eq3loop_close_slave() mmd_hmip
Jun  4 23:56:09 homematic-raspi user.info kernel: [   74.774107] eq3loop: eq3loop_open_slave() mmd_hmip
Jun  4 21:56:27 homematic-raspi daemon.info : starting pid 992, tty '/dev/null': '/usr/bin/monit -Ic /etc/monitrc'
Jun  4 23:56:27 homematic-raspi user.info monit[992]: Starting Monit 5.27.2 daemon with http interface at /var/run/monit.sock
Jun  4 23:56:27 homematic-raspi user.info monit[992]: 'homematic-raspi' Monit 5.27.2 started
Jun  4 23:56:28 homematic-raspi user.err monit[992]: 'chronyd' process is not running
Jun  4 23:56:28 homematic-raspi user.info monit[992]: 'chronyd' trying to restart
Jun  4 23:56:28 homematic-raspi user.info monit[992]: 'chronyd' restart: '/etc/init.d/S46chrony restart'
Jun  4 23:56:32 homematic-raspi user.info kernel: [   97.694336] Voltage normalised (0x00000000)
Jun  4 23:56:32 homematic-raspi local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"001F5A499403CB:0","CARRIER_SENSE_LEVEL"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: CARRIER_SENSE_LEVEL"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Jun  4 23:56:32 homematic-raspi local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1038, params: {"001F5A499403CB:0","CARRIER_SENSE_LEVEL"}) [CallGetValue():iseXmlRpc.cpp:1435]
Jun  4 23:56:32 homematic-raspi local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0.000000 [ReadValue():iseDOMdpHSS.cpp:124]
Jun  4 23:56:32 homematic-raspi local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"001F5A499403CB:0","DUTY_CYCLE_LEVEL"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: DUTY_CYCLE_LEVEL"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Jun  4 23:56:32 homematic-raspi local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1038, params: {"001F5A499403CB:0","DUTY_CYCLE_LEVEL"}) [CallGetValue():iseXmlRpc.cpp:1435]
Jun  4 23:56:32 homematic-raspi local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0.000000 [ReadValue():iseDOMdpHSS.cpp:124]
Jun  4 23:56:32 homematic-raspi local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"001F5A499403CB:0","INCLUSION_UNSUPPORTED_DEVICE"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: INCLUSION_UNSUPPORTED_DEVICE"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Jun  4 23:56:32 homematic-raspi local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1038, params: {"001F5A499403CB:0","INCLUSION_UNSUPPORTED_DEVICE"}) [CallGetValue():iseXmlRpc.cpp:1435]
Jun  4 23:56:32 homematic-raspi local0.err ReGaHss: ERROR: CallGetValue failed; sVal =  [ReadValue():iseDOMdpHSS.cpp:124]
Jun  4 23:56:34 homematic-raspi user.crit kernel: [   99.710382] Under-voltage detected! (0x00050000)
Jun  4 23:56:36 homematic-raspi user.info kernel: [  101.726369] Voltage normalised (0x00000000)
Jun  4 23:56:40 homematic-raspi daemon.err ntpdate[1008]: no server suitable for synchronization found
Jun  4 23:56:51 homematic-raspi daemon.err ntpdate[1027]: no server suitable for synchronization found
Jun  4 23:56:58 homematic-raspi user.err monit[992]: 'chronyd' failed to restart (exit status 0) -- '/etc/init.d/S46chrony restart': Stopping chrony: FAIL Starting chrony: using default NTPs, could not sync to '0.de.pool.ntp.org 1.de.pool.ntp.org 2.de.pool.ntp.org 3.de.pool.ntp.org', FAIL
Jun  4 23:57:12 homematic-raspi user.err monit[992]: 'chronyd' service restarted 1 times within 1 cycles(s) - exec
Jun  4 23:57:12 homematic-raspi user.info monit[992]: 'chronyd' exec: '/bin/triggerAlarm.tcl Chrony-NTP restarted WatchDog-Alarm'
Jun  4 23:57:12 homematic-raspi user.err monit[992]: 'chronyd' process is not running
Jun  4 23:57:12 homematic-raspi user.info monit[992]: 'chronyd' trying to restart
Jun  4 23:57:12 homematic-raspi user.info monit[992]: 'chronyd' restart: '/etc/init.d/S46chrony restart'
Jun  4 23:57:25 homematic-raspi daemon.err ntpdate[1086]: no server suitable for synchronization found
Jun  4 23:57:36 homematic-raspi daemon.err ntpdate[1093]: no server suitable for synchronization found
Jun  4 23:57:43 homematic-raspi user.err monit[992]: 'chronyd' failed to restart (exit status 0) -- '/etc/init.d/S46chrony restart': Stopping chrony: FAIL Starting chrony: using default NTPs, could not sync to '0.de.pool.ntp.org 1.de.pool.ntp.org 2.de.pool.ntp.org 3.de.pool.ntp.org', FAIL
Jun  4 23:57:44 homematic-raspi user.err monit[992]: 'hs485dEnabled' status failed (2) -- grep: /var/etc/hs485d.conf: No such file or directory
Jun  4 23:57:44 homematic-raspi user.err monit[992]: 'hmlangwEnabled' status failed (1) -- no output
Jun  4 23:57:45 homematic-raspi user.warn monit[992]: 'hasUSB' status failed (1) -- no output
Jun  4 23:57:45 homematic-raspi user.err monit[992]: 'hb_rf_eth-CheckEnabled' status failed (1) -- no output
Jun  4 23:57:45 homematic-raspi user.warn monit[992]: 'eMMCLifeTimeCheck' status failed (1) -- no output
Jun  4 23:57:46 homematic-raspi user.err monit[992]: Lookup for '/media/usb1' filesystem failed  -- not found in /proc/self/mounts
Jun  4 23:57:46 homematic-raspi user.err monit[992]: Filesystem '/media/usb1' not mounted
Jun  4 23:57:46 homematic-raspi user.err monit[992]: 'usb1' unable to read filesystem '/media/usb1' state
Jun  4 23:57:46 homematic-raspi user.info monit[992]: 'usb1' trying to restart
Jun  4 23:57:59 homematic-raspi user.err monit[992]: 'chronyd' process is not running
Jun  4 23:57:59 homematic-raspi user.info monit[992]: 'chronyd' trying to restart
Jun  4 23:57:59 homematic-raspi user.info monit[992]: 'chronyd' restart: '/etc/init.d/S46chrony restart'
Jun  4 23:58:11 homematic-raspi daemon.err ntpdate[1155]: no server suitable for synchronization found
Jun  4 23:58:23 homematic-raspi daemon.err ntpdate[1164]: no server suitable for synchronization found
Jun  4 23:58:29 homematic-raspi user.err monit[992]: 'chronyd' failed to restart (exit status 0) -- '/etc/init.d/S46chrony restart': Stopping chrony: FAIL Starting chrony: using default NTPs, could not sync to '0.de.pool.ntp.org 1.de.pool.ntp.org 2.de.pool.ntp.org 3.de.pool.ntp.org', FAIL
Jun  4 23:58:31 homematic-raspi user.warn monit[992]: 'hasUSB' status failed (1) -- no output
Jun  4 23:58:31 homematic-raspi user.err monit[992]: 'wlan0CheckEnabled' status failed (1) -- no output
Jun  4 23:58:32 homematic-raspi user.warn monit[992]: 'eMMCLifeTimeCheck' status failed (1) -- no output
Jun  4 23:58:32 homematic-raspi user.err monit[992]: Filesystem '/media/usb1' not mounted
Jun  4 23:58:32 homematic-raspi user.err monit[992]: 'usb1' unable to read filesystem '/media/usb1' state
Jun  4 23:58:32 homematic-raspi user.info monit[992]: 'usb1' trying to restart
Jun  4 23:58:45 homematic-raspi user.err monit[992]: 'chronyd' service restarted 1 times within 1 cycles(s) - exec
Jun  4 23:58:45 homematic-raspi user.err monit[992]: 'chronyd' process is not running
Jun  4 23:58:45 homematic-raspi user.info monit[992]: 'chronyd' trying to restart
Jun  4 23:58:45 homematic-raspi user.info monit[992]: 'chronyd' restart: '/etc/init.d/S46chrony restart'
Jun  4 23:58:57 homematic-raspi daemon.err ntpdate[1225]: no server suitable for synchronization found
Jun  4 23:59:08 homematic-raspi daemon.err ntpdate[1232]: no server suitable for synchronization found
Jun  4 23:59:15 homematic-raspi user.err monit[992]: 'chronyd' failed to restart (exit status 0) -- '/etc/init.d/S46chrony restart': Stopping chrony: FAIL Starting chrony: using default NTPs, could not sync to '0.de.pool.ntp.org 1.de.pool.ntp.org 2.de.pool.ntp.org 3.de.pool.ntp.org', FAIL
Jun  4 23:59:18 homematic-raspi user.warn monit[992]: 'hasUSB' status failed (1) -- no output
Jun  4 23:59:18 homematic-raspi user.err monit[992]: 'eMMCLifeTimeCheck' status failed (1) -- no output
Jun  4 23:59:18 homematic-raspi user.err monit[992]: Filesystem '/media/usb1' not mounted
Jun  4 23:59:18 homematic-raspi user.err monit[992]: 'usb1' unable to read filesystem '/media/usb1' state
Jun  4 23:59:18 homematic-raspi user.info monit[992]: 'usb1' trying to restart
Jun  4 23:59:31 homematic-raspi user.err monit[992]: 'chronyd' process is not running
Jun  4 23:59:31 homematic-raspi user.info monit[992]: 'chronyd' trying to restart
Jun  4 23:59:31 homematic-raspi user.info monit[992]: 'chronyd' restart: '/etc/init.d/S46chrony restart'
Jun  4 23:59:43 homematic-raspi daemon.err ntpdate[1290]: no server suitable for synchronization found
Jun  4 23:59:54 homematic-raspi daemon.err ntpdate[1299]: no server suitable for synchronization found
Jun  5 00:00:01 homematic-raspi user.err monit[992]: 'chronyd' failed to restart (exit status 0) -- '/etc/init.d/S46chrony restart': Stopping chrony: FAIL Starting chrony: using default NTPs, could not sync to '0.de.pool.ntp.org 1.de.pool.ntp.org 2.de.pool.ntp.org 3.de.pool.ntp.org', FAIL
Jun  5 00:00:04 homematic-raspi user.warn monit[992]: 'hasUSB' status failed (1) -- no output
Jun  5 00:00:04 homematic-raspi user.err monit[992]: Filesystem '/media/usb1' not mounted
Jun  5 00:00:04 homematic-raspi user.err monit[992]: 'usb1' unable to read filesystem '/media/usb1' state
Jun  5 00:00:04 homematic-raspi user.info monit[992]: 'usb1' trying to restart
Jun  5 00:00:17 homematic-raspi user.err monit[992]: 'chronyd' service restarted 1 times within 1 cycles(s) - exec
Jun  5 00:00:17 homematic-raspi user.err monit[992]: 'chronyd' process is not running
Jun  5 00:00:17 homematic-raspi user.info monit[992]: 'chronyd' trying to restart
Jun  5 00:00:17 homematic-raspi user.info monit[992]: 'chronyd' restart: '/etc/init.d/S46chrony restart'
Jun  5 00:00:18 homematic-raspi user.warn kernel: [  323.486342] rpi_firmware_get_throttled: 4 callbacks suppressed
Jun  5 00:00:18 homematic-raspi user.crit kernel: [  323.486356] Under-voltage detected! (0x00050005)
Jun  5 00:00:30 homematic-raspi daemon.err ntpdate[1356]: no server suitable for synchronization found
Jun  5 00:00:41 homematic-raspi daemon.err ntpdate[1364]: no server suitable for synchronization found
Jun  5 00:00:47 homematic-raspi user.err monit[992]: 'chronyd' failed to restart (exit status 0) -- '/etc/init.d/S46chrony restart': Stopping chrony: FAIL Starting chrony: using default NTPs, could not sync to '0.de.pool.ntp.org 1.de.pool.ntp.org 2.de.pool.ntp.org 3.de.pool.ntp.org', FAIL
Jun  5 00:00:49 homematic-raspi user.err monit[992]: 'hasUSB' status failed (1) -- no output
Jun  5 00:01:03 homematic-raspi user.err monit[992]: 'chronyd' process is not running
Jun  5 00:01:03 homematic-raspi user.info monit[992]: 'chronyd' trying to restart
Jun  5 00:01:03 homematic-raspi user.info monit[992]: 'chronyd' restart: '/etc/init.d/S46chrony restart'
Jun  5 00:01:10 homematic-raspi user.crit kernel: [  375.902369] Under-voltage detected! (0x00050005)
Jun  5 00:01:14 homematic-raspi user.warn kernel: [  379.934346] rpi_firmware_get_throttled: 5 callbacks suppressed
Jun  5 00:01:14 homematic-raspi user.info kernel: [  379.934360] Voltage normalised (0x00000000)
Jun  5 00:01:15 homematic-raspi daemon.err ntpdate[1418]: no server suitable for synchronization found
Jun  5 00:01:26 homematic-raspi daemon.err ntpdate[1428]: no server suitable for synchronization found
Jun  5 00:01:33 homematic-raspi user.err monit[992]: 'chronyd' failed to restart (exit status 0) -- '/etc/init.d/S46chrony restart': Stopping chrony: FAIL Starting chrony: using default NTPs, could not sync to '0.de.pool.ntp.org 1.de.pool.ntp.org 2.de.pool.ntp.org 3.de.pool.ntp.org', FAIL
Jun  5 00:01:49 homematic-raspi user.err monit[992]: 'chronyd' service restarted 1 times within 1 cycles(s) - exec
Jun  5 00:01:49 homematic-raspi user.err monit[992]: 'chronyd' process is not running
Jun  5 00:01:49 homematic-raspi user.info monit[992]: 'chronyd' trying to restart
Jun  5 00:01:49 homematic-raspi user.info monit[992]: 'chronyd' restart: '/etc/init.d/S46chrony restart'
Jun  5 00:02:01 homematic-raspi daemon.err ntpdate[1483]: no server suitable for synchronization found
Jun  5 00:02:12 homematic-raspi daemon.err ntpdate[1491]: no server suitable for synchronization found
Jun  5 00:02:19 homematic-raspi user.err monit[992]: 'chronyd' failed to restart (exit status 0) -- '/etc/init.d/S46chrony restart': Stopping chrony: FAIL Starting chrony: using default NTPs, could not sync to '0.de.pool.ntp.org 1.de.pool.ntp.org 2.de.pool.ntp.org 3.de.pool.ntp.org', FAIL
Jun  5 00:02:35 homematic-raspi user.err monit[992]: 'chronyd' process is not running
Jun  5 00:02:35 homematic-raspi user.info monit[992]: 'chronyd' trying to restart
Jun  5 00:02:35 homematic-raspi user.info monit[992]: 'chronyd' restart: '/etc/init.d/S46chrony restart'
Jun  5 00:02:47 homematic-raspi daemon.err ntpdate[1544]: no server suitable for synchronization found
Jun  5 00:02:59 homematic-raspi daemon.err ntpdate[1553]: no server suitable for synchronization found
Jun  5 00:03:05 homematic-raspi user.err monit[992]: 'chronyd' failed to restart (exit status 0) -- '/etc/init.d/S46chrony restart': Stopping chrony: FAIL Starting chrony: using default NTPs, could not sync to '0.de.pool.ntp.org 1.de.pool.ntp.org 2.de.pool.ntp.org 3.de.pool.ntp.org', FAIL
Jun  5 00:03:09 homematic-raspi user.crit kernel: [  494.846361] Under-voltage detected! (0x00050005)
Jun  5 00:03:11 homematic-raspi user.info kernel: [  496.862373] Voltage normalised (0x00000000)
Jun  5 00:03:20 homematic-raspi user.err monit[992]: 'chronyd' service restarted 1 times within 1 cycles(s) - exec
Jun  5 00:03:20 homematic-raspi user.err monit[992]: 'chronyd' process is not running
Jun  5 00:03:20 homematic-raspi user.info monit[992]: 'chronyd' trying to restart
Jun  5 00:03:20 homematic-raspi user.info monit[992]: 'chronyd' restart: '/etc/init.d/S46chrony restart'
Jun  5 00:03:33 homematic-raspi daemon.err ntpdate[1606]: no server suitable for synchronization found
Jun  5 00:03:44 homematic-raspi daemon.err ntpdate[1614]: no server suitable for synchronization found
Jun  5 00:03:51 homematic-raspi user.err monit[992]: 'chronyd' failed to restart (exit status 0) -- '/etc/init.d/S46chrony restart': Stopping chrony: FAIL Starting chrony: using default NTPs, could not sync to '0.de.pool.ntp.org 1.de.pool.ntp.org 2.de.pool.ntp.org 3.de.pool.ntp.org', FAIL
Jun  5 00:04:06 homematic-raspi user.err monit[992]: 'chronyd' process is not running
Jun  5 00:04:06 homematic-raspi user.info monit[992]: 'chronyd' trying to restart
Jun  5 00:04:06 homematic-raspi user.info monit[992]: 'chronyd' restart: '/etc/init.d/S46chrony restart'
Jun  5 00:04:19 homematic-raspi daemon.err ntpdate[1671]: no server suitable for synchronization found
Jun  5 00:04:30 homematic-raspi daemon.err ntpdate[1679]: no server suitable for synchronization found
Jun  5 00:04:37 homematic-raspi user.err monit[992]: 'chronyd' failed to restart (exit status 0) -- '/etc/init.d/S46chrony restart': Stopping chrony: FAIL Starting chrony: using default NTPs, could not sync to '0.de.pool.ntp.org 1.de.pool.ntp.org 2.de.pool.ntp.org 3.de.pool.ntp.org', FAIL
Jun  5 00:04:53 homematic-raspi user.err monit[992]: 'chronyd' service restarted 1 times within 1 cycles(s) - exec
Jun  5 00:04:53 homematic-raspi user.err monit[992]: 'chronyd' process is not running
Jun  5 00:04:53 homematic-raspi user.info monit[992]: 'chronyd' trying to restart
Jun  5 00:04:53 homematic-raspi user.info monit[992]: 'chronyd' restart: '/etc/init.d/S46chrony restart'
Jun  5 00:05:05 homematic-raspi daemon.err ntpdate[1732]: no server suitable for synchronization found
Jun  5 00:05:16 homematic-raspi daemon.err ntpdate[1741]: no server suitable for synchronization found
Jun  5 00:05:24 homematic-raspi user.err monit[992]: 'chronyd' failed to restart (exit status 0) -- '/etc/init.d/S46chrony restart': Stopping chrony: FAIL Starting chrony: using default NTPs, could not sync to '0.de.pool.ntp.org 1.de.pool.ntp.org 2.de.pool.ntp.org 3.de.pool.ntp.org', FAIL
Jun  5 00:05:39 homematic-raspi user.err monit[992]: 'chronyd' process is not running
Jun  5 00:05:39 homematic-raspi user.info monit[992]: 'chronyd' trying to restart
Jun  5 00:05:39 homematic-raspi user.info monit[992]: 'chronyd' restart: '/etc/init.d/S46chrony restart'
Jun  5 00:05:51 homematic-raspi daemon.err ntpdate[1795]: no server suitable for synchronization found
Jun  5 00:06:02 homematic-raspi daemon.err ntpdate[1802]: no server suitable for synchronization found
Jun  5 00:06:10 homematic-raspi user.err monit[992]: 'chronyd' failed to restart (exit status 0) -- '/etc/init.d/S46chrony restart': Stopping chrony: FAIL Starting chrony: using default NTPs, could not sync to '0.de.pool.ntp.org 1.de.pool.ntp.org 2.de.pool.ntp.org 3.de.pool.ntp.org', FAIL
Jun  5 00:06:10 homematic-raspi user.crit kernel: [  676.286556] Under-voltage detected! (0x00050005)
Jun  5 00:06:15 homematic-raspi user.info kernel: [  680.318369] Voltage normalised (0x00000000)
Jun  5 00:06:25 homematic-raspi user.err monit[992]: 'chronyd' service restarted 1 times within 1 cycles(s) - exec
Jun  5 00:06:25 homematic-raspi user.err monit[992]: 'chronyd' process is not running
Jun  5 00:06:25 homematic-raspi user.info monit[992]: 'chronyd' trying to restart
Jun  5 00:06:25 homematic-raspi user.info monit[992]: 'chronyd' restart: '/etc/init.d/S46chrony restart'
Jun  5 00:06:37 homematic-raspi daemon.err ntpdate[1857]: no server suitable for synchronization found
Jun  5 00:06:49 homematic-raspi daemon.err ntpdate[1865]: no server suitable for synchronization found
Jun  5 00:06:56 homematic-raspi user.err monit[992]: 'chronyd' failed to restart (exit status 0) -- '/etc/init.d/S46chrony restart': Stopping chrony: FAIL Starting chrony: using default NTPs, could not sync to '0.de.pool.ntp.org 1.de.pool.ntp.org 2.de.pool.ntp.org 3.de.pool.ntp.org', FAIL
Jun  5 00:06:59 homematic-raspi user.crit kernel: [  724.670384] Under-voltage detected! (0x00050005)
Jun  5 00:07:03 homematic-raspi user.info kernel: [  728.702379] Voltage normalised (0x00000000)
Jun  5 00:07:11 homematic-raspi user.err monit[992]: 'chronyd' process is not running
Jun  5 00:07:11 homematic-raspi user.info monit[992]: 'chronyd' trying to restart
Jun  5 00:07:11 homematic-raspi user.info monit[992]: 'chronyd' restart: '/etc/init.d/S46chrony restart'
Jun  5 00:07:24 homematic-raspi daemon.err ntpdate[1922]: no server suitable for synchronization found
Jun  5 00:07:35 homematic-raspi daemon.err ntpdate[1929]: no server suitable for synchronization found
Jun  5 00:07:42 homematic-raspi user.err monit[992]: 'chronyd' failed to restart (exit status 0) -- '/etc/init.d/S46chrony restart': Stopping chrony: FAIL Starting chrony: using default NTPs, could not sync to '0.de.pool.ntp.org 1.de.pool.ntp.org 2.de.pool.ntp.org 3.de.pool.ntp.org', FAIL
Jun  5 00:07:43 homematic-raspi user.crit kernel: [  769.022360] Under-voltage detected! (0x00050005)
Jun  5 00:07:47 homematic-raspi user.info kernel: [  773.054374] Voltage normalised (0x00000000)
Jun  5 00:07:58 homematic-raspi user.err monit[992]: 'chronyd' service restarted 1 times within 1 cycles(s) - exec
Jun  5 00:07:58 homematic-raspi user.err monit[992]: 'chronyd' process is not running
Jun  5 00:07:58 homematic-raspi user.info monit[992]: 'chronyd' trying to restart
Jun  5 00:07:58 homematic-raspi user.info monit[992]: 'chronyd' restart: '/etc/init.d/S46chrony restart'
Jun  5 00:08:10 homematic-raspi daemon.err ntpdate[1984]: no server suitable for synchronization found
Jun  5 00:08:21 homematic-raspi daemon.err ntpdate[1993]: no server suitable for synchronization found
Jun  5 00:08:29 homematic-raspi user.err monit[992]: 'chronyd' failed to restart (exit status 0) -- '/etc/init.d/S46chrony restart': Stopping chrony: FAIL Starting chrony: using default NTPs, could not sync to '0.de.pool.ntp.org 1.de.pool.ntp.org 2.de.pool.ntp.org 3.de.pool.ntp.org', FAIL
Jun  5 00:08:44 homematic-raspi user.err monit[992]: 'chronyd' process is not running
Jun  5 00:08:44 homematic-raspi user.info monit[992]: 'chronyd' trying to restart
Jun  5 00:08:44 homematic-raspi user.info monit[992]: 'chronyd' restart: '/etc/init.d/S46chrony restart'
Jun  5 00:08:56 homematic-raspi daemon.err ntpdate[2047]: no server suitable for synchronization found
Jun  5 00:09:07 homematic-raspi daemon.err ntpdate[2054]: no server suitable for synchronization found
Jun  5 00:09:15 homematic-raspi user.err monit[992]: 'chronyd' failed to restart (exit status 0) -- '/etc/init.d/S46chrony restart': Stopping chrony: FAIL Starting chrony: using default NTPs, could not sync to '0.de.pool.ntp.org 1.de.pool.ntp.org 2.de.pool.ntp.org 3.de.pool.ntp.org', FAIL
Jun  5 00:09:30 homematic-raspi user.err monit[992]: 'chronyd' service restarted 1 times within 1 cycles(s) - exec
Jun  5 00:09:30 homematic-raspi user.err monit[992]: 'chronyd' process is not running
Jun  5 00:09:30 homematic-raspi user.info monit[992]: 'chronyd' trying to restart
Jun  5 00:09:30 homematic-raspi user.info monit[992]: 'chronyd' restart: '/etc/init.d/S46chrony restart'
Jun  5 00:09:43 homematic-raspi daemon.err ntpdate[2107]: no server suitable for synchronization found
Jun  5 00:09:54 homematic-raspi daemon.err ntpdate[2116]: no server suitable for synchronization found
Jun  5 00:10:01 homematic-raspi user.err monit[992]: 'chronyd' failed to restart (exit status 0) -- '/etc/init.d/S46chrony restart': Stopping chrony: FAIL Starting chrony: using default NTPs, could not sync to '0.de.pool.ntp.org 1.de.pool.ntp.org 2.de.pool.ntp.org 3.de.pool.ntp.org', FAIL
Jun  5 00:10:17 homematic-raspi user.err monit[992]: 'chronyd' process is not running
Jun  5 00:10:17 homematic-raspi user.info monit[992]: 'chronyd' trying to restart
Jun  5 00:10:17 homematic-raspi user.info monit[992]: 'chronyd' restart: '/etc/init.d/S46chrony restart'
Jun  5 00:10:29 homematic-raspi daemon.err ntpdate[2173]: no server suitable for synchronization found
Jun  5 00:10:40 homematic-raspi daemon.err ntpdate[2180]: no server suitable for synchronization found
Jun  5 00:10:47 homematic-raspi user.err monit[992]: 'chronyd' failed to restart (exit status 0) -- '/etc/init.d/S46chrony restart': Stopping chrony: FAIL Starting chrony: using default NTPs, could not sync to '0.de.pool.ntp.org 1.de.pool.ntp.org 2.de.pool.ntp.org 3.de.pool.ntp.org', FAIL
Jun  5 00:10:50 homematic-raspi user.warn monit[992]: 'voltageCheck' status failed (0) -- no output
Jun  5 00:11:03 homematic-raspi user.err monit[992]: 'chronyd' service restarted 1 times within 1 cycles(s) - exec
Jun  5 00:11:03 homematic-raspi user.err monit[992]: 'chronyd' process is not running
Jun  5 00:11:03 homematic-raspi user.info monit[992]: 'chronyd' trying to restart
Jun  5 00:11:03 homematic-raspi user.info monit[992]: 'chronyd' restart: '/etc/init.d/S46chrony restart'
Jun  5 00:11:11 homematic-raspi user.warn kernel: [  976.670358] rpi_firmware_get_throttled: 2 callbacks suppressed
Jun  5 00:11:11 homematic-raspi user.crit kernel: [  976.670373] Under-voltage detected! (0x00050005)
Jun  5 00:11:15 homematic-raspi user.warn kernel: [  980.702368] rpi_firmware_get_throttled: 2 callbacks suppressed
Jun  5 00:11:15 homematic-raspi user.info kernel: [  980.702383] Voltage normalised (0x00000000)
Jun  5 00:11:15 homematic-raspi daemon.err ntpdate[2235]: no server suitable for synchronization found
Jun  5 00:11:26 homematic-raspi daemon.err ntpdate[2243]: no server suitable for synchronization found
Jun  5 00:11:33 homematic-raspi user.err monit[992]: 'chronyd' failed to restart (exit status 0) -- '/etc/init.d/S46chrony restart': Stopping chrony: FAIL Starting chrony: using default NTPs, could not sync to '0.de.pool.ntp.org 1.de.pool.ntp.org 2.de.pool.ntp.org 3.de.pool.ntp.org', FAIL
Jun  5 00:11:49 homematic-raspi user.err monit[992]: 'chronyd' process is not running
Jun  5 00:11:49 homematic-raspi user.info monit[992]: 'chronyd' trying to restart
Jun  5 00:11:49 homematic-raspi user.info monit[992]: 'chronyd' restart: '/etc/init.d/S46chrony restart'
Jun  5 00:11:49 homematic-raspi user.crit kernel: [ 1014.974382] Under-voltage detected! (0x00050005)
Jun  5 00:11:53 homematic-raspi user.info kernel: [ 1019.006367] Voltage normalised (0x00000000)
Jun  5 00:12:01 homematic-raspi daemon.err ntpdate[2297]: no server suitable for synchronization found
Jun  5 00:12:13 homematic-raspi daemon.err ntpdate[2307]: no server suitable for synchronization found
Jun  5 00:12:19 homematic-raspi user.err monit[992]: 'chronyd' failed to restart (exit status 0) -- '/etc/init.d/S46chrony restart': Stopping chrony: FAIL Starting chrony: using default NTPs, could not sync to '0.de.pool.ntp.org 1.de.pool.ntp.org 2.de.pool.ntp.org 3.de.pool.ntp.org', FAIL
Jun  5 00:12:35 homematic-raspi user.err monit[992]: 'chronyd' service restarted 1 times within 1 cycles(s) - exec
Jun  5 00:12:35 homematic-raspi user.err monit[992]: 'chronyd' process is not running
Jun  5 00:12:35 homematic-raspi user.info monit[992]: 'chronyd' trying to restart
Jun  5 00:12:35 homematic-raspi user.info monit[992]: 'chronyd' restart: '/etc/init.d/S46chrony restart'
Jun  5 00:12:47 homematic-raspi daemon.err ntpdate[2360]: no server suitable for synchronization found
Jun  5 00:12:58 homematic-raspi daemon.err ntpdate[2368]: no server suitable for synchronization found
Jun  5 00:13:05 homematic-raspi user.err monit[992]: 'chronyd' failed to restart (exit status 0) -- '/etc/init.d/S46chrony restart': Stopping chrony: FAIL Starting chrony: using default NTPs, could not sync to '0.de.pool.ntp.org 1.de.pool.ntp.org 2.de.pool.ntp.org 3.de.pool.ntp.org', FAIL
Jun  5 00:13:21 homematic-raspi user.err monit[992]: 'chronyd' process is not running
Jun  5 00:13:21 homematic-raspi user.info monit[992]: 'chronyd' trying to restart
Jun  5 00:13:21 homematic-raspi user.info monit[992]: 'chronyd' restart: '/etc/init.d/S46chrony restart'
Jun  5 00:13:33 homematic-raspi daemon.err ntpdate[2423]: no server suitable for synchronization found
Jun  5 00:13:44 homematic-raspi daemon.err ntpdate[2432]: no server suitable for synchronization found
Jun  5 00:13:51 homematic-raspi user.err monit[992]: 'chronyd' failed to restart (exit status 0) -- '/etc/init.d/S46chrony restart': Stopping chrony: FAIL Starting chrony: using default NTPs, could not sync to '0.de.pool.ntp.org 1.de.pool.ntp.org 2.de.pool.ntp.org 3.de.pool.ntp.org', FAIL
Jun  5 00:14:07 homematic-raspi user.err monit[992]: 'chronyd' service restarted 1 times within 1 cycles(s) - exec
Jun  5 00:14:07 homematic-raspi user.err monit[992]: 'chronyd' process is not running
Jun  5 00:14:07 homematic-raspi user.info monit[992]: 'chronyd' trying to restart
Jun  5 00:14:07 homematic-raspi user.info monit[992]: 'chronyd' restart: '/etc/init.d/S46chrony restart'
Jun  5 00:14:20 homematic-raspi daemon.err ntpdate[2485]: no server suitable for synchronization found
Jun  5 00:14:31 homematic-raspi daemon.err ntpdate[2495]: no server suitable for synchronization found
Jun  5 00:14:37 homematic-raspi user.err monit[992]: 'chronyd' failed to restart (exit status 0) -- '/etc/init.d/S46chrony restart': Stopping chrony: FAIL Starting chrony: using default NTPs, could not sync to '0.de.pool.ntp.org 1.de.pool.ntp.org 2.de.pool.ntp.org 3.de.pool.ntp.org', FAIL
Jun  5 00:14:41 homematic-raspi user.crit kernel: [ 1186.334372] Under-voltage detected! (0x00050005)
Jun  5 00:14:45 homematic-raspi user.info kernel: [ 1190.366337] Voltage normalised (0x00000000)
Jun  5 00:14:53 homematic-raspi user.err monit[992]: 'chronyd' process is not running
Jun  5 00:14:53 homematic-raspi user.info monit[992]: 'chronyd' trying to restart
Jun  5 00:14:53 homematic-raspi user.info monit[992]: 'chronyd' restart: '/etc/init.d/S46chrony restart'
Jun  5 00:15:05 homematic-raspi daemon.err ntpdate[2547]: no server suitable for synchronization found
Jun  5 00:15:16 homematic-raspi daemon.err ntpdate[2556]: no server suitable for synchronization found
Jun  5 00:15:23 homematic-raspi user.err monit[992]: 'chronyd' failed to restart (exit status 0) -- '/etc/init.d/S46chrony restart': Stopping chrony: FAIL Starting chrony: using default NTPs, could not sync to '0.de.pool.ntp.org 1.de.pool.ntp.org 2.de.pool.ntp.org 3.de.pool.ntp.org', FAIL
Jun  5 00:15:39 homematic-raspi user.err monit[992]: 'chronyd' service restarted 1 times within 1 cycles(s) - exec
Jun  5 00:15:39 homematic-raspi user.err monit[992]: 'chronyd' process is not running
Jun  5 00:15:39 homematic-raspi user.info monit[992]: 'chronyd' trying to restart
Jun  5 00:15:39 homematic-raspi user.info monit[992]: 'chronyd' restart: '/etc/init.d/S46chrony restart'
Jun  5 00:15:51 homematic-raspi daemon.err ntpdate[2608]: no server suitable for synchronization found
Jun  5 00:16:02 homematic-raspi daemon.err ntpdate[2616]: no server suitable for synchronization found
Jun  5 00:16:09 homematic-raspi user.err monit[992]: 'chronyd' failed to restart (exit status 0) -- '/etc/init.d/S46chrony restart': Stopping chrony: FAIL Starting chrony: using default NTPs, could not sync to '0.de.pool.ntp.org 1.de.pool.ntp.org 2.de.pool.ntp.org 3.de.pool.ntp.org', FAIL
Jun  5 00:16:11 homematic-raspi user.crit kernel: [ 1277.054382] Under-voltage detected! (0x00050005)
Jun  5 00:16:25 homematic-raspi user.err monit[992]: 'chronyd' process is not running
Jun  5 00:16:25 homematic-raspi user.info monit[992]: 'chronyd' trying to restart
Jun  5 00:16:25 homematic-raspi user.info monit[992]: 'chronyd' restart: '/etc/init.d/S46chrony restart'
Jun  5 00:16:38 homematic-raspi daemon.err ntpdate[2672]: no server suitable for synchronization found
Jun  5 00:16:49 homematic-raspi daemon.err ntpdate[2680]: no server suitable for synchronization found
Jun  5 00:16:55 homematic-raspi user.err monit[992]: 'chronyd' failed to restart (exit status 0) -- '/etc/init.d/S46chrony restart': Stopping chrony: FAIL Starting chrony: using default NTPs, could not sync to '0.de.pool.ntp.org 1.de.pool.ntp.org 2.de.pool.ntp.org 3.de.pool.ntp.org', FAIL
Jun  5 00:17:11 homematic-raspi user.err monit[992]: 'chronyd' service restarted 1 times within 1 cycles(s) - exec
Jun  5 00:17:11 homematic-raspi user.err monit[992]: 'chronyd' process is not running
Jun  5 00:17:11 homematic-raspi user.info monit[992]: 'chronyd' trying to restart
Jun  5 00:17:11 homematic-raspi user.info monit[992]: 'chronyd' restart: '/etc/init.d/S46chrony restart'
Jun  5 00:17:23 homematic-raspi daemon.err ntpdate[2734]: no server suitable for synchronization found
Jun  5 00:17:34 homematic-raspi daemon.err ntpdate[2742]: no server suitable for synchronization found
Jun  5 00:17:42 homematic-raspi user.err monit[992]: 'chronyd' failed to restart (exit status 0) -- '/etc/init.d/S46chrony restart': Stopping chrony: FAIL Starting chrony: using default NTPs, could not sync to '0.de.pool.ntp.org 1.de.pool.ntp.org 2.de.pool.ntp.org 3.de.pool.ntp.org', FAIL
Jun  5 00:17:57 homematic-raspi user.err monit[992]: 'chronyd' process is not running
Jun  5 00:17:57 homematic-raspi user.info monit[992]: 'chronyd' trying to restart
Jun  5 00:17:57 homematic-raspi user.info monit[992]: 'chronyd' restart: '/etc/init.d/S46chrony restart'
Jun  5 00:18:09 homematic-raspi daemon.err ntpdate[2797]: no server suitable for synchronization found
Jun  5 00:18:21 homematic-raspi daemon.err ntpdate[2805]: no server suitable for synchronization found
Jun  5 00:18:22 homematic-raspi user.crit kernel: [ 1408.094362] Under-voltage detected! (0x00050005)
Jun  5 00:18:28 homematic-raspi user.err monit[992]: 'chronyd' failed to restart (exit status 0) -- '/etc/init.d/S46chrony restart': Stopping chrony: FAIL Starting chrony: using default NTPs, could not sync to '0.de.pool.ntp.org 1.de.pool.ntp.org 2.de.pool.ntp.org 3.de.pool.ntp.org', FAIL
Jun  5 00:18:30 homematic-raspi user.warn kernel: [ 1416.158496] rpi_firmware_get_throttled: 1 callbacks suppressed
Jun  5 00:18:30 homematic-raspi user.info kernel: [ 1416.158510] Voltage normalised (0x00000000)
Jun  5 00:18:43 homematic-raspi user.err monit[992]: 'chronyd' service restarted 1 times within 1 cycles(s) - exec
Jun  5 00:18:43 homematic-raspi user.err monit[992]: 'chronyd' process is not running
Jun  5 00:18:43 homematic-raspi user.info monit[992]: 'chronyd' trying to restart
Jun  5 00:18:43 homematic-raspi user.info monit[992]: 'chronyd' restart: '/etc/init.d/S46chrony restart'
Jun  5 00:18:56 homematic-raspi daemon.err ntpdate[2887]: no server suitable for synchronization found
Jun  5 00:18:57 homematic-raspi user.crit kernel: [ 1442.366395] Under-voltage detected! (0x00050005)
Jun  5 00:19:07 homematic-raspi daemon.err ntpdate[2897]: no server suitable for synchronization found
Jun  5 00:19:09 homematic-raspi user.info kernel: [ 1454.462384] Voltage normalised (0x00000000)
Jun  5 00:19:14 homematic-raspi user.err monit[992]: 'chronyd' failed to restart (exit status 0) -- '/etc/init.d/S46chrony restart': Stopping chrony: FAIL Starting chrony: using default NTPs, could not sync to '0.de.pool.ntp.org 1.de.pool.ntp.org 2.de.pool.ntp.org 3.de.pool.ntp.org', FAIL
Jun  5 00:19:23 homematic-raspi user.info kernel: [ 1468.574369] Voltage normalised (0x00000000)
Jun  5 00:19:30 homematic-raspi user.err monit[992]: 'chronyd' process is not running
Jun  5 00:19:30 homematic-raspi user.info monit[992]: 'chronyd' trying to restart
Jun  5 00:19:30 homematic-raspi user.info monit[992]: 'chronyd' restart: '/etc/init.d/S46chrony restart'
Jun  5 00:19:42 homematic-raspi daemon.err ntpdate[3002]: no server suitable for synchronization found
Jun  5 00:19:53 homematic-raspi daemon.err ntpdate[3019]: no server suitable for synchronization found
Jun  5 00:20:00 homematic-raspi user.err monit[992]: 'chronyd' failed to restart (exit status 0) -- '/etc/init.d/S46chrony restart': Stopping chrony: FAIL Starting chrony: using default NTPs, could not sync to '0.de.pool.ntp.org 1.de.pool.ntp.org 2.de.pool.ntp.org 3.de.pool.ntp.org', FAIL
Jun  5 00:20:16 homematic-raspi user.err monit[992]: 'chronyd' service restarted 1 times within 1 cycles(s) - exec
Jun  5 00:20:16 homematic-raspi user.err monit[992]: 'chronyd' process is not running
Jun  5 00:20:16 homematic-raspi user.info monit[992]: 'chronyd' trying to restart
Jun  5 00:20:16 homematic-raspi user.info monit[992]: 'chronyd' restart: '/etc/init.d/S46chrony restart'
Jun  5 00:20:28 homematic-raspi daemon.err ntpdate[3100]: no server suitable for synchronization found
Jun  5 00:20:39 homematic-raspi daemon.err ntpdate[3113]: no server suitable for synchronization found
Jun  5 00:20:47 homematic-raspi user.err monit[992]: 'chronyd' failed to restart (exit status 0) -- '/etc/init.d/S46chrony restart': Stopping chrony: FAIL Starting chrony: using default NTPs, could not sync to '0.de.pool.ntp.org 1.de.pool.ntp.org 2.de.pool.ntp.org 3.de.pool.ntp.org', FAIL
Jun  5 00:20:49 homematic-raspi user.warn monit[992]: 'voltageCheck' status failed (0) -- no output


***** hmserver.log *****
Jun 4 23:55:50 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] @GenericFactory 
Jun 4 23:55:50 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] created instance of HMServerConfiguration with parameter(s) 
Jun 4 23:55:50 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] passed 1 parameter(s), in declarative order [String] 
Jun 4 23:56:04 de.eq3.cbcs.devicedescription.ChannelTypeDescription WARN  [Thread-0] Invalid state parameter or subtype: Parameter LOCK_STATE_STATUS subtype=default 
Jun 4 23:56:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [HMIPTRXWriterWorker] (1) *worker 
Jun 4 23:56:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [KeyServerWorker] (1) *worker 
Jun 4 23:56:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [KryoPersistenceWorker] (1) *worker 
Jun 4 23:56:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [TransactionSubsystemHandler] (1) *worker 
Jun 4 23:56:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [FirmwareLoaderFileSystem] (1) *worker 
Jun 4 23:56:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerPersistentDataLoader] (1)  
Jun 4 23:56:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerAdapterInitialization] (1)  
Jun 4 23:56:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [TransactionManagementVerticle] (1)  
Jun 4 23:56:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [BackendCommandHandler] (1)  
Jun 4 23:56:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceInclusionAcceptHandler] (1)  
Jun 4 23:56:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [CheckDeviceExistHandler] (1)  
Jun 4 23:56:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [IncomingHMIPFrameHandler] (1)  
Jun 4 23:56:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceBackgroundUpdateSubsystem] (1)  
Jun 4 23:56:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceLiveUpdateSubsystem] (1)  
Jun 4 23:56:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceInclusionDefaultConfigurationChanger] (1)  
Jun 4 23:56:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [CyclicSmokeDetectorAwakening] (1)  
Jun 4 23:56:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerFirmwareUpdateInitialization] (1)  
Jun 4 23:56:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [RoutingNotificationHandler] (1)  
Jun 4 23:56:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [BackboneWorker] (1) *worker 
Jun 4 23:56:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [RouteManagementWorker] (1) *worker 
Jun 4 23:56:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyNotificationHandler] (1) *worker 
Jun 4 23:56:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyAPIWorker] (1) *worker 
Jun 4 23:56:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyBackendNotificationHandler] (3) *worker 
Jun 4 23:56:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyBlindLevelCorrectionHandler] (1) *worker 
Jun 4 23:56:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyInitializion] (1)  
Jun 4 23:56:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: deploying 25 classes to Vert.x 
Jun 4 23:56:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: 25 VertxDeployers initialized 
Jun 4 23:56:06 de.eq3.cbcs.server.core.vertx.CyclicSmokeDetectorAwakening INFO  [vert.x-eventloop-thread-1] SYSTEM: CyclicSmokeDetectorAwakening Verticle or Worker started 
Jun 4 23:56:06 de.eq3.cbcs.server.core.vertx.DeviceInclusionDefaultConfigurationChanger INFO  [vert.x-eventloop-thread-6] SYSTEM: DeviceInclusionDefaultConfigurationChanger Verticle or Worker started 
Jun 4 23:56:06 de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyBlindLevelCorrectionHandler INFO  [vert.x-worker-thread-2] SYSTEM: LegacyBlindLevelCorrectionHandler Verticle or Worker started 
Jun 4 23:56:06 de.eq3.cbcs.server.core.vertx.HMIPAbstractWriterWorker INFO  [vert.x-worker-thread-1] SYSTEM: HMIPTRXWriterWorker Verticle or Worker started 
Jun 4 23:56:06 de.eq3.cbcs.server.core.vertx.TransactionSubsystemHandler INFO  [vert.x-worker-thread-0] SYSTEM: TransactionSubsystemHandler Verticle or Worker started 
Jun 4 23:56:06 de.eq3.cbcs.server.core.vertx.KeyServerWorker ERROR [vert.x-worker-thread-3] Missing key server configuration parameter (Network.Key) for  mode: KEYSERVER_LOCAL 
Jun 4 23:56:06 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of LegacyBlindLevelCorrectionHandler succeeded (419f72df-75fd-4e0f-b6f4-ef7dc55ccaa6) 
Jun 4 23:56:06 de.eq3.cbcs.server.core.vertx.RoutingNotificationHandler INFO  [vert.x-eventloop-thread-0] SYSTEM: RoutingNotificationHandler Verticle or Worker started 
Jun 4 23:56:06 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-6] SYSTEM: start of HMIPTRXWriterWorker succeeded (b2ed7d48-336d-454b-b6ca-dcf8447c8dbc) 
Jun 4 23:56:06 de.eq3.cbcs.server.core.vertx.CheckDeviceExistHandler INFO  [vert.x-eventloop-thread-2] SYSTEM: CheckDeviceExistHandler Verticle or Worker started 
Jun 4 23:56:06 de.eq3.cbcs.server.core.vertx.KeyServerWorker INFO  [vert.x-worker-thread-3] SYSTEM: KeyServerWorker Verticle or Worker started 
Jun 4 23:56:06 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-7] SYSTEM: start of RoutingNotificationHandler succeeded (7be01f27-1b34-4870-80b3-e0c98c741b0c) 
Jun 4 23:56:06 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of TransactionSubsystemHandler succeeded (9049ea7f-e273-4377-a950-298dfcb070ce) 
Jun 4 23:56:06 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of CheckDeviceExistHandler succeeded (b6465047-2024-49c3-a09a-0b958b2fa83b) 
Jun 4 23:56:06 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of CyclicSmokeDetectorAwakening succeeded (2c81e1a4-1198-4a8d-bb05-4cdf38c9f2ba) 
Jun 4 23:56:07 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of KryoPersistenceWorker succeeded (eece4691-0a8d-463e-a2ae-72ff0aa11007) 
Jun 4 23:56:08 de.eq3.cbcs.server.local.base.internal.LocalServerPersistentDataLoader INFO  [vert.x-eventloop-thread-2] SYSTEM: LocalServerPersistentDataLoader Verticle or Worker started 
Jun 4 23:56:08 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of LocalServerPersistentDataLoader succeeded (a2995e90-6a78-4278-909e-0a2aa4b8a8b3) 
Jun 4 23:56:08 de.eq3.cbcs.server.core.otau.AbstractUpdateSubsystem INFO  [vert.x-eventloop-thread-7] SYSTEM: DeviceBackgroundUpdateSubsystem Verticle or Worker started 
Jun 4 23:56:08 de.eq3.cbcs.server.core.otau.AbstractUpdateSubsystem INFO  [vert.x-eventloop-thread-3] SYSTEM: DeviceLiveUpdateSubsystem Verticle or Worker started 
Jun 4 23:56:08 de.eq3.cbcs.server.core.live_otau.DeviceLiveUpdateSubsystem INFO  [vert.x-eventloop-thread-3] SYSTEM: DeviceLiveUpdateSubsystem started 
Jun 4 23:56:08 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of DeviceLiveUpdateSubsystem succeeded (2e776497-10f1-4bb0-ad74-8a04e016f5bd) 
Jun 4 23:56:08 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of DeviceInclusionDefaultConfigurationChanger succeeded (ad08bf10-32ef-4187-9b60-9432b0f34e6e) 
Jun 4 23:56:08 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of KeyServerWorker succeeded (dc2e9153-ffb4-4572-9714-275038318556) 
Jun 4 23:56:08 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of DeviceBackgroundUpdateSubsystem succeeded (065bd253-f78e-45b5-a2b3-1cdaf36ada6c) 
Jun 4 23:56:09 de.eq3.cbcs.server.local.base.internal.LocalServerAdapterInitialization INFO  [vert.x-eventloop-thread-4] SYSTEM: LocalServerAdapterInitialization Verticle or Worker started 
Jun 4 23:56:09 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of LocalServerAdapterInitialization succeeded (6eadf0b0-3af3-4da4-993d-2cb83bd3bb10) 
Jun 4 23:56:09 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-7] TRX adapter state 1: HMIP_TRX_App 
Jun 4 23:56:09 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-7] TRX adapter application is already running or started 
Jun 4 23:56:09 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-7] No NWK, try to set address ... 
Jun 4 23:56:09 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-7] Try to set radio address 11801093... 
Jun 4 23:56:09 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-7] Set max send attempts for 3014F711A0001F5A499403CB to 3 
Jun 4 23:56:09 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-7] Try to get application version... 
Jun 4 23:56:09 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-7] Application version 4.2.14 
Jun 4 23:56:09 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-7] Bootloader version 1.0.1 
Jun 4 23:56:09 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-7] hmos version 1.54.0 
Jun 4 23:56:09 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-7] MCU type: CC1310 
Jun 4 23:56:09 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-7] Duty Cycle: 1.0 
Jun 4 23:56:09 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-7] set DutyCycle limit to ffffffc8 
Jun 4 23:56:09 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-7] Set Duty Cycle Limit 
Jun 4 23:56:09 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-7] Current Security Counter: 305152 
Jun 4 23:56:09 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-7] Update security counter to calculation: 645286 
Jun 4 23:56:10 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-7] TRX adapter has no linkpartner 
Jun 4 23:56:10 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-7] Adapter with Access Point id 3014F711A0001F5A499403CB initialized 
Jun 4 23:56:10 de.eq3.cbcs.server.local.base.internal.LocalServerAdapterInitialization INFO  [Thread-7] HMIPTRXInitialResponseListener said that Adapter was initialized 
Jun 4 23:56:10 de.eq3.cbcs.server.core.otau.util.FirmwareLoaderFileSystem INFO  [vert.x-worker-thread-2] SYSTEM: Firmware update directory is set to /etc/config/firmware 
Jun 4 23:56:10 de.eq3.cbcs.server.core.otau.util.FirmwareLoaderFileSystem INFO  [vert.x-worker-thread-2] SYSTEM: FirmwareLoaderFileSystem Verticle or Worker started 
Jun 4 23:56:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of FirmwareLoaderFileSystem succeeded (aea148ec-2924-42c1-872c-b43292c90989) 
Jun 4 23:56:10 de.eq3.cbcs.server.core.vertx.DeviceInclusionAcceptHandler INFO  [vert.x-eventloop-thread-7] SYSTEM: DeviceInclusionAcceptHandler Verticle or Worker started 
Jun 4 23:56:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-6] SYSTEM: start of DeviceInclusionAcceptHandler succeeded (2e162a80-74c2-484e-8ae7-997e48f03cbe) 
Jun 4 23:56:10 de.eq3.cbcs.server.core.vertx.IncomingHMIPFrameHandler INFO  [vert.x-eventloop-thread-6] SYSTEM: IncomingHMIPFrameHandler Verticle or Worker started 
Jun 4 23:56:10 de.eq3.cbcs.server.local.base.internal.LocalServerFirmwareUpdateInitialization INFO  [vert.x-eventloop-thread-3] SYSTEM: LocalServerFirmwareUpdateInitialization Verticle or Worker started 
Jun 4 23:56:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of LocalServerFirmwareUpdateInitialization succeeded (8de2cb35-ed42-4b36-8d0f-29a4572b2f47) 
Jun 4 23:56:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of IncomingHMIPFrameHandler succeeded (4cbabecb-a830-4fc8-9160-36a9e1ec0fa3) 
Jun 4 23:56:10 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-7] SYSTEM: Checking all devices on all accesspoints for updates 
Jun 4 23:56:10 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-7] SYSTEM: There are 0 APs queued with updatable devices (RF) 
Jun 4 23:56:10 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-7] SYSTEM: There are 0 APs queued with updatable devices (WIRED) 
Jun 4 23:56:10 de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyBackendNotificationHandler INFO  [vert.x-worker-thread-3] SYSTEM: LegacyBackendNotificationHandler Verticle or Worker started 
Jun 4 23:56:10 de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyBackendNotificationHandler INFO  [vert.x-worker-thread-1] SYSTEM: LegacyBackendNotificationHandler Verticle or Worker started 
Jun 4 23:56:10 de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyBackendNotificationHandler INFO  [vert.x-worker-thread-3] SYSTEM: LegacyBackendNotificationHandler Verticle or Worker started 
Jun 4 23:56:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of LegacyBackendNotificationHandler succeeded (3ebb8113-8698-4514-ab0e-17b0300be789) 
Jun 4 23:56:10 de.eq3.cbcs.server.core.transaction.TransactionManagementVerticle INFO  [vert.x-eventloop-thread-7] SYSTEM: TransactionManagementVerticle Verticle or Worker started 
Jun 4 23:56:10 de.eq3.cbcs.lib.backbone.lanrouting.RouteManagementWorker INFO  [vert.x-worker-thread-2] SYSTEM: RouteManagementWorker Verticle or Worker started 
Jun 4 23:56:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of TransactionManagementVerticle succeeded (a2233c9b-2ea1-4f6f-ad4c-e5a50a97a6be) 
Jun 4 23:56:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of RouteManagementWorker succeeded (7e09ecf3-05fb-447a-8cab-6759981013e6) 
Jun 4 23:56:10 de.eq3.cbcs.lib.backbone.lanrouting.UdpServer INFO  [vert.x-worker-thread-4] UDP Routing configuration: trying to bind port 43438 on eth0 0.0.0.0 -> 192.168.1.20 
Jun 4 23:56:10 de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyNotificationHandler INFO  [vert.x-worker-thread-0] SYSTEM: LegacyNotificationHandler Verticle or Worker started 
Jun 4 23:56:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of LegacyNotificationHandler succeeded (12447e9f-5267-4785-8369-f7ca4d4ed571) 
Jun 4 23:56:10 de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyAPIWorker INFO  [vert.x-worker-thread-1] SYSTEM: LegacyAPIWorker Verticle or Worker started 
Jun 4 23:56:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of LegacyAPIWorker succeeded (28dfa6a4-1745-4a72-9535-1b994eafc97d) 
Jun 4 23:56:12 de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyInitializion INFO  [vert.x-eventloop-thread-5] SYSTEM: LegacyInitializion Verticle or Worker started 
Jun 4 23:56:12 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of LegacyInitializion succeeded (24ecd152-c1d6-47c6-96ae-78d98b32bbeb) 
Jun 4 23:56:12 de.eq3.cbcs.server.core.vertx.BackendCommandHandler INFO  [vert.x-eventloop-thread-1] SYSTEM: BackendCommandHandler Verticle or Worker started 
Jun 4 23:56:12 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of BackendCommandHandler succeeded (2c24edcb-2cac-42d4-9597-c51cd20bd5d9) 
Jun 4 23:56:12 de.eq3.cbcs.lib.backbone.lanrouting.BackboneWorker INFO  [vert.x-worker-thread-4] SYSTEM: BackboneWorker Verticle or Worker started 
Jun 4 23:56:12 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-7] SYSTEM: start of BackboneWorker succeeded (0f62b59c-16a8-42c1-b6fb-27b93f2993c3) 
Jun 4 23:56:12 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: initial deployment complete _____________________________________________________ 
Jun 4 23:56:12 de.eq3.cbcs.lib.backbone.lanrouting.UdpServer INFO  [vert.x-worker-thread-1] UDP Routing established on network interface eth0 : 0.0.0.0 (192.168.1.20) 
Jun 4 23:56:12 de.eq3.cbcs.lib.backbone.lanrouting.UdpServer INFO  [vert.x-worker-thread-1] UDP Routing multi cast 'DEFAULT_MULTICAST_ADDRESS' established on network interface eth0 : 192.168.1.20 
Jun 4 23:56:14 de.eq3.cbcs.server.local.LocalServer INFO  [Thread-0] SYSTEM: Bind XML-RPC api to port 32010 
Jun 4 23:56:15 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Default MaxEventLoopExecuteTime: 2000000000 
Jun 4 23:56:15 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Default BlockedThreadCheckInterval: 1000 
Jun 4 23:56:15 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Default MaxWorkerExecuteTime: 60000000000 
Jun 4 23:56:15 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Default EventLoopPoolSize: 8 
Jun 4 23:56:15 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [BackendWorker] (1) *worker 
Jun 4 23:56:15 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [GroupRequestWorker] (1) *worker 
Jun 4 23:56:15 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [DiagramRequestWorker] (1) *worker 
Jun 4 23:56:15 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [StorageRequestWorker] (1) *worker 
Jun 4 23:56:15 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [DeviceFirmwareRequestWorker] (1) *worker 
Jun 4 23:56:15 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [EnergyPriceRequestWorker] (1) *worker 
Jun 4 23:56:15 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [CouplingRequestWorker] (1) *worker 
Jun 4 23:56:15 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [RegaClientWorker] (1) *worker 
Jun 4 23:56:15 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [GroupConfigurationPersistenceFileSystem] (1) *worker 
Jun 4 23:56:15 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [HmIPGatewayManagementRequestWorker] (1) *worker 
Jun 4 23:56:15 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [AccessPointUpdateServerWorker] (1) *worker 
Jun 4 23:56:15 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [AccessPointUpdateLoaderWorker] (1) *worker 
Jun 4 23:56:15 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: deploying 12 classes to Vert.x 
Jun 4 23:56:15 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: 12 VertxDeployers initialized 
Jun 4 23:56:15 de.eq3.ccu.hmip.accesspoint.update.AccessPointUpdateLoaderWorker INFO  [vert.x-worker-thread-3] SYSTEM: Firmware update directory is set to /etc/config/firmware 
Jun 4 23:56:15 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of AccessPointUpdateLoaderWorker succeeded (20d10b18-d25e-47ef-ba88-4caf6fc1fa09) 
Jun 4 23:56:15 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of GroupConfigurationPersistenceFileSystem succeeded (bb2dab77-b5f9-41f1-bab5-94ee254281d2) 
Jun 4 23:56:15 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of CouplingRequestWorker succeeded (13d8874c-935e-4f78-8b37-995387ae9eac) 
Jun 4 23:56:15 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of RegaClientWorker succeeded (39bec635-819c-4e1f-868d-7eb0d3285031) 
Jun 4 23:56:15 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of AccessPointUpdateServerWorker succeeded (a48617cc-0dd2-419d-8a65-836911af8597) 
Jun 4 23:56:15 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of EnergyPriceRequestWorker succeeded (bf427228-c023-40f6-b16c-52b71fc2b870) 
Jun 4 23:56:15 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of BackendWorker succeeded (a533f247-e47f-44d9-8d2f-d4f02a2da66a) 
Jun 4 23:56:15 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of StorageRequestWorker succeeded (ad4cf136-8a6d-46be-a748-c9946a78f2c2) 
Jun 4 23:56:15 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of DiagramRequestWorker succeeded (c5c0a0ca-b167-4124-bb53-316ad4ed45ba) 
Jun 4 23:56:15 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of GroupRequestWorker succeeded (336f6534-fe26-4871-a17f-5c992f8923f5) 
Jun 4 23:56:15 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of DeviceFirmwareRequestWorker succeeded (80780fe0-5bc1-44b2-93b1-b64caca4e6f0) 
Jun 4 23:56:15 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of HmIPGatewayManagementRequestWorker succeeded (0a4ffa79-47d2-4501-91ad-27dcb6b9a736) 
Jun 4 23:56:15 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: initial deployment complete _____________________________________________________ 
Jun 4 23:56:15 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Starting HMServer at 127.0.0.1:39292 
Jun 4 23:56:15 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Read Configuration 
Jun 4 23:56:16 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create Bidcos Dispatcher 
Jun 4 23:56:16 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] InitBidCosCache 
Jun 4 23:56:19 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create groupDefinitionProvider 
Jun 4 23:56:20 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create VirtualDeviceHolder 
Jun 4 23:56:21 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create VirtualDeviceHandlerRega 
Jun 4 23:56:21 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create GroupAdministrationService 
Jun 4 23:56:21 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create GroupDeviceDispatcher 
Jun 4 23:56:21 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create GroupDeviceHandler 
Jun 4 23:56:21 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-1] @GroupDeviceHandler - initializing... 
Jun 4 23:56:21 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-1] --> created groupDeviceDispatcher (GroupDeviceService to BidCoS (via Dispatcher)) 
Jun 4 23:56:21 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-1] --> created virtualDeviceHandler (GroupDeviceService to ReGa) 
Jun 4 23:56:21 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-1] --> got groupDefinitionProvider 
Jun 4 23:56:21 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create BidCosGroupMemberProvider 
Jun 4 23:56:21 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Init groupAdministrationService 
Jun 4 23:56:21 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Init Virtual OS Device 
Jun 4 23:56:21 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Init ESHLight Bridge 
Jun 4 23:56:23 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create RrdDatalogging 
Jun 4 23:56:23 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create MeasurementService 
Jun 4 23:56:23 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Init MeasurementService 
Jun 4 23:56:23 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create HTTP Server 
Jun 4 23:56:23 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create BidCos context and start handler 
Jun 4 23:56:23 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create group context and start handler 
Jun 4 23:56:23 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-2] (un)registerCallback on LegacyServiceHandler called from url: http://127.0.0.1:39292/bidcos 
Jun 4 23:56:23 de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyBackendNotificationHandler INFO  [HmIP-RF_java_WorkerPool-0] SYSTEM: LegacyBackendNotificationHandler Verticle or Worker started 
Jun 4 23:56:23 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-4] init finished 
Jun 4 23:56:23 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO  [vert.x-worker-thread-3] Added InterfaceId: HmIP-RF_java 
Jun 4 23:56:24 de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil INFO  [vert.x-worker-thread-3] updateDevicesForClient HmIP-RF_java -> 54 device addresses will be added 
Jun 4 23:56:24 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-7] SYSTEM: Checking all devices on all accesspoints for updates 
Jun 4 23:56:24 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-7] SYSTEM: There are 0 APs queued with updatable devices (RF) 
Jun 4 23:56:24 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-7] SYSTEM: There are 0 APs queued with updatable devices (WIRED) 
Jun 4 23:56:24 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Starting HMServer done 
Jun 4 23:56:32 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-5] (un)registerCallback on VirtualDeviceHandlerRega called from url: xmlrpc_bin://127.0.0.1:31999 
Jun 4 23:56:32 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-5] Added InterfaceId: 1007 
Jun 4 23:56:32 de.eq3.ccu.virtualdevice.service.internal.rega.BackendWorker INFO  [vert.x-worker-thread-14] Execute BackendCommand: de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand 
Jun 4 23:56:42 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-0] (un)registerCallback on LegacyServiceHandler called from url: xmlrpc_bin://127.0.0.1:31999 
Jun 4 23:56:42 de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyBackendNotificationHandler INFO  [1038_WorkerPool-0] SYSTEM: LegacyBackendNotificationHandler Verticle or Worker started 
Jun 4 23:56:42 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO  [vert.x-worker-thread-2] Added InterfaceId: 1038 
Jun 4 23:56:42 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-0] init finished 
Jun 5 00:01:08 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-7] SYSTEM: 0 Accesspoints in Queue 
Jun 5 00:01:08 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-7] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Jun 5 00:01:08 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-7] SYSTEM: Eventlistener Handler utilization: 0/50 used 
Jun 5 00:06:08 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-7] SYSTEM: 0 Accesspoints in Queue 
Jun 5 00:06:08 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-7] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Jun 5 00:06:08 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-7] SYSTEM: Eventlistener Handler utilization: 0/50 used 
Jun 5 00:11:08 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-7] SYSTEM: 0 Accesspoints in Queue 
Jun 5 00:11:08 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-7] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Jun 5 00:11:08 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-7] SYSTEM: Eventlistener Handler utilization: 0/50 used 
Jun 5 00:16:08 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-7] SYSTEM: 0 Accesspoints in Queue 
Jun 5 00:16:08 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-7] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Jun 5 00:16:08 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-7] SYSTEM: Eventlistener Handler utilization: 0/50 used 
Jun 5 00:18:56 de.eq3.cbcs.server.core.vertx.keyserver.KeyServerOperation WARN  [vert.x-worker-thread-3] AP 3014F711A0001F5A499403CB: Exception while communicating to Frontend Server: 
io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: secgtw.homematic.com/81.14.202.208:8443
	at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
	at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:716)
	at io.netty.channel.socket.nio.NioSocketChannel.doFinishConnect(NioSocketChannel.java:347)
	at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:340)
	at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:630)
	at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:565)
	at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:479)
	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:441)
	at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:858)
	at java.lang.Thread.run(Thread.java:748)
Jun 5 00:18:56 de.eq3.cbcs.server.core.internal.InclusionHandling INFO  [vert.x-eventloop-thread-7] AP 3014F711A0001F5A499403CB: Aborting inclusion process; device 3014F711A0000A9BE9A1D02B will stay in inclusion state UNKNOWN 
Jun 5 00:19:05 de.eq3.cbcs.server.core.vertx.keyserver.KeyServerOperation WARN  [vert.x-worker-thread-2] AP 3014F711A0001F5A499403CB: Exception while communicating to Frontend Server: 
io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: secgtw.homematic.com/81.14.202.208:8443
	at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
	at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:716)
	at io.netty.channel.socket.nio.NioSocketChannel.doFinishConnect(NioSocketChannel.java:347)
	at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:340)
	at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:630)
	at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:565)
	at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:479)
	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:441)
	at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:858)
	at java.lang.Thread.run(Thread.java:748)
Jun 5 00:19:05 de.eq3.cbcs.server.core.internal.InclusionHandling INFO  [vert.x-eventloop-thread-7] AP 3014F711A0001F5A499403CB: Aborting inclusion process; device 3014F711A0000A9BE9A1D02B will stay in inclusion state UNKNOWN 
Jun 5 00:19:15 de.eq3.cbcs.server.core.vertx.keyserver.KeyServerOperation WARN  [vert.x-worker-thread-0] AP 3014F711A0001F5A499403CB: Exception while communicating to Frontend Server: 
io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: secgtw.homematic.com/81.14.202.208:8443
	at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
	at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:716)
	at io.netty.channel.socket.nio.NioSocketChannel.doFinishConnect(NioSocketChannel.java:347)
	at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:340)
	at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:630)
	at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:565)
	at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:479)
	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:441)
	at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:858)
	at java.lang.Thread.run(Thread.java:748)
Jun 5 00:19:15 de.eq3.cbcs.server.core.internal.InclusionHandling INFO  [vert.x-eventloop-thread-7] AP 3014F711A0001F5A499403CB: Aborting inclusion process; device 3014F711A0000A9BE9A1D02B will stay in inclusion state UNKNOWN 
Jun 5 00:19:25 de.eq3.cbcs.server.core.vertx.keyserver.KeyServerOperation WARN  [vert.x-worker-thread-3] AP 3014F711A0001F5A499403CB: Exception while communicating to Frontend Server: 
io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: secgtw.homematic.com/81.14.202.208:8443
	at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
	at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:716)
	at io.netty.channel.socket.nio.NioSocketChannel.doFinishConnect(NioSocketChannel.java:347)
	at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:340)
	at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:630)
	at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:565)
	at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:479)
	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:441)
	at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:858)
	at java.lang.Thread.run(Thread.java:748)
Jun 5 00:19:25 de.eq3.cbcs.server.core.internal.InclusionHandling INFO  [vert.x-eventloop-thread-7] AP 3014F711A0001F5A499403CB: Aborting inclusion process; device 3014F711A0000A9BE9A1D02B will stay in inclusion state UNKNOWN 
Jun 5 00:19:35 de.eq3.cbcs.server.core.vertx.keyserver.KeyServerOperation WARN  [vert.x-worker-thread-0] AP 3014F711A0001F5A499403CB: Exception while communicating to Frontend Server: 
io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: secgtw.homematic.com/81.14.202.208:8443
	at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
	at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:716)
	at io.netty.channel.socket.nio.NioSocketChannel.doFinishConnect(NioSocketChannel.java:347)
	at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:340)
	at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:630)
	at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:565)
	at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:479)
	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:441)
	at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:858)
	at java.lang.Thread.run(Thread.java:748)
Jun 5 00:19:35 de.eq3.cbcs.server.core.internal.InclusionHandling INFO  [vert.x-eventloop-thread-7] AP 3014F711A0001F5A499403CB: Aborting inclusion process; device 3014F711A0000A9BE9A1D02B will stay in inclusion state UNKNOWN 
Jun 5 00:19:45 de.eq3.cbcs.server.core.vertx.keyserver.KeyServerOperation WARN  [vert.x-worker-thread-0] AP 3014F711A0001F5A499403CB: Exception while communicating to Frontend Server: 
io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: secgtw.homematic.com/81.14.202.208:8443
	at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
	at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:716)
	at io.netty.channel.socket.nio.NioSocketChannel.doFinishConnect(NioSocketChannel.java:347)
	at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:340)
	at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:630)
	at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:565)
	at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:479)
	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:441)
	at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:858)
	at java.lang.Thread.run(Thread.java:748)
Jun 5 00:19:45 de.eq3.cbcs.server.core.internal.InclusionHandling INFO  [vert.x-eventloop-thread-7] AP 3014F711A0001F5A499403CB: Aborting inclusion process; device 3014F711A0000A9BE9A1D02B will stay in inclusion state UNKNOWN 
Jun 5 00:19:55 de.eq3.cbcs.server.core.vertx.keyserver.KeyServerOperation WARN  [vert.x-worker-thread-0] AP 3014F711A0001F5A499403CB: Exception while communicating to Frontend Server: 
io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: secgtw.homematic.com/81.14.202.208:8443
	at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
	at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:716)
	at io.netty.channel.socket.nio.NioSocketChannel.doFinishConnect(NioSocketChannel.java:347)
	at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:340)
	at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:630)
	at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:565)
	at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:479)
	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:441)
	at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:858)
	at java.lang.Thread.run(Thread.java:748)
Jun 5 00:19:55 de.eq3.cbcs.server.core.internal.InclusionHandling INFO  [vert.x-eventloop-thread-7] AP 3014F711A0001F5A499403CB: Aborting inclusion process; device 3014F711A0000A9BE9A1D02B will stay in inclusion state UNKNOWN 
Jun 5 00:20:05 de.eq3.cbcs.server.core.vertx.keyserver.KeyServerOperation WARN  [vert.x-worker-thread-4] AP 3014F711A0001F5A499403CB: Exception while communicating to Frontend Server: 
io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: secgtw.homematic.com/81.14.202.208:8443
	at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
	at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:716)
	at io.netty.channel.socket.nio.NioSocketChannel.doFinishConnect(NioSocketChannel.java:347)
	at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:340)
	at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:630)
	at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:565)
	at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:479)
	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:441)
	at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:858)
	at java.lang.Thread.run(Thread.java:748)
Jun 5 00:20:05 de.eq3.cbcs.server.core.internal.InclusionHandling INFO  [vert.x-eventloop-thread-7] AP 3014F711A0001F5A499403CB: Aborting inclusion process; device 3014F711A0000A9BE9A1D02B will stay in inclusion state UNKNOWN 
Jun 5 00:20:15 de.eq3.cbcs.server.core.vertx.keyserver.KeyServerOperation WARN  [vert.x-worker-thread-1] AP 3014F711A0001F5A499403CB: Exception while communicating to Frontend Server: 
io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: secgtw.homematic.com/81.14.202.208:8443
	at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
	at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:716)
	at io.netty.channel.socket.nio.NioSocketChannel.doFinishConnect(NioSocketChannel.java:347)
	at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:340)
	at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:630)
	at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:565)
	at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:479)
	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:441)
	at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:858)
	at java.lang.Thread.run(Thread.java:748)
Jun 5 00:20:15 de.eq3.cbcs.server.core.internal.InclusionHandling INFO  [vert.x-eventloop-thread-7] AP 3014F711A0001F5A499403CB: Aborting inclusion process; device 3014F711A0000A9BE9A1D02B will stay in inclusion state UNKNOWN 
Jun 5 00:20:25 de.eq3.cbcs.server.core.vertx.keyserver.KeyServerOperation WARN  [vert.x-worker-thread-1] AP 3014F711A0001F5A499403CB: Exception while communicating to Frontend Server: 
io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: secgtw.homematic.com/81.14.202.208:8443
	at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
	at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:716)
	at io.netty.channel.socket.nio.NioSocketChannel.doFinishConnect(NioSocketChannel.java:347)
	at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:340)
	at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:630)
	at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:565)
	at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:479)
	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:441)
	at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:858)
	at java.lang.Thread.run(Thread.java:748)
Jun 5 00:20:25 de.eq3.cbcs.server.core.internal.InclusionHandling INFO  [vert.x-eventloop-thread-7] AP 3014F711A0001F5A499403CB: Aborting inclusion process; device 3014F711A0000A9BE9A1D02B will stay in inclusion state UNKNOWN 
Jun 5 00:20:35 de.eq3.cbcs.server.core.vertx.keyserver.KeyServerOperation WARN  [vert.x-worker-thread-3] AP 3014F711A0001F5A499403CB: Exception while communicating to Frontend Server: 
io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: secgtw.homematic.com/81.14.202.208:8443
	at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
	at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:716)
	at io.netty.channel.socket.nio.NioSocketChannel.doFinishConnect(NioSocketChannel.java:347)
	at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:340)
	at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:630)
	at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:565)
	at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:479)
	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:441)
	at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:858)
	at java.lang.Thread.run(Thread.java:748)
Jun 5 00:20:35 de.eq3.cbcs.server.core.internal.InclusionHandling INFO  [vert.x-eventloop-thread-7] AP 3014F711A0001F5A499403CB: Aborting inclusion process; device 3014F711A0000A9BE9A1D02B will stay in inclusion state UNKNOWN 
Jun 5 00:20:45 de.eq3.cbcs.server.core.vertx.keyserver.KeyServerOperation WARN  [vert.x-worker-thread-3] AP 3014F711A0001F5A499403CB: Exception while communicating to Frontend Server: 
io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: secgtw.homematic.com/81.14.202.208:8443
	at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
	at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:716)
	at io.netty.channel.socket.nio.NioSocketChannel.doFinishConnect(NioSocketChannel.java:347)
	at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:340)
	at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:630)
	at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:565)
	at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:479)
	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:441)
	at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:858)
	at java.lang.Thread.run(Thread.java:748)
Jun 5 00:20:45 de.eq3.cbcs.server.core.internal.InclusionHandling INFO  [vert.x-eventloop-thread-7] AP 3014F711A0001F5A499403CB: Aborting inclusion process; device 3014F711A0000A9BE9A1D02B will stay in inclusion state UNKNOWN 

Gruß Jochen
Zuletzt geändert von Roland M. am 05.06.2021, 10:56, insgesamt 2-mal geändert.
Grund: Thema verschoben
Hardware:
Raspberry Pi 3+ (16GB Sd) RaspberryMatic-3.57.5.20210525-rpi3.img
RPI-RF-MOD Firmware 4.2.14
Netzteil 5V 3A
Steckdose HMIP-PSM
Temperaturanzeige HMIP-WTH-2
Fernbedienung HMIP-RC8
und Heizkörperthermostate und Fensterkontakte
und einiges mehr ...

Xel66
Beiträge: 9579
Registriert: 08.05.2013, 23:33
System: Alternative CCU (auf Basis OCCU)
Wohnort: Nordwürttemberg
Hat sich bedankt: 128 Mal
Danksagung erhalten: 623 Mal

Re: mit Charly kein Geräte anlernen möglich

Beitrag von Xel66 » 05.06.2021, 05:58

JochenV hat geschrieben:
05.06.2021, 00:28
Frage 1.
Nein, man kann nichts, aber auch gar nichts übernehmen. Ein Umstieg bedeutet einen vollständigen Neubeginn.
JochenV hat geschrieben:
05.06.2021, 00:28
Frage 2....
Wieso kommt diese Meldung ?
Das was Du eventuell auch einem Messgerät siehst, ist nur die halbe Wahrheit. In Lastspitzen geht die Spannung kurzfristig runter und triggert die Meldung. Und welche Spannung am Netzteil anliegt und was nachher an der Buchse des Pi ankommt, sind auch zwei verschiedene Welten.
JochenV hat geschrieben:
05.06.2021, 00:28
Frage 3 und wichtigste Frage.
ich kann keine Geräte anlernen.
Klingt für mich nach Pi4. Dieser hat einen ausgesprochen starken Störnebel, welches die CS-Erkennung (Carrier Sense) triggert und somit die Sendemöglichkeiten des Funkmoduls einschränkt (listen before call). Hier hilft nur, einen anderen Pi(3) einzusetzen oder das Funkmodul abzusetzen.

Gruß Xel66
-------------------------------------------------------------------------------------------
343 Kanäle in 118 Geräten und 264 CUxD-Kanäle in 33 CUxD-Geräten:
282 Programme, 246 Systemvariablen und 144 Direktverknüpfungen,
RaspberryMatic Version 3.55.10.20210213 + Testsystem: CCU2 2.53.27
-------------------------------------------------------------------------------------------
Einsteigerthread, Programmlogik-Thread, WebUI-Handbuch

Daimler
Beiträge: 8032
Registriert: 17.11.2012, 10:47
Wohnort: Köln
Hat sich bedankt: 14 Mal
Danksagung erhalten: 179 Mal

Re: mit Charly kein Geräte anlernen möglich

Beitrag von Daimler » 05.06.2021, 06:30

Hi,
Xel66 hat geschrieben:
05.06.2021, 05:58
Klingt für mich nach Pi4.
JochenV hat geschrieben:
05.06.2021, 00:28
Raspberry Pi 3+ (16GB Sd)
:wink:
JochenV hat geschrieben:
05.06.2021, 00:28
RaspberryMatic-3.57.5.20210525-rpi3.img
Dann bist du hier im falschen Unterforum :!:
Lass den Beitrag von einem Moderator verschieben.

RPI-RF-MOD Firmware 4.2.14 - steckt das auf der GPIO-Leiste oder wie ist das angeschlossen?
Gruß Günter

3 * pivccx mit 3.57.4 in Produktiv, pivccx mit 3.57.4 Testsystem mit HM-, HMIP- und HMIP-Wired Testgeräten, 3 * HPCx Studio 4.1,
6 * L-Gateway, 3 * RS-L-Gateway, 4 * HAP, FHZ200x, vereinzelt noch FS2x-Komponenten.
HM: Zur Zeit knapp 300 Komponenten mit ??? Kanälen .

Ich übernehme für alle von mir gegebenen Hinweise, Tipps und Links keine Haftung! Das Befolgen meiner Tipps ist nur für Fachkundige gedacht und erfolgt auf eigene Gefahr!

Xel66
Beiträge: 9579
Registriert: 08.05.2013, 23:33
System: Alternative CCU (auf Basis OCCU)
Wohnort: Nordwürttemberg
Hat sich bedankt: 128 Mal
Danksagung erhalten: 623 Mal

Re: mit Charly kein Geräte anlernen möglich

Beitrag von Xel66 » 05.06.2021, 06:39

Daimler hat geschrieben:
05.06.2021, 06:30
:wink:
OK, überlesen. Heißt aber nicht, dass die CCU nicht doch in der Nähe eines funkenden Gerätes (WLAN-Router, DECT-Telefon o.ä.) steht, was die CS-Erkennung zuballert. Bisher war es bei ähnlichen Berichten immer ein Pi4. Da ist man eben konditioniert. ;-)

Gruß Xel66
-------------------------------------------------------------------------------------------
343 Kanäle in 118 Geräten und 264 CUxD-Kanäle in 33 CUxD-Geräten:
282 Programme, 246 Systemvariablen und 144 Direktverknüpfungen,
RaspberryMatic Version 3.55.10.20210213 + Testsystem: CCU2 2.53.27
-------------------------------------------------------------------------------------------
Einsteigerthread, Programmlogik-Thread, WebUI-Handbuch

deimos
Beiträge: 4427
Registriert: 20.06.2017, 10:38
Wohnort: Leimersheim
Hat sich bedankt: 76 Mal
Danksagung erhalten: 512 Mal
Kontaktdaten:

Re: mit Charly kein Geräte anlernen möglich

Beitrag von deimos » 05.06.2021, 07:36

Hi,

erst in der Weboberfläche den Anlernmodus starten, dann die Stromversorgung des Geräts herstellen und nichts am Gerät drücken.

Viele Grüße
Alex

Baxxy
Beiträge: 3395
Registriert: 18.12.2018, 15:45
System: Alternative CCU (auf Basis OCCU)
Hat sich bedankt: 235 Mal
Danksagung erhalten: 569 Mal

Re: mit Charly kein Geräte anlernen möglich

Beitrag von Baxxy » 05.06.2021, 08:36

JochenV hat geschrieben:
05.06.2021, 00:28
"WatchDog-Alarm - ausgelöst - under-voltage detected"
Mal ein anderes Netzteil testen, idealerweise eins mit Hohlstecker direkt am Funkmodul
JochenV hat geschrieben:
05.06.2021, 00:28
ich kann keine Geräte anlernen.
Der normale Anlernvorgang "Homematic IP Gerät mit Internetzugang anlernen" kann bei Dir nicht funktionieren.
Deine Zentrale kann keine Verbindung zum eQ-3 Keyserver herstellen was dafür zwingend erforderlich ist. Irgendwas im Heimnetz blockt die Verbindung deiner Zentrale ins Internet.
Das sieht man im Log, z.B hier:

Code: Alles auswählen

Jun 5 00:19:15 de.eq3.cbcs.server.core.vertx.keyserver.KeyServerOperation WARN  [vert.x-worker-thread-0] AP 3014F711A0001F5A499403CB: Exception while communicating to Frontend Server: 
io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: secgtw.homematic.com/81.14.202.208:8443
Deine Zentrale kann auch keine korrekte Uhrzeit beziehen da du scheinbar keinen lokalen NTP-Server hast und die Online-NTP Server nicht erreichbar sind.

Code: Alles auswählen

Jun  5 00:16:55 homematic-raspi user.err monit[992]: 'chronyd' failed to restart (exit status 0) -- '/etc/init.d/S46chrony restart': Stopping chrony: FAIL Starting chrony: using default NTPs, could not sync to '0.de.pool.ntp.org 1.de.pool.ntp.org 2.de.pool.ntp.org 3.de.pool.ntp.org', FAIL 
Die Uhrzeitsynchronisation ist m.E. nicht so dramatisch, du hast ja scheinbar die Uhrzeit manuell korrekt gesetzt.

Warum das Anlernen ohne Internetzugang auch nicht geht kann ich nicht sagen, vielleicht Tippfehler bei der Eingabe von KEY /SGTIN

Hast du mal auf der Startseite geschaut wie hoch der CS-Wert ist?

JochenV
Beiträge: 9
Registriert: 04.06.2021, 23:04
System: Alternative CCU (auf Basis OCCU)
Danksagung erhalten: 1 Mal

Re: mit Charly kein Geräte anlernen möglich

Beitrag von JochenV » 07.06.2021, 15:56

Hallo und Danke für Eure Antworten.
Baxxy hat geschrieben:
05.06.2021, 08:36
JochenV hat geschrieben: ↑
05.06.2021, 00:28
"WatchDog-Alarm - ausgelöst - under-voltage detected"

Mal ein anderes Netzteil testen, idealerweise eins mit Hohlstecker direkt am Funkmodul
Ist bestellt.
Baxxy hat geschrieben:
05.06.2021, 08:36
Jun 5 00:16:55 homematic-raspi user.err monit[992]: 'chronyd' failed to restart (exit status 0) -- '/etc/init.d/S46chrony restart': Stopping chrony: FAIL Starting chrony: using default NTPs, could not sync to '0.de.pool.ntp.org 1.de.pool.ntp.org 2.de.pool.ntp.org 3.de.pool.ntp.org', FAIL

Die Uhrzeitsynchronisation ist m.E. nicht so dramatisch, du hast ja scheinbar die Uhrzeit manuell korrekt gesetzt.
Ich habe mal ein ping von Laptop und ein ping vom PI gemacht. Der ping läuft beides mal, jedoch wurde wurde die Ardresse auf dem Laptop aufgelöst und bei PI nicht.

Code: Alles auswählen

Laptop
>ping 0.de.pool.ntp.org
PING 0.de.pool.ntp.org (162.159.200.123) 56(84) Bytes Daten.
64 Bytes von time.cloudflare.com (162.159.200.123): icmp_seq=1 ttl=59 Zeit=23.1 ms
64 Bytes von time.cloudflare.com (162.159.200.123): icmp_seq=2 ttl=59 Zeit=22.8 ms

PI
>ping 0.de.pool.ntp.org
PING 0.de.pool.ntp.org (162.159.200.123): 56 data bytes
64 bytes from 162.159.200.123: seq=1 ttl=59 time=26.194 ms
64 bytes from 162.159.200.123: seq=2 ttl=59 time=22.263 ms
Hardware:
Raspberry Pi 3+ (16GB Sd) RaspberryMatic-3.57.5.20210525-rpi3.img
RPI-RF-MOD Firmware 4.2.14
Netzteil 5V 3A
Steckdose HMIP-PSM
Temperaturanzeige HMIP-WTH-2
Fernbedienung HMIP-RC8
und Heizkörperthermostate und Fensterkontakte
und einiges mehr ...

JochenV
Beiträge: 9
Registriert: 04.06.2021, 23:04
System: Alternative CCU (auf Basis OCCU)
Danksagung erhalten: 1 Mal

Re: mit Charly kein Geräte anlernen möglich

Beitrag von JochenV » 07.06.2021, 16:08

Hallo zusammen,

zu meiner Frage 3:
Problem ist gelöst.

Das Problem lag an nicht offenen Ports. Nachdem ich alle Ports für den Pi auf gemacht hatte lief alles.
Jetzt würde ich gern ein paar Ports wieder zu machen. Welche Ports werden benötigt ?

Gruß Jochen
Hardware:
Raspberry Pi 3+ (16GB Sd) RaspberryMatic-3.57.5.20210525-rpi3.img
RPI-RF-MOD Firmware 4.2.14
Netzteil 5V 3A
Steckdose HMIP-PSM
Temperaturanzeige HMIP-WTH-2
Fernbedienung HMIP-RC8
und Heizkörperthermostate und Fensterkontakte
und einiges mehr ...

Antworten

Zurück zu „RaspberryMatic“