LAN Adapter erzeugen Fehlermeldungen auf CCU2

Einrichtung, Anschluss und Programmierung der HomeMatic CCU

Moderator: Co-Administratoren

Antworten
ABN
Beiträge: 2
Registriert: 03.04.2018, 19:38

LAN Adapter erzeugen Fehlermeldungen auf CCU2

Beitrag von ABN » 03.04.2018, 19:56

Hallo zusammen,

vor einigen Wochen habe ich meine CCU1 gegen eine CCU2 getauscht und der Wechsel hat problemlos geklappt.
Zur Reichweitenverlängerung (Keller, EG, OG) habe ich auf jeder Etage einen runden LAN-Adapter.

In letzter Zeit gibt es einige Auffälligkeiten:
a.) hin und wieder wird ein Status verspätet aktualisiert
b.) die CCU2 wird bei mir weitgehend nur als "Gateway" eingesetzt, ich verwende IP-Symcon. Dort kommen Stati ebenfalls verspätet oder gar nicht an und, viel schlimmer, scripte laufen mal und mal nicht. Eine Fehlermeldung in IP-Symcon läßt auf einen Fehler in der CCU schliessen, daher folgende Log-Datei der CCU zur Begutachtung:

In der Logdatei der Ccu2 sind sehr viele Einträge:

Code: Alles auswählen

Apr 2 08:20:24 homematic-ccu2 user.err rfd: 0: Could not determine IP
Apr 2 08:20:33 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::GetObjectByHSSAddress: no exists device object with address= IEQ0244607 [iseXmlRpc.cpp:2144]
Apr 2 08:20:36 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::GetObjectByHSSAddress: no exists device object with address= IEQ0244986 [iseXmlRpc.cpp:2144]
Apr 2 08:20:40 homematic-ccu2 user.err rfd: IEQ0244242: Could not determine IP
Apr 2 08:20:58 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::GetObjectByHSSAddress: no exists device object with address= IEQ0244242 [iseXmlRpc.cpp:2144]
Apr 2 08:21:23 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::GetObjectByHSSAddress: no exists device object with address= IEQ0244986 [iseXmlRpc.cpp:2144]
Apr 2 08:21:24 homematic-ccu2 user.err rfd: IEQ0244986: Could not determine IP
Apr 2 08:21:24 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::GetObjectByHSSAddress: no exists device object with address= IEQ0244607 [iseXmlRpc.cpp:2144]
Apr 2 08:21:26 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::GetObjectByHSSAddress: no exists device object with address= IEQ0244242 [iseXmlRpc.cpp:2144]
Apr 2 08:21:26 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::GetObjectByHSSAddress: no exists device object with address= IEQ0244607 [iseXmlRpc.cpp:2144]
Apr 2 08:21:28 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::GetObjectByHSSAddress: no exists device object with address= IEQ0244242 [iseXmlRpc.cpp:2144]
Apr 2 08:21:41 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::GetObjectByHSSAddress: no exists device object with address= IEQ0244986 [iseXmlRpc.cpp:2144]
Apr 2 08:22:30 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::GetObjectByHSSAddress: no exists device object with address= IEQ0244986 [iseXmlRpc.cpp:2144]
Apr 2 08:22:31 homematic-ccu2 user.err rfd: IEQ0244986: Could not determine IP
Apr 2 08:22:36 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::GetObjectByHSSAddress: no exists device object with address= IEQ0244607 [iseXmlRpc.cpp:2144]
Apr 2 08:22:36 homematic-ccu2 user.err rfd: IEQ0244607: Could not determine IP
Apr 2 08:22:36 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::GetObjectByHSSAddress: no exists device object with address= IEQ0244242 [iseXmlRpc.cpp:2144]
Diese IEQ0244... Geräte sind meine 3 LAN Adapter. Bei der CCU1 hatte ich nie Probleme damit.

Es sieht so aus, als ob die LAN-Adapter rebellieren. "Einfach so", will ich natürlich nicht auf neue LAN Adapter wechseln. Im WEBUI finde ich keinen Hinweis auf Probleme. Was ist zu tun?

Gruß ABN
Zuletzt geändert von alchy am 09.04.2018, 08:19, insgesamt 1-mal geändert.
Grund: Code in Codetags posten

ABN
Beiträge: 2
Registriert: 03.04.2018, 19:38

Re: LAN Adapter erzeugen Fehlermeldungen auf CCU2

Beitrag von ABN » 07.04.2018, 20:00

Hallo,

ich habe alle LAN-Adapter gelöscht und neu komplett auch mit IP Adresse neu angelegt. Die CCU2 neu gestartet, alle LAN Adapter zeigen "verbunden".

Hier mal das komplette Logfile seit Neustart bis jetzt (... nur ein paar Minuten).

Die CCU2 ist gefühlt "lahm" geworden

Kann bitte jemand drüber schauen? - Die HM-LAN-CFG sagen dem WEB UI: "alles iO" und im Logfile ist alles voller Fehlermeldungen.

Code: Alles auswählen


***** messages *****
Apr  7 18:47:41 homematic-ccu2 syslog.info syslogd started: BusyBox v1.20.2
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: klogd started: BusyBox v1.20.2 (2018-01-15 15:55:20 CET)
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.000000] Booting Linux on physical CPU 0
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.000000] Initializing cgroup subsys cpu
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    0.000000] Linux version 3.4.11.ccu2 (jenkins@entw-build-10) (gcc version 4.6.1 (Sourcery CodeBench Lite 2011.09-70) ) #1 PREEMPT Mon Jan 15 16:24:50 CET 2018
Apr  7 18:47:41 homematic-ccu2 user.warn kernel: [    0.000000] CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
Apr  7 18:47:41 homematic-ccu2 user.warn kernel: [    0.000000] CPU: VIVT data cache, VIVT instruction cache
Apr  7 18:47:41 homematic-ccu2 user.warn kernel: [    0.000000] Machine: eQ-3 HomeMatic CCU2
Apr  7 18:47:41 homematic-ccu2 user.warn kernel: [    0.000000] Memory policy: ECC disabled, Data cache writeback
Apr  7 18:47:41 homematic-ccu2 user.debug kernel: [    0.000000] On node 0 totalpages: 65536
Apr  7 18:47:41 homematic-ccu2 user.debug kernel: [    0.000000] free_area_init_node: node 0, pgdat c03c42ec, node_mem_map c03f8000
Apr  7 18:47:41 homematic-ccu2 user.debug kernel: [    0.000000]   Normal zone: 512 pages used for memmap
Apr  7 18:47:41 homematic-ccu2 user.debug kernel: [    0.000000]   Normal zone: 0 pages reserved
Apr  7 18:47:41 homematic-ccu2 user.debug kernel: [    0.000000]   Normal zone: 65024 pages, LIFO batch:15
Apr  7 18:47:41 homematic-ccu2 user.debug kernel: [    0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
Apr  7 18:47:41 homematic-ccu2 user.debug kernel: [    0.000000] pcpu-alloc: [0] 0 
Apr  7 18:47:41 homematic-ccu2 user.warn kernel: [    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 65024
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    0.000000] Kernel command line: eQ3Mode=production console=ttyAMA0,115200 ubi.mtd=7 ubi.mtd=6 ro ip=none root=ubi0:root ubi.mtd=7 rootfstype=ubifs noinitrd mtdparts=gpmi-nand:1024k(fcb)ro,1024k(bbt),1024k(bootenv),1536k(boo
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.000000] allocated 524288 bytes of page_cgroup
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.000000] Memory: 256MB = 256MB total
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    0.000000] Memory: 255276k/255276k available, 6868k reserved, 0K highmem
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    0.000000] Virtual kernel memory layout:
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    0.000000]     vmalloc : 0xd0800000 - 0xff000000   ( 744 MB)
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    0.000000]     lowmem  : 0xc0000000 - 0xd0000000   ( 256 MB)
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    0.000000]     modules : 0xbf000000 - 0xc0000000   (  16 MB)
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    0.000000]       .text : 0xc0008000 - 0xc037d000   (3540 kB)
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    0.000000]       .init : 0xc037d000 - 0xc039a000   ( 116 kB)
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    0.000000]       .data : 0xc039a000 - 0xc03c4a20   ( 171 kB)
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    0.000000]        .bss : 0xc03c4a44 - 0xc03f77dc   ( 204 kB)
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.000000] SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.000000] NR_IRQS:304
Apr  7 18:47:41 homematic-ccu2 user.err kernel: [    0.000000] saif0_clk_set_rate: clock is gated
Apr  7 18:47:41 homematic-ccu2 user.err kernel: [    0.000000] saif1_clk_set_rate: clock is gated
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.000000] sched_clock: 32 bits at 100 Hz, resolution 10000000ns, wraps every 4294967286ms
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.000000] Console: colour dummy device 80x30
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.000000] Calibrating delay loop... 226.09 BogoMIPS (lpj=1130496)
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.070000] pid_max: default: 32768 minimum: 301
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.070000] Mount-cache hash table entries: 512
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.070000] Initializing cgroup subsys cpuacct
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.070000] Initializing cgroup subsys memory
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.070000] Initializing cgroup subsys devices
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.070000] Initializing cgroup subsys freezer
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.070000] CPU: Testing write buffer coherency: ok
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.070000] Setting up static identity map for 0x402b1198 - 0x402b11f0
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.070000] devtmpfs: initialized
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.080000] dummy: 
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.080000] NET: Registered protocol family 16
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.080000] gpiochip_add: registered GPIOs 0 to 31 on device: gpio-mxs.0
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.080000] gpiochip_add: registered GPIOs 32 to 63 on device: gpio-mxs.1
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.080000] gpiochip_add: registered GPIOs 64 to 95 on device: gpio-mxs.2
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.080000] gpiochip_add: registered GPIOs 96 to 127 on device: gpio-mxs.3
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.080000] gpiochip_add: registered GPIOs 128 to 159 on device: gpio-mxs.4
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.090000] Serial: AMBA PL011 UART driver
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.090000] duart: ttyAMA0 at MMIO 0x80074000 (irq = 47) is a PL011 rev2
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.100000] console [ttyAMA0] enabled
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.100000] mxs-usbphy mxs-usbphy.0: initialized usb phy
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.110000] mxs-usbphy mxs-usbphy.1: initialized usb phy
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.120000] bio: create slab <bio-0> at 0
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.130000] mxs-dma mxs-dma-apbh: initialized
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.140000] mxs-dma mxs-dma-apbx: initialized
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.140000] REG-3V3: 3300 mV normal 
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.150000] REG-1V8: 1800 mV normal 
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.150000] USB 5V: 5000 mV normal 
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.150000] VDDIO-SD: 3300 mV normal 
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.160000] Switching to clocksource mxs_timer
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.200000] NET: Registered protocol family 2
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.200000] IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.210000] TCP established hash table entries: 8192 (order: 4, 65536 bytes)
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.220000] TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.220000] TCP: Hash tables configured (established 8192 bind 8192)
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.230000] TCP: reno registered
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.230000] UDP hash table entries: 256 (order: 0, 4096 bytes)
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.240000] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.250000] NET: Registered protocol family 1
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.250000] RPC: Registered named UNIX socket transport module.
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.260000] RPC: Registered udp transport module.
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.260000] RPC: Registered tcp transport module.
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.270000] RPC: Registered tcp NFSv4.1 backchannel transport module.
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.280000] audit: initializing netlink socket (disabled)
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    0.280000] type=2000 audit(0.280:1): initialized
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.490000] fuse init (API version 7.18)
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.500000] msgmni has been set to 498
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.500000] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251)
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.510000] io scheduler noop registered (default)
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.520000] uart-pl011 duart: no DMA platform data
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.520000] mxs-auart.1: ttyAPP1 at MMIO 0x8006c000 (irq = 113) is a mxs-auart.1
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.530000] mxs-auart mxs-auart.1: Found APPUART 3.1.0
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.540000] ONFI param page 0 valid
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.540000] ONFI flash detected
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.550000] NAND device: Manufacturer ID: 0x01, Chip ID: 0xda (AMD S34ML02G1)
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    0.550000] Scanning device for bad blocks
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    0.960000] 8 cmdlinepart partitions found on MTD device gpmi-nand
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    0.970000] Creating 8 MTD partitions on "gpmi-nand":
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    0.970000] 0x000000000000-0x000000100000 : "fcb"
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    0.980000] 0x000000100000-0x000000200000 : "bbt"
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    0.990000] 0x000000200000-0x000000300000 : "bootenv"
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    1.000000] 0x000000300000-0x000000480000 : "bootstream0"
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    1.010000] 0x000000480000-0x000000a80000 : "bootstream1"
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    1.020000] 0x000000a80000-0x000000e80000 : "kernel"
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    1.020000] 0x000000e80000-0x000003e80000 : "user"
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    1.030000] 0x000003e80000-0x000010000000 : "root"
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    1.040000] GPMI NAND driver registered. (IMX)
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    1.050000] UBI: attaching mtd7 to ubi0
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    1.050000] UBI: physical eraseblock size:   131072 bytes (128 KiB)
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    1.060000] UBI: logical eraseblock size:    126976 bytes
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    1.060000] UBI: smallest flash I/O unit:    2048
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    1.070000] UBI: VID header offset:          2048 (aligned 2048)
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    1.070000] UBI: data offset:                4096
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    2.770000] UBI: max. sequence number:       2
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    2.790000] UBI: attached mtd7 to ubi0
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    2.800000] UBI: MTD device name:            "root"
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    2.800000] UBI: MTD device size:            193 MiB
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    2.810000] UBI: number of good PEBs:        1548
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    2.810000] UBI: number of bad PEBs:         0
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    2.820000] UBI: number of corrupted PEBs:   0
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    2.820000] UBI: max. allowed volumes:       128
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    2.830000] UBI: wear-leveling threshold:    4096
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    2.830000] UBI: number of internal volumes: 1
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    2.840000] UBI: number of user volumes:     1
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    2.840000] UBI: available PEBs:             0
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    2.850000] UBI: total number of reserved PEBs: 1548
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    2.850000] UBI: number of PEBs reserved for bad PEB handling: 15
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    2.860000] UBI: max/mean erase counter: 3/1
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    2.860000] UBI: image sequence number:  803677353
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    2.870000] UBI: background thread "ubi_bgt0d" started, PID 32
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    2.870000] UBI: attaching mtd6 to ubi1
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    2.880000] UBI: physical eraseblock size:   131072 bytes (128 KiB)
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    2.880000] UBI: logical eraseblock size:    126976 bytes
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    2.890000] UBI: smallest flash I/O unit:    2048
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    2.890000] UBI: VID header offset:          2048 (aligned 2048)
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    2.900000] UBI: data offset:                4096
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    3.320000] UBI: max. sequence number:       1275
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    3.340000] UBI: attached mtd6 to ubi1
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    3.350000] UBI: MTD device name:            "user"
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    3.350000] UBI: MTD device size:            48 MiB
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    3.360000] UBI: number of good PEBs:        384
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    3.360000] UBI: number of bad PEBs:         0
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    3.370000] UBI: number of corrupted PEBs:   0
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    3.370000] UBI: max. allowed volumes:       128
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    3.370000] UBI: wear-leveling threshold:    4096
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    3.380000] UBI: number of internal volumes: 1
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    3.380000] UBI: number of user volumes:     1
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    3.390000] UBI: available PEBs:             0
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    3.390000] UBI: total number of reserved PEBs: 384
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    3.400000] UBI: number of PEBs reserved for bad PEB handling: 3
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    3.400000] UBI: max/mean erase counter: 6/3
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    3.410000] UBI: image sequence number:  1076046500
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    3.410000] UBI: background thread "ubi_bgt1d" started, PID 33
Apr  7 18:47:41 homematic-ccu2 user.err kernel: [    3.420000] UBI error: ubi_init: cannot attach mtd7
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    3.450000] fec_enet_mii_bus: probed
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    3.460000] rtc-rs5c372 0-0032: rs5c372a found, 24hr, driver version 0.6
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    3.480000] rtc-rs5c372 0-0032: rtc core: registered rtc-rs5c372 as rtc0
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    3.480000] stmp3xxx-rtc stmp3xxx-rtc: rtc core: registered stmp3xxx-rtc as rtc1
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    3.490000] watchdog watchdog0: watchdog initialized, 115 seconds remaining
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    3.500000] cpuidle: using governor ladder
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    3.500000] cpuidle: using governor menu
Apr  7 18:47:41 homematic-ccu2 user.debug kernel: [    3.510000] Registered led device: power
Apr  7 18:47:41 homematic-ccu2 user.debug kernel: [    3.510000] Registered led device: internet
Apr  7 18:47:41 homematic-ccu2 user.debug kernel: [    3.510000] Registered led device: info
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    3.510000] NET: Registered protocol family 17
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    3.520000] registered taskstats version 1
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    3.530000] rtc-rs5c372 0-0032: setting system clock to 2018-04-07 16:47:38 UTC (1523119658)
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    3.670000] UBIFS: mounted UBI device 0, volume 0, name "root"
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    3.680000] UBIFS: mounted read-only
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    3.680000] UBIFS: file system size:   192749568 bytes (188232 KiB, 183 MiB, 1518 LEBs)
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    3.690000] UBIFS: journal size:       9023488 bytes (8812 KiB, 8 MiB, 72 LEBs)
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    3.700000] UBIFS: media format:       w4/r0 (latest is w4/r0)
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    3.700000] UBIFS: default compressor: lzo
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    3.710000] UBIFS: reserved for root:  0 bytes (0 KiB)
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    3.710000] VFS: Mounted root (ubifs filesystem) readonly on device 0:12.
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    3.730000] devtmpfs: mounted
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    3.730000] Freeing init memory: 116K
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    4.290000] UBIFS: mounted UBI device 1, volume 0, name "user"
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    4.300000] UBIFS: file system size:   46473216 bytes (45384 KiB, 44 MiB, 366 LEBs)
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    4.310000] UBIFS: journal size:       9023488 bytes (8812 KiB, 8 MiB, 72 LEBs)
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    4.310000] UBIFS: media format:       w4/r0 (latest is w4/r0)
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    4.320000] UBIFS: default compressor: lzo
Apr  7 18:47:41 homematic-ccu2 user.notice kernel: [    4.320000] UBIFS: reserved for root:  0 bytes (0 KiB)
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    4.990000] eq3spi eq3spi.0: master is unqueued, this is deprecated
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    5.070000] input: gpio-keys as /devices/platform/gpio-keys/input/input0
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    5.120000] Freescale High-Speed USB SOC Device Controller driver (Apr 20, 2007)
Apr  7 18:47:41 homematic-ccu2 user.debug kernel: [    5.130000] mxs-usbphy mxs-usbphy.0: enabling gadget mode
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    5.200000] usb0: MAC 00:1a:22:00:05:87
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    5.210000] usb0: HOST MAC 00:1a:22:00:05:86
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    5.220000] g_multi gadget: Mass Storage Function, version: 2009/09/11
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    5.230000] g_multi gadget: Number of LUNs=1
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    5.230000]  lun0: LUN: read only CD-ROM file: /usr/share/eq3/install.iso
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    5.240000] g_multi gadget: Multifunction Composite Gadget
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    5.240000] g_multi gadget: g_multi ready
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    5.250000] fsl-usb2-udc: bind to driver g_multi
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    5.280000] tun: Universal TUN/TAP device driver, 1.6
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    5.290000] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    5.370000] usbcore: registered new interface driver usbfs
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    5.380000] usbcore: registered new interface driver hub
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    5.380000] usbcore: registered new device driver usb
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    5.410000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    5.410000] mxs-ehci mxs-ehci.1: initializing i.MX USB Controller
Apr  7 18:47:41 homematic-ccu2 user.debug kernel: [    5.430000] mxs-usbphy mxs-usbphy.1: enabling host mode
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    5.450000] mxs-ehci mxs-ehci.1: using regulator to control VBUS
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    5.450000] mxs-ehci mxs-ehci.1: Freescale On-Chip EHCI Host Controller
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    5.460000] mxs-ehci mxs-ehci.1: new USB bus registered, assigned bus number 1
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    5.500000] mxs-ehci mxs-ehci.1: irq 92, io mem 0x80090000
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    5.520000] mxs-ehci mxs-ehci.1: USB 2.0 started, EHCI 1.00
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    5.520000] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    5.530000] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    5.540000] usb usb1: Product: Freescale On-Chip EHCI Host Controller
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    5.540000] usb usb1: Manufacturer: Linux 3.4.11.ccu2 ehci_hcd
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    5.550000] usb usb1: SerialNumber: mxs-ehci.1
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    5.550000] hub 1-0:1.0: USB hub found
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    5.560000] hub 1-0:1.0: 1 port detected
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    5.590000] mxs-raw-auart mxs-raw-auart.0: Found raw APPUART 3.1.0
Apr  7 18:47:41 homematic-ccu2 user.info kernel: [    6.150000] ip_tables: (C) 2000-2006 Netfilter Core Team
Apr  7 18:47:41 homematic-ccu2 user.err kernel: 0>[    6.790000] udevd[115]: starting version 182
Apr  7 16:47:41 homematic-ccu2 daemon.err udevd[115]: specified group 'dialout' unknown
Apr  7 16:47:41 homematic-ccu2 daemon.err udevd[115]: specified group 'kmem' unknown
Apr  7 16:47:41 homematic-ccu2 daemon.err udevd[115]: specified group 'video' unknown
Apr  7 16:47:41 homematic-ccu2 daemon.err udevd[115]: specified group 'lp' unknown
Apr  7 16:47:41 homematic-ccu2 daemon.err udevd[115]: specified group 'floppy' unknown
Apr  7 16:47:41 homematic-ccu2 daemon.err udevd[115]: specified group 'cdrom' unknown
Apr  7 16:47:41 homematic-ccu2 daemon.err udevd[115]: specified group 'tape' unknown
Apr  7 18:47:42 homematic-ccu2 user.info kernel: [    8.000000] mxs-mmc mxs-mmc.0: using regulator to control VDDIO-SD
Apr  7 18:47:43 homematic-ccu2 user.info kernel: [    8.030000] mxs-mmc mxs-mmc.0: initialized
Apr  7 18:47:43 homematic-ccu2 daemon.info udhcpd[140]: udhcpd (v1.20.2) started
Apr  7 18:47:43 homematic-ccu2 daemon.err udhcpd[140]: can't open '/var/lib/misc/udhcpd.leases': No such file or directory
Apr  7 16:47:44 homematic-ccu2 daemon.info ifplugd(eth0)[189]: ifplugd 0.28 initializing.
Apr  7 18:47:44 homematic-ccu2 user.info kernel: [    9.590000] eth0: Freescale FEC PHY driver [SMSC LAN8710/LAN8720] (mii_bus:phy_addr=imx28-fec-1:00, irq=185)
Apr  7 16:47:44 homematic-ccu2 daemon.info ifplugd(eth0)[189]: Using interface eth0/00:1A:22:0B:DC:39 with driver <fec> (version: Revision: 1.0)
Apr  7 16:47:44 homematic-ccu2 daemon.info ifplugd(eth0)[189]: Using detection mode: SIOCETHTOOL
Apr  7 16:47:44 homematic-ccu2 daemon.info ifplugd(eth0)[189]: Initialization complete, link beat not detected.
Apr  7 18:47:45 homematic-ccu2 user.debug setclock: Try to get time from ptbtime1.ptb.de
Apr  7 18:47:45 homematic-ccu2 user.debug setclock: Sat Apr 7 18:47:45 CEST 2018
Apr  7 18:47:46 homematic-ccu2 user.info kernel: [   11.590000] PHY: imx28-fec-1:00 - Link is Up - 100/Full
Apr  7 16:47:46 homematic-ccu2 daemon.info ifplugd(eth0)[189]: Link beat detected.
Apr  7 16:47:47 homematic-ccu2 daemon.info ifplugd(eth0)[189]: Executing '/etc/ifplugd/ifplugd.action eth0 up'.
Apr  7 16:47:47 homematic-ccu2 daemon.warn ifplugd(eth0)[189]: client: net.ipv4.tcp_timestamps = 0
Apr  7 16:47:48 homematic-ccu2 daemon.warn ifplugd(eth0)[189]: client: eth0 carrier detected
Apr  7 16:47:48 homematic-ccu2 daemon.info ifplugd(eth0)[189]: Program executed successfully.
Apr  7 16:47:49 homematic-ccu2 user.info logger: Updating RF Lan Gateway Coprocessor Firmware
Apr  7 16:47:49 homematic-ccu2 user.debug update-coprocessor: firmware filename is: coprocessor_update_hm_only.eq3
Apr  7 16:47:49 homematic-ccu2 user.info logger: Updating RF Lan Gateway Firmware
Apr  7 16:47:49 homematic-ccu2 user.info update-lgw-firmware: No gateway found in config file /etc/config/rfd.conf
Apr  7 16:47:49 homematic-ccu2 user.info logger: Updating Wired Lan Gateway Firmware
Apr  7 16:47:49 homematic-ccu2 user.info update-lgw-firmware: No gateway found in config file /etc/config/hs485d.conf
Apr  7 18:47:55 homematic-ccu2 user.info update-coprocessor: Version: 2.8.6
Apr  7 18:47:55 homematic-ccu2 user.info update-coprocessor: No update necessary
Apr  7 18:47:56 homematic-ccu2 user.info kernel: [   21.270000] eq3loop: created slave ttyS0
Apr  7 18:47:56 homematic-ccu2 user.info kernel: [   21.280000] eq3loop: created slave mmd_bidcos
Apr  7 18:47:58 homematic-ccu2 user.info kernel: [   23.820000] eq3loop: eq3loop_open_slave() mmd_bidcos
Apr  7 18:48:02 homematic-ccu2 user.err rfd: IEQ0244607: Could not connect to host
Apr  7 18:48:45 homematic-ccu2 user.debug setclock: Try to get time from ptbtime1.ptb.de
Apr  7 18:48:46 homematic-ccu2 user.debug setclock: Sat Apr 7 18:48:46 CEST 2018
Apr  7 18:49:33 homematic-ccu2 user.err rfd: IEQ0244242: Could not connect to host
Apr  7 18:49:47 homematic-ccu2 user.info kernel: [  132.300000] eq3loop: eq3loop_open_slave() ttyS0
Apr  7 18:49:47 homematic-ccu2 user.info kernel: [  132.320000] eq3loop: eq3loop_close_slave() ttyS0
Apr  7 18:49:47 homematic-ccu2 user.info kernel: [  132.450000] eq3loop: eq3loop_open_slave() ttyS0
Apr  7 18:49:47 homematic-ccu2 user.info kernel: [  132.450000] eq3loop: eq3loop_close_slave() ttyS0
Apr  7 18:49:48 homematic-ccu2 user.info kernel: [  132.650000] eq3loop: eq3loop_open_slave() ttyS0
Apr  7 18:49:48 homematic-ccu2 user.notice kernel: [  132.670000] eq3loop: eq3loop_ioctl_slave() ttyS0: unhandled ioctl 0x5459
Apr  7 18:49:48 homematic-ccu2 user.notice kernel: [  132.680000] eq3loop: eq3loop_ioctl_slave() ttyS0: unhandled ioctl 0x545D
Apr  7 18:50:04 homematic-ccu2 user.err rfd: IEQ0244607: Could not connect to host
Apr  7 18:50:56 homematic-ccu2 user.info : hss_lcd: Programm initialisiert.
Apr  7 16:50:56 homematic-ccu2 daemon.info init: starting pid 525, tty '/dev/ttyAMA0': '/sbin/getty -L ttyAMA0 115200 vt100 '
Apr  7 16:50:56 homematic-ccu2 daemon.info init: starting pid 526, tty '/dev/ttyGS0': '/sbin/getty -L ttyGS0 115200 vt100 '
Apr  7 18:51:17 homematic-ccu2 local0.err ReGaHss: Error: XmlRpc: Error in XmlRpcClient::writeRequest: write error (error 111). [iseXmlRpc.h:281]
Apr  7 18:51:17 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute failed; method =init Params = {"xmlrpc_bin://127.0.0.1:1999","1008"} result= nil [iseXmlRpc.cpp:2599]
Apr  7 18:51:17 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallInit: CallXmlrpcMethod failed [iseXmlRpc.cpp:1204]
Apr  7 18:51:17 homematic-ccu2 local0.err ReGaHss: Error: XmlRpcClientThread::ThreadFunction(): failed call init for interface=BidCos-Wired [iseRTHss.cpp:163]
Apr  7 18:51:17 homematic-ccu2 local0.err ReGaHss: Error: XmlRpc: Error in XmlRpcClient::writeRequest: write error (error 111). [iseXmlRpc.h:281]
Apr  7 18:51:17 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute failed; method =init Params = {"xmlrpc_bin://127.0.0.1:1999","1009"} result= nil [iseXmlRpc.cpp:2599]
Apr  7 18:51:17 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallInit: CallXmlrpcMethod failed [iseXmlRpc.cpp:1204]
Apr  7 18:51:17 homematic-ccu2 local0.err ReGaHss: Error: XmlRpcClientThread::ThreadFunction(): failed call init for interface=System [iseRTHss.cpp:163]
Apr  7 18:51:19 homematic-ccu2 user.err rfd: RFPhysicalDataInterfaceCommand::GetData SendFrame failed for LEVEL_GET
Apr  7 18:51:19 homematic-ccu2 user.err rfd: HSSParameter::GetValue() id=ENERGY_COUNTER failed getting physical value.
Apr  7 18:51:19 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"OEQ0630846:2","ENERGY_COUNTER"} result= [faultCode:-1,faultString:"Failure"] [iseXmlRpc.cpp:2605]
Apr  7 18:51:19 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432]
Apr  7 18:51:19 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0.000000 [iseDOMdpHSS.cpp:130]
Apr  7 18:51:21 homematic-ccu2 user.err rfd: RFPhysicalDataInterfaceCommand::GetData SendFrame failed for LEVEL_GET
Apr  7 18:51:21 homematic-ccu2 user.err rfd: HSSParameter::GetValue() id=BOOT failed getting physical value.
Apr  7 18:51:22 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"OEQ0630846:2","BOOT"} result= [faultCode:-1,faultString:"Failure"] [iseXmlRpc.cpp:2605]
Apr  7 18:51:22 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432]
Apr  7 18:51:22 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0 [iseDOMdpHSS.cpp:130]
Apr  7 18:52:31 homematic-ccu2 user.err rfd: IEQ0244607: Could not connect to host
Apr  7 18:52:31 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::GetObjectByHSSAddress: no exists device object with address= IEQ0244607 [iseXmlRpc.cpp:2144]
Apr  7 18:52:31 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::GetObjectByHSSAddress: no exists device object with address= IEQ0244607 [iseXmlRpc.cpp:2144]
Apr  7 18:52:32 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::GetObjectByHSSAddress: no exists device object with address= IEQ0244242 [iseXmlRpc.cpp:2144]
Apr  7 18:52:36 homematic-ccu2 user.err rfd: IEQ0244242: Could not connect to host
Apr  7 18:52:36 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::GetObjectByHSSAddress: no exists device object with address= IEQ0244242 [iseXmlRpc.cpp:2144]
Apr  7 18:52:48 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::GetObjectByHSSAddress: no exists device object with address= IEQ0244607 [iseXmlRpc.cpp:2144]
Apr  7 18:52:48 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::GetObjectByHSSAddress: no exists device object with address= IEQ0244607 [iseXmlRpc.cpp:2144]
Apr  7 18:52:53 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::GetObjectByHSSAddress: no exists device object with address= IEQ0244242 [iseXmlRpc.cpp:2144]
Apr  7 18:53:07 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::GetObjectByHSSAddress: no exists device object with address= IEQ0244607 [iseXmlRpc.cpp:2144]
Apr  7 18:54:03 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::GetObjectByHSSAddress: no exists device object with address= IEQ0244242 [iseXmlRpc.cpp:2144]
Apr  7 18:54:04 homematic-ccu2 user.err rfd: IEQ0244242: Could not connect to host
Apr  7 18:54:04 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::GetObjectByHSSAddress: no exists device object with address= IEQ0244242 [iseXmlRpc.cpp:2144]
Apr  7 18:54:27 homematic-ccu2 user.err rfd: IEQ0244242: Timeout waiting for initialization vector message
Apr  7 18:54:27 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::GetObjectByHSSAddress: no exists device object with address= IEQ0244242 [iseXmlRpc.cpp:2144]
Apr  7 18:54:45 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::GetObjectByHSSAddress: no exists device object with address= IEQ0244242 [iseXmlRpc.cpp:2144]
Apr  7 18:57:59 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::GetObjectByHSSAddress: no exists device object with address= IEQ0244242 [iseXmlRpc.cpp:2144]
Apr  7 18:58:01 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::GetObjectByHSSAddress: no exists device object with address= IEQ0244607 [iseXmlRpc.cpp:2144]
Apr  7 18:58:02 homematic-ccu2 user.err rfd: HSSParameter::SetValue() 10.000000 Put failed
Apr  7 18:58:03 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::GetObjectByHSSAddress: no exists device object with address= IEQ0244986 [iseXmlRpc.cpp:2144]
Apr  7 18:58:04 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::GetObjectByHSSAddress: no exists device object with address= IEQ0244607 [iseXmlRpc.cpp:2144]
Apr  7 18:58:04 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::GetObjectByHSSAddress: no exists device object with address= IEQ0244242 [iseXmlRpc.cpp:2144]
Apr  7 18:58:05 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::GetObjectByHSSAddress: no exists device object with address= IEQ0244986 [iseXmlRpc.cpp:2144]
Apr  7 18:59:05 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::GetObjectByHSSAddress: no exists device object with address= IEQ0244986 [iseXmlRpc.cpp:2144]
Apr  7 18:59:12 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::GetObjectByHSSAddress: no exists device object with address= IEQ0244242 [iseXmlRpc.cpp:2144]
Apr  7 18:59:12 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::GetObjectByHSSAddress: no exists device object with address= IEQ0244607 [iseXmlRpc.cpp:2144]
Apr  7 18:59:14 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::GetObjectByHSSAddress: no exists device object with address= IEQ0244242 [iseXmlRpc.cpp:2144]
Apr  7 18:59:14 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::GetObjectByHSSAddress: no exists device object with address= IEQ0244986 [iseXmlRpc.cpp:2144]
Apr  7 18:59:14 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::GetObjectByHSSAddress: no exists device object with address= IEQ0244607 [iseXmlRpc.cpp:2144]
Apr  7 19:08:08 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::GetObjectByHSSAddress: no exists device object with address= IEQ0244242 [iseXmlRpc.cpp:2144]
Apr  7 19:08:09 homematic-ccu2 user.err rfd: IEQ0244242: Could not connect to host
Apr  7 19:08:09 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::GetObjectByHSSAddress: no exists device object with address= IEQ0244242 [iseXmlRpc.cpp:2144]
Apr  7 19:08:35 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::GetObjectByHSSAddress: no exists device object with address= IEQ0244242 [iseXmlRpc.cpp:2144]
Apr  7 19:21:33 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::GetObjectByHSSAddress: no exists device object with address= IEQ0244242 [iseXmlRpc.cpp:2144]
Apr  7 19:21:36 homematic-ccu2 user.err rfd: IEQ0244242: Could not connect to host
Apr  7 19:21:36 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::GetObjectByHSSAddress: no exists device object with address= IEQ0244242 [iseXmlRpc.cpp:2144]
Apr  7 19:21:54 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::GetObjectByHSSAddress: no exists device object with address= IEQ0244242 [iseXmlRpc.cpp:2144]
Apr  7 19:26:02 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::GetObjectByHSSAddress: no exists device object with address= IEQ0244607 [iseXmlRpc.cpp:2144]
Apr  7 19:26:05 homematic-ccu2 user.err rfd: IEQ0244607: Could not connect to host
Apr  7 19:26:05 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::GetObjectByHSSAddress: no exists device object with address= IEQ0244607 [iseXmlRpc.cpp:2144]
Apr  7 19:26:26 homematic-ccu2 user.err rfd: IEQ0244607: Timeout waiting for initialization vector message
Apr  7 19:26:26 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::GetObjectByHSSAddress: no exists device object with address= IEQ0244607 [iseXmlRpc.cpp:2144]
Apr  7 19:26:44 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::GetObjectByHSSAddress: no exists device object with address= IEQ0244607 [iseXmlRpc.cpp:2144]
Apr  7 19:36:00 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::GetObjectByHSSAddress: no exists device object with address= IEQ0244242 [iseXmlRpc.cpp:2144]
Apr  7 19:36:02 homematic-ccu2 user.err rfd: IEQ0244242: Could not connect to host
Apr  7 19:36:02 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::GetObjectByHSSAddress: no exists device object with address= IEQ0244242 [iseXmlRpc.cpp:2144]
Apr  7 19:36:20 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::GetObjectByHSSAddress: no exists device object with address= IEQ0244242 [iseXmlRpc.cpp:2144]
Apr  7 19:36:21 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::GetObjectByHSSAddress: no exists device object with address= IEQ0244242 [iseXmlRpc.cpp:2144]
Apr  7 19:36:39 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::GetObjectByHSSAddress: no exists device object with address= IEQ0244242 [iseXmlRpc.cpp:2144]


***** hmserver.log *****
Apr 7 18:48:35 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] @GenericFactory 
Apr 7 18:48:36 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] creating instance of HMServerConfiguration with no-arg constructor 
Apr 7 18:49:23 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [HMIPTRXWriterWorker] (1) *worker 
Apr 7 18:49:23 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [KeyServerWorker] (1) *worker 
Apr 7 18:49:23 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [KryoPersistenceWorker] (1) *worker 
Apr 7 18:49:23 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [TransactionSubsystemHandler] (1) *worker 
Apr 7 18:49:23 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [FirmwareLoaderFileSystem] (1) *worker 
Apr 7 18:49:23 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerPersistentDataLoader] (1)  
Apr 7 18:49:23 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerAdapterInitialization] (1)  
Apr 7 18:49:23 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [BackendCommandHandler] (1)  
Apr 7 18:49:23 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceInclusionAcceptHandler] (1)  
Apr 7 18:49:23 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [IncomingHMIPFrameHandler] (1)  
Apr 7 18:49:23 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceBackgroundUpdateSubsystem] (1)  
Apr 7 18:49:23 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceInclusionDefaultConfigurationChanger] (1)  
Apr 7 18:49:23 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [CyclicSmokeDetectorAwakening] (1)  
Apr 7 18:49:23 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerFirmwareUpdateInitialization] (1)  
Apr 7 18:49:23 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyNotificationHandler] (1) *worker 
Apr 7 18:49:23 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyAPIWorker] (1) *worker 
Apr 7 18:49:23 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyBackendNotificationHandler] (3) *worker 
Apr 7 18:49:23 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyBlindLevelCorrectionHandler] (1) *worker 
Apr 7 18:49:23 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyInitializion] (1)  
Apr 7 18:49:23 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: deploying 19 classes to Vert.x 
Apr 7 18:49:24 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: 19 VertxDeployers initialized 
Apr 7 18:49:28 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of CyclicSmokeDetectorAwakening succeeded (f321f20c-5c33-4b8e-b9ca-e9e7f2cf70c2) 
Apr 7 18:49:28 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of HMIPTRXWriterWorker succeeded (830f4410-f725-45b1-bc0a-b86acb850843) 
Apr 7 18:49:28 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of TransactionSubsystemHandler succeeded (f62888b2-475d-48e1-a5e2-3845f7d07c7c) 
Apr 7 18:49:28 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of DeviceInclusionDefaultConfigurationChanger succeeded (c97d91fa-4c36-4067-96a5-079431b3c5f7) 
Apr 7 18:49:28 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of LegacyBlindLevelCorrectionHandler succeeded (dff8312c-1900-447c-bd0b-1c62945672de) 
Apr 7 18:49:29 de.eq3.cbcs.server.core.vertx.KeyServerWorker ERROR [vert.x-worker-thread-1] Missing key server configuration parameter (Network.Key) for  mode: KEYSERVER_LOCAL 
Apr 7 18:49:29 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of KeyServerWorker succeeded (163ee646-5ecc-461a-b806-4946bbb78eb2) 
Apr 7 18:49:31 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of LocalServerPersistentDataLoader still not met - check deployment configuration  
Apr 7 18:49:31 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of KryoPersistenceWorker still not met - check deployment configuration  
Apr 7 18:49:31 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of LocalServerAdapterInitialization still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded]) 
Apr 7 18:49:31 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of FirmwareLoaderFileSystem still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded]) 
Apr 7 18:49:31 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of DeviceBackgroundUpdateSubsystem still not met - check deployment configuration  
Apr 7 18:49:31 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of BackendCommandHandler still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded]) 
Apr 7 18:49:31 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of DeviceInclusionAcceptHandler still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded]) 
Apr 7 18:49:31 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of IncomingHMIPFrameHandler still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded]) 
Apr 7 18:49:31 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of LegacyAPIWorker still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded]) 
Apr 7 18:49:31 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of LegacyBackendNotificationHandler still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded]) 
Apr 7 18:49:31 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of LegacyNotificationHandler still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded]) 
Apr 7 18:49:31 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of LocalServerFirmwareUpdateInitialization still not met - check deployment configuration  (still unfulfilled: [connector.open][firmware.update.subsystem.started][persistent.data.loaded]) 
Apr 7 18:49:31 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of LegacyInitializion still not met - check deployment configuration  (still unfulfilled: [connector.open][persistent.data.loaded]) 
Apr 7 18:49:38 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: long-lasting deployment, check deployment configuration - currently deployed 6 out of 19 
Apr 7 18:49:38 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of KryoPersistenceWorker still not met - check deployment configuration  
Apr 7 18:49:38 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of LocalServerPersistentDataLoader still not met - check deployment configuration  
Apr 7 18:49:38 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of LocalServerAdapterInitialization still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded]) 
Apr 7 18:49:38 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of FirmwareLoaderFileSystem still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded]) 
Apr 7 18:49:38 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of BackendCommandHandler still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded]) 
Apr 7 18:49:38 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of DeviceBackgroundUpdateSubsystem still not met - check deployment configuration  
Apr 7 18:49:38 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of IncomingHMIPFrameHandler still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded]) 
Apr 7 18:49:38 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of DeviceInclusionAcceptHandler still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded]) 
Apr 7 18:49:38 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of LegacyAPIWorker still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded]) 
Apr 7 18:49:38 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of LegacyBackendNotificationHandler still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded]) 
Apr 7 18:49:38 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of LegacyNotificationHandler still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded]) 
Apr 7 18:49:38 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of LocalServerFirmwareUpdateInitialization still not met - check deployment configuration  (still unfulfilled: [connector.open][firmware.update.subsystem.started][persistent.data.loaded]) 
Apr 7 18:49:38 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of LegacyInitializion still not met - check deployment configuration  (still unfulfilled: [connector.open][persistent.data.loaded]) 
Apr 7 18:49:40 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of DeviceBackgroundUpdateSubsystem succeeded (c4bbb74d-8d0b-4f43-a2ca-5ba661b6a274) 
Apr 7 18:49:42 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of KryoPersistenceWorker succeeded (c9b7ce8f-2c6f-4ea2-a4be-ec31c97a9699) 
Apr 7 18:49:42 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of LocalServerPersistentDataLoader succeeded (f70a7688-f433-4a5a-848c-a482c8be964f) 
Apr 7 18:49:45 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of LocalServerAdapterInitialization still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded]) 
Apr 7 18:49:45 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of FirmwareLoaderFileSystem still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded]) 
Apr 7 18:49:45 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of BackendCommandHandler still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded]) 
Apr 7 18:49:45 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of IncomingHMIPFrameHandler still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded]) 
Apr 7 18:49:45 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of DeviceInclusionAcceptHandler still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded]) 
Apr 7 18:49:45 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of LegacyNotificationHandler still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded]) 
Apr 7 18:49:45 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of LocalServerFirmwareUpdateInitialization still not met - check deployment configuration  (still unfulfilled: [connector.open]) 
Apr 7 18:49:45 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of LegacyBackendNotificationHandler still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded]) 
Apr 7 18:49:45 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of LegacyInitializion still not met - check deployment configuration  (still unfulfilled: [connector.open]) 
Apr 7 18:49:45 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of LegacyBackendNotificationHandler succeeded (93f8282f-20f7-4c45-91dc-8f684ea7268b) 
Apr 7 18:49:46 de.eq3.cbcs.server.core.otau.util.FirmwareLoaderFileSystem INFO  [vert.x-worker-thread-1] SYSTEM: Firmware update directory is set to /etc/config/firmware 
Apr 7 18:49:46 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of FirmwareLoaderFileSystem succeeded (0d85c122-7068-4662-91f5-1bc467d19883) 
Apr 7 18:49:46 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of DeviceInclusionAcceptHandler succeeded (4f485201-31c4-4a0d-8ff7-f9283b72e340) 
Apr 7 18:49:46 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of LegacyAPIWorker succeeded (24e6caee-b601-48a0-900a-e3ab828f7c58) 
Apr 7 18:49:48 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of LocalServerAdapterInitialization succeeded (ab2e16db-526b-4a25-9f5b-5aa5cf489a54) 
Apr 7 18:49:48 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of IncomingHMIPFrameHandler succeeded (f9eccca3-0e24-43a5-bf1b-e5ccc0e6b43a) 
Apr 7 18:49:48 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] TRX adapter state 1: HMIP_TRX_App 
Apr 7 18:49:48 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] TRX adapter application is already running 
Apr 7 18:49:48 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] No NWK, try to set address ... 
Apr 7 18:49:48 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Try to set radio address 12510567... 
Apr 7 18:49:48 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Set max send attempts for 3014F711A00003570998CA5E to 3 
Apr 7 18:49:48 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Try to get application version... 
Apr 7 18:49:48 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of LegacyNotificationHandler succeeded (d4c227b5-700d-4612-99eb-ebae5d639d2e) 
Apr 7 18:49:48 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of BackendCommandHandler succeeded (7869b3cb-16b3-4799-aef6-f23d8a1143d3) 
Apr 7 18:49:48 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Application version 2.8.6 
Apr 7 18:49:48 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Bootloader version 1.0.5 
Apr 7 18:49:48 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] hmos version 1.20.3 
Apr 7 18:49:48 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] MCU type: ATmega644pa_AVR 
Apr 7 18:49:48 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Duty Cycle: 1.0 
Apr 7 18:49:48 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] set DutyCycle limit to ffffffc8 
Apr 7 18:49:49 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Set Duty Cycle Limit 
Apr 7 18:49:49 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Current Security Counter: 12715520 
Apr 7 18:49:49 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Update security counter to calculation: 12719853 
Apr 7 18:49:50 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] TRX adapter has 1 link partners 
Apr 7 18:49:51 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Adapter with Access Point id 3014F711A00003570998CA5E initialized 
Apr 7 18:49:51 de.eq3.cbcs.server.local.base.internal.LocalServerAdapterInitialization INFO  [Thread-6] HMIPTRXInitialResponseListener said that Adapter was initialized 
Apr 7 18:49:52 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: long-lasting deployment, check deployment configuration - currently deployed 17 out of 19 
Apr 7 18:49:52 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of LocalServerFirmwareUpdateInitialization still not met - check deployment configuration  (still unfulfilled: [connector.open]) 
Apr 7 18:49:52 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of LegacyInitializion succeeded (14354ed6-c2f0-48fb-b0aa-44f8e8064a40) 
Apr 7 18:49:52 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of LocalServerFirmwareUpdateInitialization succeeded (186b4034-65d8-496d-be23-cad6dd17d41a) 
Apr 7 18:49:52 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: initial deployment complete _____________________________________________________ 
Apr 7 18:49:52 de.eq3.cbcs.server.core.otau.util.FirmwareLoaderFileSystem WARN  [vert.x-worker-thread-0] SYSTEM: Firmware update directory in config file is no valid directory: /etc/config/firmware 
Apr 7 18:49:52 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Checking all devices on all accesspoints for updates 
Apr 7 18:49:52 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: There are 0 APs queued with updatable devices 
Apr 7 18:49:56 de.eq3.ccu.server.HMServer INFO  [Thread-2] Default MaxEventLoopExecuteTime: 2000000000 
Apr 7 18:49:56 de.eq3.ccu.server.HMServer INFO  [Thread-2] Default BlockedThreadCheckInterval: 1000 
Apr 7 18:49:56 de.eq3.ccu.server.HMServer INFO  [Thread-2] Default MaxWorkerExecuteTime: 60000000000 
Apr 7 18:49:56 de.eq3.ccu.server.HMServer INFO  [Thread-2] Default EventLoopPoolSize: 2 
Apr 7 18:49:57 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [BackendWorker] (1) *worker 
Apr 7 18:49:57 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [GroupRequestWorker] (1) *worker 
Apr 7 18:49:57 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [DiagramRequestWorker] (1) *worker 
Apr 7 18:49:57 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [StorageRequestWorker] (1) *worker 
Apr 7 18:49:57 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [DeviceFirmwareRequestWorker] (1) *worker 
Apr 7 18:49:57 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [EnergyPriceRequestWorker] (1) *worker 
Apr 7 18:49:57 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [CouplingRequestWorker] (1) *worker 
Apr 7 18:49:57 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: deploying 7 classes to Vert.x 
Apr 7 18:49:57 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: 7 VertxDeployers initialized 
Apr 7 18:49:57 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of BackendWorker succeeded (212bc96d-e1b1-497a-ba6c-f0a1aa5de05a) 
Apr 7 18:49:57 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of StorageRequestWorker succeeded (9874ef74-969a-41cc-b6b1-512b42f52339) 
Apr 7 18:49:58 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of CouplingRequestWorker succeeded (140db81e-0ac3-4ae8-8235-9c6bad82e81b) 
Apr 7 18:49:58 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of EnergyPriceRequestWorker succeeded (7fc33a1e-c101-4548-bdc6-ca60d129b52e) 
Apr 7 18:50:01 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of DiagramRequestWorker succeeded (7cc359b0-3b84-41d1-a1a4-ac01d70f2b3a) 
Apr 7 18:50:01 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of GroupRequestWorker succeeded (437a101f-50de-49ba-ae08-6ef420db1351) 
Apr 7 18:50:01 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of DeviceFirmwareRequestWorker succeeded (7bdb3461-03c0-42e7-b1a9-fc435044ffc7) 
Apr 7 18:50:01 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: initial deployment complete _____________________________________________________ 
Apr 7 18:50:02 de.eq3.ccu.server.HMServer INFO  [Thread-2] Starting HMServer at 127.0.0.1:9292 
Apr 7 18:50:02 de.eq3.ccu.server.HMServer INFO  [Thread-2] Read Configuration 
Apr 7 18:50:08 de.eq3.ccu.server.HMServer INFO  [Thread-2] Create Bidcos Dispatcher 
Apr 7 18:50:09 de.eq3.ccu.server.HMServer INFO  [Thread-2] InitBidCosCache 
Apr 7 18:50:24 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-4] (un)registerCallback on LegacyServiceHandler called from url: http://192.168.20.119:5544 
Apr 7 18:50:24 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-4] init finished 
Apr 7 18:50:25 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO  [vert.x-worker-thread-1] Added InterfaceId: IPS-192.168.20.119 
Apr 7 18:50:26 de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil INFO  [vert.x-worker-thread-1] updateDevicesForClient IPS-192.168.20.119 -> 3 device addresses will be added 
Apr 7 18:50:30 de.eq3.ccu.server.HMServer INFO  [Thread-2] Create groupDefinitionProvider 
Apr 7 18:50:39 de.eq3.ccu.server.HMServer INFO  [Thread-2] Create VirtualDeviceHolder 
Apr 7 18:50:39 de.eq3.ccu.server.HMServer INFO  [Thread-2] Create VirtualDeviceHandlerRega 
Apr 7 18:50:39 de.eq3.ccu.server.HMServer INFO  [Thread-2] Create GroupAdministrationService 
Apr 7 18:50:39 de.eq3.ccu.server.HMServer INFO  [Thread-2] Create GroupDeviceDispatcher 
Apr 7 18:50:39 de.eq3.ccu.server.HMServer INFO  [Thread-2] Create GroupDeviceHandler 
Apr 7 18:50:39 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-2] @GroupDeviceHandler - initializing... 
Apr 7 18:50:39 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-2] --> created groupDeviceDispatcher (GroupDeviceService to BidCoS (via Dispatcher)) 
Apr 7 18:50:39 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-2] --> created virtualDeviceHandler (GroupDeviceService to ReGa) 
Apr 7 18:50:39 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-2] --> got groupDefinitionProvider 
Apr 7 18:50:39 de.eq3.ccu.server.HMServer INFO  [Thread-2] Create BidCosGroupMemberProvider 
Apr 7 18:50:40 de.eq3.ccu.server.HMServer INFO  [Thread-2] Init groupAdministrationService 
Apr 7 18:50:40 de.eq3.ccu.server.HMServer INFO  [Thread-2] Init Virtual OS Device 
Apr 7 18:50:40 de.eq3.ccu.server.HMServer INFO  [Thread-2] Init ESHLight Bridge 
Apr 7 18:50:49 de.eq3.ccu.server.HMServer INFO  [Thread-2] Create RrdDatalogging 
Apr 7 18:50:49 de.eq3.ccu.server.HMServer INFO  [Thread-2] Create MeasurementService 
Apr 7 18:50:50 de.eq3.ccu.server.HMServer INFO  [Thread-2] Init MeasurementService 
Apr 7 18:50:50 de.eq3.ccu.server.HMServer INFO  [Thread-2] Create HTTP Server 
Apr 7 18:50:51 de.eq3.ccu.server.HMServer INFO  [Thread-2] Create BidCos context and start handler 
Apr 7 18:50:51 de.eq3.ccu.server.HMServer INFO  [Thread-2] Create group context and start handler 
Apr 7 18:50:51 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:9292/bidcos 
Apr 7 18:50:51 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO  [vert.x-worker-thread-0] Added InterfaceId: HmIP-RF_java 
Apr 7 18:50:51 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-2] init finished 
Apr 7 18:50:52 de.eq3.ccu.server.HMServer INFO  [Thread-2] Starting HMServer done 
Apr 7 18:50:52 de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil INFO  [vert.x-worker-thread-0] updateDevicesForClient HmIP-RF_java -> 3 device addresses will be added 
Apr 7 18:51:17 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-1] (un)registerCallback on VirtualDeviceHandlerRega called from url: xmlrpc_bin://127.0.0.1:1999 
Apr 7 18:51:17 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-1] Added InterfaceId: 2802 
Apr 7 18:51:17 de.eq3.ccu.virtualdevice.service.internal.rega.BackendWorker INFO  [vert.x-worker-thread-7] Execute BackendCommand: de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand 
Apr 7 18:51:27 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-1] (un)registerCallback on LegacyServiceHandler called from url: xmlrpc_bin://127.0.0.1:1999 
Apr 7 18:51:27 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-1] init finished 
Apr 7 18:51:28 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO  [vert.x-worker-thread-2] Added InterfaceId: 2803 

Zuletzt geändert von ABN am 08.04.2018, 00:06, insgesamt 1-mal geändert.

NickHM
Beiträge: 3729
Registriert: 23.09.2017, 12:04
Hat sich bedankt: 65 Mal
Danksagung erhalten: 119 Mal

Re: LAN Adapter erzeugen Fehlermeldungen auf CCU2

Beitrag von NickHM » 07.04.2018, 23:21

vor dem abschließenden

[/code]

fehlt die eckige Klammer. KannstDu das bitte einfügen?

Danke

Antworten

Zurück zu „HomeMatic Zentrale (CCU / CCU2 / CCU3 / Charly)“