Geräte anlernen klappt nicht

Virtualisierte CCU für Raspberry Pi und Clones

Moderator: Co-Administratoren

deimos
Beiträge: 1342
Registriert: 20.06.2017, 10:38
Wohnort: Leimersheim
Kontaktdaten:

Re: Geräte anlernen klappt nicht

Beitrag von deimos » 10.08.2018, 15:04

Hi,

bitte nach dem Einlegen der Batterien nicht den Alernknopf drucken.

Viele Grüße
Alex

Familienvater
Beiträge: 6289
Registriert: 31.12.2006, 16:18
Wohnort: Rhein-Main

Re: Geräte anlernen klappt nicht

Beitrag von Familienvater » 10.08.2018, 15:10

Hi,

und an das "Listen before Talk" bei HmIP denken. Wenn die Umgebung "voll" mit Störeinflüssen auf 868 Mhz ist, dann funkt zwar vielleicht der eine Partner, weil der weit genug weg von den Störungen ist, aber der andere "traut" sich nicht, irgendwas zu funken, weil der Rausch-Pegel immer zu hoch ist.


Der Familienvater

hannoi
Beiträge: 9
Registriert: 10.08.2018, 12:18

Re: Geräte anlernen klappt nicht

Beitrag von hannoi » 10.08.2018, 15:21

deimos hat geschrieben:
10.08.2018, 15:04
Hi,

bitte nach dem Einlegen der Batterien nicht den Alernknopf drucken.

Viele Grüße
Alex

Hatte nur die Batterien eingelegt wie du es beschrieben hattest.

An Störungen hatte ich auch schon gedacht aber ich wüsste nicht was auf der Frequenz 868 Mhz "funken" sollte. Die Geräte stehen quasi nur ein paar Meter auseinander - also der Pi und der Aktor.

Kann man das Funkmodul irgendwie anders testen ob es überhaupt tut quasi mit einer Art Dummy Aktor oder sowas ?

deimos
Beiträge: 1342
Registriert: 20.06.2017, 10:38
Wohnort: Leimersheim
Kontaktdaten:

Re: Geräte anlernen klappt nicht

Beitrag von deimos » 10.08.2018, 15:38

Hi,

leider kann man beim Funkmodul ohne echten Aktor nicht testen ob der Funk funktioniert (Gut, ich wüsste jetzt auch nicht wie das gehen soll, irgendwas anderes muss ja die Signale empfangen und den Empfang bestätigen, sonst weiß man maximal, dass das Funkmodul reden wollte).

Dadurch, dass das Funkmodul von piVCCU erkannt wird und die Seriennummer ausgibt, ist zumindest aber schon mal soweit getestet, dass der Bausatz korrekt zusammengelötet und aufgesteckt ist.

Hast du es mal versucht mit SGTIN und Key? Wenn das nicht klappt, wird es rein virtuell im Forum dann fast unmöglich, noch weiter zu helfen.

Viele Grüße
Alex

hannoi
Beiträge: 9
Registriert: 10.08.2018, 12:18

Re: Geräte anlernen klappt nicht

Beitrag von hannoi » 10.08.2018, 15:43

Also auch wieder Batterien raus, KEY und SGTIN eintragen, Button drücken und Batterien rein und warten ? Oder Anlernknopf am Aktor?

Hast schon recht, ohne echte Gegenstelle ist es schwierig mit einem Test, hab dummerweise auch bisher nur dieses eine Homematic Gerät...sonst hätte ich es auch mit einem anderen Teil probiert.

Danke aber trotzdem für die Unterstützung.

deimos
Beiträge: 1342
Registriert: 20.06.2017, 10:38
Wohnort: Leimersheim
Kontaktdaten:

Re: Geräte anlernen klappt nicht

Beitrag von deimos » 10.08.2018, 15:52

Hi,

zu lange her, dass ich das mit SGTIN und Key machen musste.

Kannst sein, dass man erst die Batterien drin haben muss und dann in der CCU auf Anlernen geht oder ob das erst in der CCU auf Anlernen gehen muss und dann die Batterien reinmacht. Idealerweise probierst du beides aus.

Viele Grüße
Alex

Familienvater
Beiträge: 6289
Registriert: 31.12.2006, 16:18
Wohnort: Rhein-Main

Re: Geräte anlernen klappt nicht

Beitrag von Familienvater » 10.08.2018, 16:59

Hi,

mit HmIP habe ich es noch nicht wirklich getestet und die multimac-Ausschriften analysiert:
Wenn Du den Bidcos-RF in der WebUI auf "Alles loggen" stellst, und dann die virtuelle CCU sauber über die WebUI neu startest, sollte auch der multimacd (quasi die Protokoll-Weiche HM/HmIP) im "Debug-Modus" in das syslog schreiben, damit könnte man im syslog evtl. sehen, wenn vom Wandthermostat irgendwas empfangen wird. Habe das aber mit HmIP noch nie probiert, und bin auch nicht zu Hause, um das mal schnell zu testen. Wenn aber sonst KEINE eigenen HM-Funkpakete von anderen Installationen rumschwirren, dürfte das Log noch relativ sauber bleiben, nur wenn eine große Installation in der Nähe ist, dann kommen zumindest die fremden HM-Pakete auch im Log, dann wird es ggf. unübersichtlich.

Der Familienvater

hannoi
Beiträge: 9
Registriert: 10.08.2018, 12:18

Re: Geräte anlernen klappt nicht

Beitrag von hannoi » 10.08.2018, 19:57

Also mit dem Anlernen mit KEY und SGTIN hat nicht geklappt, weder Batterien raus und Anlernmodus starten noch mit dem Anlernknopf am Aktor, leider blinkt er wie wild Orange und am Ende einmal Rot, vermutlich weil er nichts findet.

Ich hatte vorher in der WebUI auf " alles loggen " gestellt, hier der Logauszug:

Code: Alles auswählen

***** messages *****
Aug 10 19:48:31 homematic-ccu2 syslog.info syslogd started: BusyBox v1.20.2
Aug 10 19:48:31 homematic-ccu2 user.notice kernel: klogd started: BusyBox v1.20.2 (2018-07-03 14:19:59 CEST)
Aug 10 17:48:34 homematic-ccu2 daemon.info ifplugd(eth0)[136]: ifplugd 0.28 initializing.
Aug 10 17:48:34 homematic-ccu2 daemon.info ifplugd(eth0)[136]: Using interface eth0/6A:C4:93:D1:C4:95 with driver <veth> (version: 1.0)
Aug 10 17:48:34 homematic-ccu2 daemon.info ifplugd(eth0)[136]: Using detection mode: SIOCETHTOOL
Aug 10 17:48:34 homematic-ccu2 daemon.info ifplugd(eth0)[136]: Initialization complete, link beat detected.
Aug 10 17:48:34 homematic-ccu2 daemon.warn ifplugd(eth0)[136]: Could not open /dev/tty, cannot beep.
Aug 10 17:48:34 homematic-ccu2 daemon.info ifplugd(eth0)[136]: Executing '/etc/ifplugd/ifplugd.action eth0 up'.
Aug 10 17:48:34 homematic-ccu2 daemon.warn ifplugd(eth0)[136]: client: net.ipv4.tcp_timestamps = 0
Aug 10 17:48:34 homematic-ccu2 daemon.warn ifplugd(eth0)[136]: client: udhcpc (v1.20.2) started
Aug 10 19:48:34 homematic-ccu2 user.debug setclock: Try to get time from ntp.homematic.com
Aug 10 19:48:34 homematic-ccu2 user.debug setclock: Fri Aug 10 19:48:34 CEST 2018
Aug 10 17:48:34 homematic-ccu2 daemon.warn ifplugd(eth0)[136]: client: Sending discover...
Aug 10 17:48:35 homematic-ccu2 daemon.warn ifplugd(eth0)[136]: client: Sending select for 192.168.2.76...
Aug 10 17:48:35 homematic-ccu2 daemon.warn ifplugd(eth0)[136]: client: Lease of 192.168.2.76 obtained, lease time 864000
Aug 10 17:48:35 homematic-ccu2 daemon.warn ifplugd(eth0)[136]: client: rm: can't remove '/var/etc/resolv.conf': No such file or directory
Aug 10 17:48:35 homematic-ccu2 daemon.warn ifplugd(eth0)[136]: client: udhcpc (v1.20.2) started
Aug 10 17:48:35 homematic-ccu2 daemon.warn ifplugd(eth0)[136]: client: Sending discover...
Aug 10 17:48:37 homematic-ccu2 daemon.warn ifplugd(eth0)[136]: client: Sending select for 192.168.2.76...
Aug 10 17:48:37 homematic-ccu2 daemon.warn ifplugd(eth0)[136]: client: Lease of 192.168.2.76 obtained, lease time 864000
Aug 10 17:48:37 homematic-ccu2 daemon.info ifplugd(eth0)[136]: Program executed successfully.
Aug 10 17:48:39 homematic-ccu2 user.info logger: Updating RF Lan Gateway Coprocessor Firmware
Aug 10 17:48:39 homematic-ccu2 user.debug update-coprocessor: firmware filename is: coprocessor_update_hm_only.eq3
Aug 10 17:48:39 homematic-ccu2 user.info logger: Updating RF Lan Gateway Firmware
Aug 10 17:48:39 homematic-ccu2 user.info update-lgw-firmware: No gateway found in config file /etc/config/rfd.conf
Aug 10 17:48:39 homematic-ccu2 user.info logger: Updating Wired Lan Gateway Firmware
Aug 10 17:48:39 homematic-ccu2 user.info update-lgw-firmware: No gateway found in config file /etc/config/hs485d.conf
Aug 10 17:48:39 homematic-ccu2 user.info logger: Checking if firmware Update is needed for HM-MOD-RPI-PCB
Aug 10 17:48:42 homematic-ccu2 user.info update-coprocessor: Version: 2.8.6
Aug 10 17:48:42 homematic-ccu2 user.info update-coprocessor: No update necessary
Aug 10 19:48:43 homematic-ccu2 user.debug multimac: FastMacResponder::ThreadFunction() started Id=265
Aug 10 19:48:43 homematic-ccu2 user.debug multimac: UpstreamCharConnection slave ttyS0 ThreadFunction() started Id=268
Aug 10 19:48:43 homematic-ccu2 user.debug multimac: SubsystemManager::ThreadFunction() started. Id=267
Aug 10 19:48:43 homematic-ccu2 user.debug multimac: MacController::ThreadFunction() started. Id=266
Aug 10 19:48:43 homematic-ccu2 user.debug multimac: C<: #0 COMMON IdentifyRequest
Aug 10 19:48:43 homematic-ccu2 user.debug multimac: C< @19843293: bin:FD 00 03 FE 00 01 14 1E
Aug 10 19:48:43 homematic-ccu2 user.debug multimac: Subsystem 1 ThreadFunction() started. Id=269
Aug 10 19:48:43 homematic-ccu2 user.debug multimac: UpstreamCharConnection slave mmd_bidcos ThreadFunction() started Id=270
Aug 10 19:48:43 homematic-ccu2 user.debug multimac: Subsystem 2 ThreadFunction() started. Id=271
Aug 10 19:48:44 homematic-ccu2 user.debug multimac: C<: #1 HmSystem Identify 
Aug 10 19:48:44 homematic-ccu2 user.debug multimac: C< @19844294: bin:FD 00 03 00 01 00 9E 03
Aug 10 19:48:44 homematic-ccu2 user.debug multimac: C> @19844296: #1 BOOTLOADER CMD=04  02 43 6F 5F 43 50 55 5F 42 4C
Aug 10 19:48:44 homematic-ccu2 user.info multimac: Legacy Bootloader detected. Starting application.
Aug 10 19:48:44 homematic-ccu2 user.debug multimac: C<: #2 HmSystem StartBootloader 
Aug 10 19:48:44 homematic-ccu2 user.debug multimac: C< @19844296: bin:FD 00 03 00 02 03 94 09
Aug 10 19:48:44 homematic-ccu2 user.debug multimac: C> @19844826: #2 BOOTLOADER CMD=04  01
Aug 10 19:48:44 homematic-ccu2 user.debug multimac: C> @19844867: #1 COMMON Identify DualCoPro_App
Aug 10 19:48:44 homematic-ccu2 user.info multimac: Copro application running.
Aug 10 19:48:44 homematic-ccu2 user.debug multimac: C<: #3 TRX GetVersion
Aug 10 19:48:44 homematic-ccu2 user.debug multimac: C< @19844867: bin:FD 00 03 01 03 02 12 18
Aug 10 19:48:44 homematic-ccu2 user.debug multimac: C> @19844970: #3 TRX Response Ack 02 08 06 01 00 03 01 14 03
Aug 10 19:48:44 homematic-ccu2 user.info multimac: Vapp=020806 Vbl=010003 Vhmos=011403
Aug 10 19:48:44 homematic-ccu2 user.debug multimac: C<: #4 COMMON GetSGTIN
Aug 10 19:48:44 homematic-ccu2 user.debug multimac: C< @19844970: bin:FD 00 03 FE 04 04 8C 03
Aug 10 19:48:44 homematic-ccu2 user.debug multimac: C> @19844975: #4 COMMON Response Ack 30 14 F7 11 A0 61 A7 D7 09 8E 23 51
Aug 10 19:48:44 homematic-ccu2 user.info multimac: SGTIN=30 14 F7 11 A0 61 A7 D7 09 8E 23 51
Aug 10 19:48:44 homematic-ccu2 user.debug multimac: C<: #5 LLMAC GetDefaultRfAddress
Aug 10 19:48:44 homematic-ccu2 user.debug multimac: C< @19844975: bin:FD 00 03 03 05 08 86 0F
Aug 10 19:48:44 homematic-ccu2 user.debug multimac: C> @19844978: #5 LLMAC Response ACK @22602: 58 4A 19
Aug 10 19:48:44 homematic-ccu2 user.info multimac: RF address=5786137
Aug 10 19:48:44 homematic-ccu2 user.debug multimac: C<: #6 LLMAC GetSerialNumber
Aug 10 19:48:44 homematic-ccu2 user.debug multimac: C< @19844978: bin:FD 00 03 03 06 07 8C 2D
Aug 10 19:48:44 homematic-ccu2 user.debug multimac: C> @19844982: #6 LLMAC Response ACK @20293: 4F 45 51 30 33 31 30 30 39 37
Aug 10 19:48:44 homematic-ccu2 user.info multimac: Serial Number=OEQ0310097
Aug 10 19:48:44 homematic-ccu2 user.debug multimac: C<: #7 LLMAC GetTimestamp
Aug 10 19:48:44 homematic-ccu2 user.debug multimac: C< @19844983: bin:FD 00 03 03 07 02 0A 30
Aug 10 19:48:44 homematic-ccu2 user.debug multimac: C> @19844986: #7 LLMAC Response ACK @131: 00 83
Aug 10 19:48:44 homematic-ccu2 user.info multimac: Timer=  131
Aug 10 19:48:47 homematic-ccu2 user.info rfd: BidCoS-Service started
Aug 10 19:48:47 homematic-ccu2 user.info rfd: XmlRpc Server is listening on TCP port 2001
Aug 10 19:48:47 homematic-ccu2 user.warn rfd: opendir(/etc/config/firmware//) failed
Aug 10 19:48:47 homematic-ccu2 user.debug multimac: UpstreamCharConnection slave device mmd_bidcos opened
Aug 10 19:48:47 homematic-ccu2 user.debug multimac: A<: #0 HmSystem Identify Co_CPU_App
Aug 10 19:48:47 homematic-ccu2 user.debug rfd: CCU2CommController::init() - Improved initialization.
Aug 10 19:48:47 homematic-ccu2 user.debug multimac: A>: #0 HmSystem Identify 
Aug 10 19:48:47 homematic-ccu2 user.debug multimac: A<: #0 HmSystem Response 02 43 6F 5F 43 50 55 5F 41 70 70
Aug 10 19:48:47 homematic-ccu2 user.debug rfd: CCU2CommController::improvedInit() - Coprocessor is in application.
Aug 10 19:48:47 homematic-ccu2 user.info kernel: [19847.389623] eq3loop: eq3loop_open_slave() mmd_bidcos
Aug 10 19:48:47 homematic-ccu2 user.debug multimac: A>: #1 HmSystem VersionRequest 
Aug 10 19:48:47 homematic-ccu2 user.debug multimac: A<: #1 HmSystem Response 02 01 00 03 02 08 06
Aug 10 19:48:47 homematic-ccu2 user.info rfd: CCU2CommController::init(): Coprocessor Bootloader Version is: 1.0.3
Aug 10 19:48:47 homematic-ccu2 user.info rfd: CCU2CommController::init(): Coprocessor Firmware Version is: 2.8.6
Aug 10 19:48:47 homematic-ccu2 user.debug multimac: A>: #2 HmSystem CsmaCaControl 00
Aug 10 19:48:47 homematic-ccu2 user.debug multimac: CSMA/CD off
Aug 10 19:48:47 homematic-ccu2 user.debug multimac: A<: #2 HmSystem Response 01
Aug 10 19:48:47 homematic-ccu2 user.info rfd: () CCU2CommController::setCSMACAEnabled(): CSMA/CA disabled.
Aug 10 19:48:47 homematic-ccu2 user.debug multimac: A>: #3 HmSystem GetSerialNumber 
Aug 10 19:48:47 homematic-ccu2 user.debug multimac: A<: #3 HmSystem Response 02 4F 45 51 30 33 31 30 30 39 37
Aug 10 19:48:47 homematic-ccu2 user.debug multimac: A>: #4 HmBidcos SetTime 5B 6D CF FF 04
Aug 10 19:48:47 homematic-ccu2 user.debug multimac: Time 1533923327 +02:00
Aug 10 19:48:47 homematic-ccu2 user.debug multimac: A<: #4 HmSystem Response 01
Aug 10 19:48:47 homematic-ccu2 user.debug rfd: Default interface is now OEQ0310097
Aug 10 19:48:47 homematic-ccu2 user.info rfd: Current AES key=0, previous AES key=0
Aug 10 19:48:47 homematic-ccu2 user.debug multimac: A>: #5 HmBidcos SetAesKey.cur (0) 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Aug 10 19:48:47 homematic-ccu2 user.debug multimac: A<: #5 HmBidcos Response 01
Aug 10 19:48:47 homematic-ccu2 user.debug rfd: (OEQ0310097) Response status: OK.
Aug 10 19:48:47 homematic-ccu2 user.debug rfd: CCU2BidcosRemoteInterface::StartInterface(): addr=58 4a 19 
Aug 10 19:48:47 homematic-ccu2 user.debug multimac: A>: #6 HmBidcos SetRfAddress 58 4A 19
Aug 10 19:48:47 homematic-ccu2 user.debug multimac: A<: #6 HmBidcos Response 01
Aug 10 19:48:47 homematic-ccu2 user.debug rfd: (OEQ0310097) Response status: OK.
Aug 10 19:48:47 homematic-ccu2 user.debug rfd: Device description rf_cmm.xml loaded (1)
Aug 10 19:48:47 homematic-ccu2 user.debug rfd: Device description rf_keymatic.xml loaded (2)
Aug 10 19:48:47 homematic-ccu2 user.debug rfd: Device description rf_resc_win_pcb_sc.xml loaded (3)
Aug 10 19:48:47 homematic-ccu2 user.debug rfd: Device description rf_sen_li.xml loaded (4)
Aug 10 19:48:47 homematic-ccu2 user.debug rfd: Device description rf_sec_sfa.xml loaded (5)
Aug 10 19:48:47 homematic-ccu2 user.debug rfd: Device description rf_tc_it_wm-w-eu.xml loaded (6)
Aug 10 19:48:47 homematic-ccu2 user.debug rfd: Device description rf_sen_db.xml loaded (7)
Aug 10 19:48:47 homematic-ccu2 user.debug rfd: Device description rf_dim_2t_644_le_v2_4.xml loaded (8)
Aug 10 19:48:47 homematic-ccu2 user.debug rfd: Device description rf_rc_12.xml loaded (9)
Aug 10 19:48:47 homematic-ccu2 user.debug rfd: Device description rf_sec_sd_2.xml loaded (10)
Aug 10 19:48:47 homematic-ccu2 user.debug rfd: Device description rf_es_tx_wm.xml loaded (11)
Aug 10 19:48:47 homematic-ccu2 user.debug rfd: Device description rf_rd_le_v1_3.xml loaded (12)
Aug 10 19:48:47 homematic-ccu2 user.debug rfd: Device description rf_4dis.xml loaded (13)
Aug 10 19:48:47 homematic-ccu2 user.debug rfd: Device description rf_wds_v1_0.xml loaded (14)
Aug 10 19:48:47 homematic-ccu2 user.debug rfd: Device description rf_tis_le_v1_0.xml loaded (15)
Aug 10 19:48:47 homematic-ccu2 user.debug rfd: Device description rf_wds40_th_i_2.xml loaded (16)
Aug 10 19:48:47 homematic-ccu2 user.debug rfd: Device description rf_em_8_bit.xml loaded (17)
Aug 10 19:48:48 homematic-ccu2 user.debug rfd: Device description rf_sec_sir_wm.xml loaded (18)
Aug 10 19:48:48 homematic-ccu2 user.debug rfd: Device description rf_cc_rt_dn.xml loaded (19)
Aug 10 19:48:48 homematic-ccu2 user.debug rfd: Device description rf_dim_1l_644.xml loaded (20)
Aug 10 19:48:48 homematic-ccu2 user.debug rfd: Device description rf_sec_mdir.xml loaded (21)
Aug 10 19:48:48 homematic-ccu2 user.debug rfd: Device description rf_s_8_ba.xml loaded (22)
Aug 10 19:48:48 homematic-ccu2 user.debug rfd: Device description rf_sc.xml loaded (23)
Aug 10 19:48:48 homematic-ccu2 user.debug rfd: Device description rf_bl_conf_644_e_v2_1.xml loaded (24)
Aug 10 19:48:48 homematic-ccu2 user.debug rfd: Device description rf_oligo_smart_iq.xml loaded (25)
Aug 10 19:48:48 homematic-ccu2 user.debug rfd: Device description rf_dim_1t_dr.xml loaded (26)
Aug 10 19:48:48 homematic-ccu2 user.debug rfd: Device description rf_ja_conf_644.xml loaded (27)
Aug 10 19:48:48 homematic-ccu2 user.debug rfd: Device description rf_sen_wa_od.xml loaded (28)
Aug 10 19:48:48 homematic-ccu2 user.debug rfd: Device description rf_bl_644.xml loaded (29)
Aug 10 19:48:48 homematic-ccu2 user.debug rfd: Device description rf_sec_sco.xml loaded (30)
Aug 10 19:48:48 homematic-ccu2 user.debug rfd: Device description rf_rc-key4-2.xml loaded (31)
Aug 10 19:48:48 homematic-ccu2 user.debug rfd: Device description rf_dis_ep_wm55.xml loaded (32)
Aug 10 19:48:48 homematic-ccu2 user.debug rfd: Device description rf_rc-sec4-2.xml loaded (33)
Aug 10 19:48:48 homematic-ccu2 user.debug rfd: Device description rf_rhs_le_v1_6.xml loaded (34)
Aug 10 19:48:48 homematic-ccu2 user.debug rfd: Device description rf_st_6_sh.xml loaded (35)
Aug 10 19:48:48 homematic-ccu2 user.debug rfd: Device description rf_dim_1l_644_le_v2_4.xml loaded (36)
Aug 10 19:48:48 homematic-ccu2 user.debug rfd: Device description rf_ou_led16_ge_v1_1.xml loaded (37)
Aug 10 19:48:48 homematic-ccu2 user.debug rfd: Device description rf_s_1conf_644_le_v2_1.xml loaded (38)
Aug 10 19:48:48 homematic-ccu2 user.debug rfd: Device description rf_sen_mdir.xml loaded (39)
Aug 10 19:48:48 homematic-ccu2 user.debug rfd: Device description rf_es_pmsw.xml loaded (40)
Aug 10 19:48:48 homematic-ccu2 user.debug rfd: Device description rf_pb-2.xml loaded (41)
Aug 10 19:48:48 homematic-ccu2 user.debug rfd: Device description rf_dim_1pwm_644_le_v2_4.xml loaded (42)
Aug 10 19:48:48 homematic-ccu2 user.debug rfd: Device description rf_bl.xml loaded (43)
Aug 10 19:48:49 homematic-ccu2 user.debug rfd: Device description rf_pb-2-wm55_le_v1_3.xml loaded (44)
Aug 10 19:48:49 homematic-ccu2 user.debug rfd: Device description rf_bl_le_v2_3.xml loaded (45)
Aug 10 19:48:49 homematic-ccu2 user.debug rfd: Device description rf_es_pmsw_le_v2_4.xml loaded (46)
Aug 10 19:48:49 homematic-ccu2 user.debug rfd: Device description rf_s_644.xml loaded (47)
Aug 10 19:48:49 homematic-ccu2 user.debug rfd: Device description rf_s_le_v2_3.xml loaded (48)
Aug 10 19:48:49 homematic-ccu2 user.debug rfd: Device description rf_swi.xml loaded (49)
Aug 10 19:48:49 homematic-ccu2 user.debug rfd: Device description rf_sen_mdir_v1_5.xml loaded (50)
Aug 10 19:48:49 homematic-ccu2 user.debug rfd: Device description rf_dim_1t_644_le_v2_4.xml loaded (51)
Aug 10 19:48:49 homematic-ccu2 user.debug rfd: Device description rf_dis_wm55.xml loaded (52)
Aug 10 19:48:49 homematic-ccu2 user.debug rfd: Device description rf_rc_dis.xml loaded (53)
Aug 10 19:48:49 homematic-ccu2 user.debug rfd: Device description rf_d_le_v1_7.xml loaded (54)
Aug 10 19:48:49 homematic-ccu2 user.debug rfd: Device description rf_rc_2_fm.xml loaded (55)
Aug 10 19:48:49 homematic-ccu2 user.debug rfd: Device description rf_central.xml loaded (56)
Aug 10 19:48:49 homematic-ccu2 user.debug rfd: Device description rf_sc_le_v1_6.xml loaded (57)
Aug 10 19:48:49 homematic-ccu2 user.debug rfd: Device description rf_rc-4-2.xml loaded (58)
Aug 10 19:48:49 homematic-ccu2 user.debug rfd: Device description rf_rep.xml loaded (59)
Aug 10 19:48:49 homematic-ccu2 user.debug rfd: Device description rf_ks550.xml loaded (60)
Aug 10 19:48:49 homematic-ccu2 user.debug rfd: Device description rf_ou_led16_le_v1_0.xml loaded (61)
Aug 10 19:48:49 homematic-ccu2 user.debug rfd: Device description rf_scd_v1_0.xml loaded (62)
Aug 10 19:48:49 homematic-ccu2 user.debug rfd: Device description rf_rhs_e_v1_7.xml loaded (63)
Aug 10 19:48:49 homematic-ccu2 user.debug rfd: Device description rf_dis_ep_wm55_le_v1_0.xml loaded (64)
Aug 10 19:48:49 homematic-ccu2 user.debug rfd: Device description rf_wds_v1_1.xml loaded (65)
Aug 10 19:48:49 homematic-ccu2 user.debug rfd: Device description rf_roto_wdf_solar.xml loaded (66)
Aug 10 19:48:49 homematic-ccu2 user.debug rfd: Device description rf_cc_tc.xml loaded (67)
Aug 10 19:48:49 homematic-ccu2 user.debug rfd: Device description rf_sec_mdir_v1_5.xml loaded (68)
Aug 10 19:48:49 homematic-ccu2 user.debug rfd: Device description rf_dim_1tconf_644.xml loaded (69)
Aug 10 19:48:49 homematic-ccu2 user.debug rfd: Device description rf_s_mega168.xml loaded (70)
Aug 10 19:48:49 homematic-ccu2 user.debug rfd: Device description rf_winmatic.xml loaded (71)
Aug 10 19:48:49 homematic-ccu2 user.debug rfd: Device description rf_pb-2-wm55_ge_v1_4.xml loaded (72)
Aug 10 19:48:49 homematic-ccu2 user.debug rfd: Device description rf_fs_ba.xml loaded (73)
Aug 10 19:48:49 homematic-ccu2 user.debug rfd: Device description rf_bl_conf_644.xml loaded (74)
Aug 10 19:48:49 homematic-ccu2 user.debug rfd: Device description rf_sen_ep.xml loaded (75)
Aug 10 19:48:50 homematic-ccu2 user.debug rfd: Device description rf_dw.xml loaded (76)
Aug 10 19:48:50 homematic-ccu2 user.debug rfd: Device description rf_rc-4-3_single_on.xml loaded (77)
Aug 10 19:48:50 homematic-ccu2 user.debug rfd: Device description rf_dim_2l_644.xml loaded (78)
Aug 10 19:48:50 homematic-ccu2 user.debug rfd: Device description rf_rhs.xml loaded (79)
Aug 10 19:48:50 homematic-ccu2 user.debug rfd: Device description rf_dim_2t_644.xml loaded (80)
Aug 10 19:48:50 homematic-ccu2 user.debug rfd: Device description rf_cc_tc_le_v1_9.xml loaded (81)
Aug 10 19:48:50 homematic-ccu2 user.debug rfd: Device description rf_ash550.xml loaded (82)
Aug 10 19:48:50 homematic-ccu2 user.debug rfd: Device description rf_d_le_v1_9.xml loaded (83)
Aug 10 19:48:50 homematic-ccu2 user.debug rfd: Device description rf_rgbw.xml loaded (84)
Aug 10 19:48:50 homematic-ccu2 user.debug rfd: Device description rf_ws550.xml loaded (85)
Aug 10 19:48:50 homematic-ccu2 user.debug rfd: Device description rf_dim_1t_644.xml loaded (86)
Aug 10 19:48:50 homematic-ccu2 user.debug rfd: Device description rf_pbi.xml loaded (87)
Aug 10 19:48:50 homematic-ccu2 user.debug rfd: Device description rf_rc_single_on.xml loaded (88)
Aug 10 19:48:50 homematic-ccu2 user.debug rfd: Device description rf_sec_sd_schueco.xml loaded (89)
Aug 10 19:48:50 homematic-ccu2 user.debug rfd: Device description rf_dim_2l_644_le_v2_4.xml loaded (90)
Aug 10 19:48:50 homematic-ccu2 user.debug rfd: Device description rf_es_tx_wm_le_v1_0.xml loaded (91)
Aug 10 19:48:50 homematic-ccu2 user.debug rfd: Device description rf_cc_vd.xml loaded (92)
Aug 10 19:48:50 homematic-ccu2 user.debug rfd: Device description rf_d.xml loaded (93)
Aug 10 19:48:50 homematic-ccu2 user.debug rfd: Device description rf_dim_t.xml loaded (94)
Aug 10 19:48:50 homematic-ccu2 user.debug rfd: Device description rf_dim_1pwm_644.xml loaded (95)
Aug 10 19:48:51 homematic-ccu2 user.debug rfd: Device description rf_cf.xml loaded (96)
Aug 10 19:48:51 homematic-ccu2 user.debug rfd: Device description rf_dim_1tconf_644_le_v2_4.xml loaded (97)
Aug 10 19:48:51 homematic-ccu2 user.debug rfd: Device description rf_cm.xml loaded (98)
Aug 10 19:48:51 homematic-ccu2 user.debug rfd: Device description rf_rc.xml loaded (99)
Aug 10 19:48:51 homematic-ccu2 user.debug rfd: Device description rf_s_4_ba.xml loaded (100)
Aug 10 19:48:51 homematic-ccu2 user.debug rfd: Device description rf_bl_conf_644_e_v2_0.xml loaded (101)
Aug 10 19:48:51 homematic-ccu2 user.debug rfd: Device description rf_hm-wds100-c6-o-2.xml loaded (102)
Aug 10 19:48:51 homematic-ccu2 user.debug rfd: Device description rf_cfm_tw.xml loaded (103)
Aug 10 19:48:51 homematic-ccu2 user.debug rfd: Device description rf_s550ia.xml loaded (104)
Aug 10 19:48:51 homematic-ccu2 user.debug rfd: Device description rf_s_2conf_644.xml loaded (105)
Aug 10 19:48:51 homematic-ccu2 user.debug rfd: Device description rf_dim_2pwm.xml loaded (106)
Aug 10 19:48:51 homematic-ccu2 user.debug rfd: Device description rf_sen_mdir_wm55.xml loaded (107)
Aug 10 19:48:51 homematic-ccu2 user.debug rfd: Device description rf_sec_sd.xml loaded (108)
Aug 10 19:48:51 homematic-ccu2 user.debug rfd: Device description rf_em_8.xml loaded (109)
Aug 10 19:48:51 homematic-ccu2 user.debug rfd: Device description rf_wds30_ot2.xml loaded (110)
Aug 10 19:48:51 homematic-ccu2 user.debug rfd: Device description rf_s_le_v1_5.xml loaded (111)
Aug 10 19:48:51 homematic-ccu2 user.debug rfd: Device description rf_tis.xml loaded (112)
Aug 10 19:48:51 homematic-ccu2 user.debug rfd: Device description rf_sci_3.xml loaded (113)
Aug 10 19:48:51 homematic-ccu2 user.debug rfd: Device description rf_rd.xml loaded (114)
Aug 10 19:48:51 homematic-ccu2 user.debug rfd: Device description rf_dim_t_le_v1_9.xml loaded (115)
Aug 10 19:48:51 homematic-ccu2 user.debug rfd: Device description rf_s_1conf_644_le_v2_3.xml loaded (116)
Aug 10 19:48:51 homematic-ccu2 user.debug rfd: Device description rf_cc_rt_dn_bom.xml loaded (117)
Aug 10 19:48:51 homematic-ccu2 user.debug rfd: Device description rf_dim_1t_fm_lf.xml loaded (118)
Aug 10 19:48:51 homematic-ccu2 user.debug rfd: Device description rf_rc_19.xml loaded (119)
Aug 10 19:48:51 homematic-ccu2 user.debug rfd: Device description rf_sc_e_v1_7.xml loaded (120)
Aug 10 19:48:51 homematic-ccu2 user.debug rfd: Device description rf_s_ba.xml loaded (121)
Aug 10 19:48:51 homematic-ccu2 user.debug rfd: Device description rf_ao.xml loaded (122)
Aug 10 19:48:52 homematic-ccu2 user.debug rfd: Device description rf_s.xml loaded (123)
Aug 10 19:48:52 homematic-ccu2 user.debug rfd: Device description rf_cfm.xml loaded (124)
Aug 10 19:48:52 homematic-ccu2 user.debug rfd: Device description rf_ddc.xml loaded (125)
Aug 10 19:48:52 homematic-ccu2 user.debug rfd: Device description rf_s_1conf_644.xml loaded (126)
Aug 10 19:48:54 homematic-ccu2 user.debug multimac: C<: #8 TRX GetDutyCycle
Aug 10 19:48:54 homematic-ccu2 user.debug multimac: C< @19854986: bin:FD 00 03 01 08 03 28 1E
Aug 10 19:48:54 homematic-ccu2 user.debug multimac: C> @19855088: #8 TRX Response Ack 00
Aug 10 19:48:54 homematic-ccu2 user.debug multimac: SubsystemBidcos::CheckDutyCycleEventThreshold( 0.0, 0.0 ) = 0
Aug 10 19:48:58 homematic-ccu2 user.debug multimac: MacController::OnDownstreamFrame(#255 LLMAC TX @32768ms [10k,WOR,NoCCA] 97 94 3F 58 4A 19 00 00 00 02 04 23 00 8C 8B)
Aug 10 19:48:58 homematic-ccu2 user.debug multimac: C<: #9 LLMAC TX @32768ms [10k,WOR,NoCCA] 97 94 3F 58 4A 19 00 00 00 02 04 23 00 8C 8B
Aug 10 19:48:58 homematic-ccu2 user.debug multimac: C< @19859019: bin:FD 00 15 03 09 06 80 00 90 97 94 3F 58 4A 19 00 00 00 02 04 23 00 8C 8B F0 26
Aug 10 19:48:59 homematic-ccu2 user.debug multimac: C> @19859404: #9 LLMAC Response ACK @14281: 37 C9
Aug 10 19:49:04 homematic-ccu2 user.debug multimac: C<: #10 TRX GetDutyCycle
Aug 10 19:49:04 homematic-ccu2 user.debug multimac: C< @19864987: bin:FD 00 03 01 0A 03 A4 1D
Aug 10 19:49:04 homematic-ccu2 user.debug multimac: C> @19864990: #10 TRX Response Ack 02
Aug 10 19:49:04 homematic-ccu2 user.debug multimac: SubsystemBidcos::CheckDutyCycleEventThreshold( 0.0, 1.0 ) = 0
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: UpstreamCharConnection slave device ttyS0 opened
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: UpstreamCharConnection slave device ttyS0 closed
Aug 10 19:49:07 homematic-ccu2 user.info kernel: [19867.320543] eq3loop: eq3loop_open_slave() ttyS0
Aug 10 19:49:07 homematic-ccu2 user.info kernel: [19867.320777] eq3loop: eq3loop_close_slave() ttyS0
Aug 10 19:49:07 homematic-ccu2 user.info kernel: [19867.327264] eq3loop: eq3loop_open_slave() ttyS0
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: UpstreamCharConnection slave device ttyS0 closed
Aug 10 19:49:07 homematic-ccu2 user.warn multimac: Subsystem 1 refusing upstream disconnect. Client mismatch.
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: UpstreamCharConnection slave device ttyS0 opened
Aug 10 19:49:07 homematic-ccu2 user.info kernel: [19867.327528] eq3loop: eq3loop_close_slave() ttyS0
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: UpstreamCharConnection slave device ttyS0 opened
Aug 10 19:49:07 homematic-ccu2 user.info kernel: [19867.344907] eq3loop: eq3loop_open_slave() ttyS0
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: A>: #16 COMMON GetSGTIN
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: A<: #16 COMMON Response Ack 30 14 F7 11 A0 61 A7 D7 09 8E 23 51
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: A>: #17 COMMON IdentifyRequest
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: A<: #17 COMMON Response Ack 48 4D 49 50 5F 54 52 58 5F 41 70 70
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: A>: #154 HMIP CMD=00  B1 C5 B7
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: MacController::OnDownstreamFrame(#154 HMIP CMD=00  B1 C5 B7)
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: C<: #11 HMIP CMD=00  B1 C5 B7
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: C< @19867417: bin:FD 00 06 02 0B 00 B1 C5 B7 E3 91
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: C> @19867420: #11 HMIP CMD=06  01
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: A<: #154 HMIP CMD=06  01
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: A>: #155 HMIP CMD=0D  03
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: MacController::OnDownstreamFrame(#155 HMIP CMD=0D  03)
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: C<: #12 HMIP CMD=0D  03
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: C< @19867441: bin:FD 00 04 02 0C 0D 03 87 C1
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: C> @19867444: #12 HMIP CMD=06  01
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: A<: #155 HMIP CMD=06  01
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: A>: #182 TRX GetVersion
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: A<: #182 TRX Response Ack 02 08 06 01 00 03 01 14 03
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: A>: #183 TRX CMD=09  
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: MacController::OnDownstreamFrame(#183 TRX CMD=09  )
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: C<: #13 TRX CMD=09  
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: C< @19867487: bin:FD 00 03 01 0D 09 36 22
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: C> @19867589: #13 TRX Response Ack 03
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: A<: #183 TRX Response Ack 03
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: A>: #184 TRX GetDutyCycle
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: A<: #184 TRX Response Ack 02
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: A>: #185 TRX CMD=07  C8
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: MacController::OnDownstreamFrame(#185 TRX CMD=07  C8)
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: C<: #14 TRX CMD=07  C8
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: C< @19867614: bin:FD 00 04 01 0E 07 C8 85 53
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: C> @19867716: #14 TRX Response Ack 
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: A<: #185 TRX Response Ack 
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: A>: #156 HMIP CMD=0A  
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: MacController::OnDownstreamFrame(#156 HMIP CMD=0A  )
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: C<: #15 HMIP CMD=0A  
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: C< @19867718: bin:FD 00 03 02 0F 0A BA 17
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: C> @19867820: #15 HMIP CMD=06  01 00 00 9A 00
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: A<: #156 HMIP CMD=06  01 00 00 9A 00
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: A>: #157 HMIP CMD=08  00 01 9A B0
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: MacController::OnDownstreamFrame(#157 HMIP CMD=08  00 01 9A B0)
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: C<: #16 HMIP CMD=08  00 01 9A B0
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: C< @19867824: bin:FD 00 07 02 10 08 00 01 9A B0 FE 51
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: C> @19867832: #16 HMIP CMD=06  01
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: A<: #157 HMIP CMD=06  01
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: A>: #158 HMIP CMD=14  9E 02 01 0A 33 9B 3A C2 07 A0 89 3E 8C A7 FA AE 83 07 F9 9C 07 DE D0 E7 46 53 9A D7 B5 56 79 D1 B4 A8 DD 0F 6B 99 58 E8 F6 87 33 77 52 A2 CE F6 E3 35 35 60 A1 A9 96 FC FF B5 3F 6F 59 9F 4D B7 F9 BA
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: MacController::OnDownstreamFrame(#158 HMIP CMD=14  9E 02 01 0A 33 9B 3A C2 07 A0 89 3E 8C A7 FA AE 83 07 F9 9C 07 DE D0 E7 46 53 9A D7 B5 56 79 D1 B4 A8 DD 0F 6B 99 58 E8 F6 87 33 77 52 A2 CE F6 E3 35 35 60 A1 A9 96 FC FF B5 
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: C<: #17 HMIP CMD=14  9E 02 01 0A 33 9B 3A C2 07 A0 89 3E 8C A7 FA AE 83 07 F9 9C 07 DE D0 E7 46 53 9A D7 B5 56 79 D1 B4 A8 DD 0F 6B 99 58 E8 F6 87 33 77 52 A2 CE F6 E3 35 35 60 A1 A9 96 FC FF B5 3F 6F 59 9F 4D B7 F9 BA
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: C< @19867960: bin:FD 00 45 02 11 14 9E 02 01 0A 33 9B 3A C2 07 A0 89 3E 8C A7 FA AE 83 07 F9 9C 07 DE D0 E7 46 53 9A D7 B5 56 79 D1 B4 A8 DD 0F 6B 99 58 E8 F6 87 33 77 52 A2 CE F6 E3 35 35 60 A1 A9 96 FC 7C FF B5 3F 6F 59 9F 
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: C> @19868077: #17 HMIP CMD=06  01
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: A<: #158 HMIP CMD=06  01
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: A>: #159 HMIP CMD=12  
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: MacController::OnDownstreamFrame(#159 HMIP CMD=12  )
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: C<: #18 HMIP CMD=12  
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: C< @19868090: bin:FD 00 03 02 12 12 F4 47
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: C> @19868098: #18 HMIP CMD=06  01
Aug 10 19:49:07 homematic-ccu2 user.debug multimac: A<: #159 HMIP CMD=06  01
Aug 10 19:49:12 homematic-ccu2 user.debug rfd: GetAvailableFirmware for HM-RCV-50 
Aug 10 19:49:14 homematic-ccu2 user.debug multimac: C<: #19 TRX GetDutyCycle
Aug 10 19:49:14 homematic-ccu2 user.debug multimac: C< @19874989: bin:FD 00 03 01 13 03 72 1E
Aug 10 19:49:14 homematic-ccu2 user.debug multimac: C> @19875090: #19 TRX Response Ack 02
Aug 10 19:49:14 homematic-ccu2 user.debug multimac: SubsystemBidcos::CheckDutyCycleEventThreshold( 1.0, 1.0 ) = 0
Aug 10 19:49:15 homematic-ccu2 user.debug rfd: PlatformInit()
Aug 10 19:49:16 homematic-ccu2 user.info rfd: BidCos-RF_java support system.methodHelp
Aug 10 19:49:16 homematic-ccu2 user.info rfd: BidCos-RF_java support system.multicall
Aug 10 19:49:16 homematic-ccu2 user.info rfd: BidCos-RF_java support updateDevice
Aug 10 19:49:16 homematic-ccu2 user.info rfd: BidCos-RF_java support newDevices
Aug 10 19:49:16 homematic-ccu2 user.info rfd: BidCos-RF_java support deleteDevices
Aug 10 19:49:16 homematic-ccu2 user.info rfd: BidCos-RF_java support firmwareUpdateStatusChanged
Aug 10 19:49:16 homematic-ccu2 user.info rfd: BidCos-RF_java support replaceDevice
Aug 10 19:49:16 homematic-ccu2 user.info rfd: yes support replace device
Aug 10 19:49:16 homematic-ccu2 user.info rfd: BidCos-RF_java support readdedDevice
Aug 10 19:49:16 homematic-ccu2 user.info rfd: BidCos-RF_java support system.listMethods
Aug 10 19:49:16 homematic-ccu2 user.info rfd: BidCos-RF_java support event
Aug 10 19:49:16 homematic-ccu2 user.info rfd: BidCos-RF_java support listDevices
Aug 10 19:49:16 homematic-ccu2 user.debug rfd: GetAvailableFirmware for HM-RCV-50 
Aug 10 19:49:19 homematic-ccu2 user.debug rfd: Event: CENTRAL.PONG="hm-rpc.0"
Aug 10 19:49:19 homematic-ccu2 user.debug rfd: HSSXmlRpcEventDispatcher::Handle send 1 events
Aug 10 19:49:19 homematic-ccu2 user.debug rfd: HSSXmlRpcEventDispatcher::Handle send completed
Aug 10 19:49:22 homematic-ccu2 user.debug multimac: C> @19882485: #0 LLMAC RX @ 5155ms 0dBm 7A 86 10 46 F1 4B 00 00 00 0A 29 05 0B 00 40
Aug 10 19:49:22 homematic-ccu2 user.debug multimac: Bidcos RX: #7A[BC|Ren|WMup] 46F14B->000000 Info: 0A 29 05 0B 00 40
Aug 10 19:49:22 homematic-ccu2 user.debug multimac: GetAckActionForIncomingTelegram(): Unknown peer, AckAction_NotForUs
Aug 10 19:49:22 homematic-ccu2 user.debug multimac: A<: #5 HmBidcos RxTelegram AuthNone #7A[BC|Ren|WMup] 46F14B->000000 Info: 0A 29 05 0B 00 40
Aug 10 19:49:24 homematic-ccu2 user.debug rfd: GetAvailableFirmware for HM-RCV-50 
Aug 10 19:49:24 homematic-ccu2 user.debug multimac: C<: #20 TRX GetDutyCycle
Aug 10 19:49:24 homematic-ccu2 user.debug multimac: C< @19884990: bin:FD 00 03 01 14 03 E0 1D
Aug 10 19:49:24 homematic-ccu2 user.debug multimac: C> @19885091: #20 TRX Response Ack 02
Aug 10 19:49:24 homematic-ccu2 user.debug multimac: SubsystemBidcos::CheckDutyCycleEventThreshold( 1.0, 1.0 ) = 0
Aug 10 19:49:25 homematic-ccu2 user.debug rfd: PlatformInit()
Aug 10 19:49:25 homematic-ccu2 user.info rfd: 1007 support deleteDevices
Aug 10 19:49:25 homematic-ccu2 user.info rfd: 1007 support event
Aug 10 19:49:25 homematic-ccu2 user.info rfd: 1007 support listDevices
Aug 10 19:49:25 homematic-ccu2 user.info rfd: 1007 support newDevices
Aug 10 19:49:25 homematic-ccu2 user.info rfd: 1007 support replaceDevice
Aug 10 19:49:25 homematic-ccu2 user.info rfd: yes support replace device
Aug 10 19:49:25 homematic-ccu2 user.info rfd: 1007 support reportValueUsage
Aug 10 19:49:25 homematic-ccu2 user.info rfd: 1007 support setReadyConfig
Aug 10 19:49:25 homematic-ccu2 user.info rfd: 1007 support system.listMethods
Aug 10 19:49:25 homematic-ccu2 user.info rfd: 1007 support system.methodHelp
Aug 10 19:49:25 homematic-ccu2 user.info rfd: 1007 support updateDevice
Aug 10 19:49:25 homematic-ccu2 user.info rfd: 1007 support system.multicall
Aug 10 19:49:25 homematic-ccu2 user.debug rfd: GetAvailableFirmware for HM-RCV-50 
Aug 10 19:49:34 homematic-ccu2 user.debug setclock: Try to get time from ntp.homematic.com
Aug 10 19:49:34 homematic-ccu2 user.debug setclock: Fri Aug 10 19:49:34 CEST 2018
Aug 10 19:49:34 homematic-ccu2 user.debug multimac: C<: #21 TRX GetDutyCycle
Aug 10 19:49:34 homematic-ccu2 user.debug multimac: C< @19894991: bin:FD 00 03 01 15 03 66 1E
Aug 10 19:49:34 homematic-ccu2 user.debug multimac: C> @19895092: #21 TRX Response Ack 02
Aug 10 19:49:34 homematic-ccu2 user.debug multimac: SubsystemBidcos::CheckDutyCycleEventThreshold( 1.0, 1.0 ) = 0
Aug 10 19:49:44 homematic-ccu2 user.debug multimac: C<: #22 TRX GetDutyCycle
Aug 10 19:49:44 homematic-ccu2 user.debug multimac: C< @19904991: bin:FD 00 03 01 16 03 6C 1E
Aug 10 19:49:44 homematic-ccu2 user.debug multimac: C> @19905093: #22 TRX Response Ack 02
Aug 10 19:49:44 homematic-ccu2 user.debug multimac: SubsystemBidcos::CheckDutyCycleEventThreshold( 1.0, 1.0 ) = 0
Aug 10 19:49:54 homematic-ccu2 user.debug multimac: C<: #23 TRX GetDutyCycle
Aug 10 19:49:54 homematic-ccu2 user.debug multimac: C< @19914991: bin:FD 00 03 01 17 03 EA 1D
Aug 10 19:49:54 homematic-ccu2 user.debug multimac: C> @19915093: #23 TRX Response Ack 02
Aug 10 19:49:54 homematic-ccu2 user.debug multimac: SubsystemBidcos::CheckDutyCycleEventThreshold( 1.0, 1.0 ) = 0
Aug 10 19:50:04 homematic-ccu2 user.debug multimac: C<: #24 TRX GetDutyCycle
Aug 10 19:50:04 homematic-ccu2 user.debug multimac: C< @19924992: bin:FD 00 03 01 18 03 C8 1D
Aug 10 19:50:04 homematic-ccu2 user.debug multimac: C> @19925093: #24 TRX Response Ack 02
Aug 10 19:50:04 homematic-ccu2 user.debug multimac: SubsystemBidcos::CheckDutyCycleEventThreshold( 1.0, 1.0 ) = 0
Aug 10 19:50:14 homematic-ccu2 user.debug multimac: C<: #25 TRX GetDutyCycle
Aug 10 19:50:14 homematic-ccu2 user.debug multimac: C< @19934993: bin:FD 00 03 01 19 03 4E 1E
Aug 10 19:50:14 homematic-ccu2 user.debug multimac: C> @19935094: #25 TRX Response Ack 02
Aug 10 19:50:14 homematic-ccu2 user.debug multimac: SubsystemBidcos::CheckDutyCycleEventThreshold( 1.0, 1.0 ) = 0
Aug 10 19:50:24 homematic-ccu2 user.debug multimac: C<: #26 TRX GetDutyCycle
Aug 10 19:50:24 homematic-ccu2 user.debug multimac: C< @19944994: bin:FD 00 03 01 1A 03 44 1E
Aug 10 19:50:24 homematic-ccu2 user.debug multimac: C> @19945095: #26 TRX Response Ack 02
Aug 10 19:50:24 homematic-ccu2 user.debug multimac: SubsystemBidcos::CheckDutyCycleEventThreshold( 1.0, 1.0 ) = 0
Aug 10 19:50:34 homematic-ccu2 user.debug multimac: C<: #27 TRX GetDutyCycle
Aug 10 19:50:34 homematic-ccu2 user.debug multimac: C< @19954995: bin:FD 00 03 01 1B 03 C2 1D
Aug 10 19:50:34 homematic-ccu2 user.debug multimac: C> @19954997: #27 TRX Response Ack 02
Aug 10 19:50:34 homematic-ccu2 user.debug multimac: SubsystemBidcos::CheckDutyCycleEventThreshold( 1.0, 1.0 ) = 0
Aug 10 19:50:41 homematic-ccu2 user.debug multimac: A>: #7 HmBidcos SetAesKey.tmp D4 1D 8C D9 8F 00 B2 04 E9 80 09 98 EC F8 42 7E
Aug 10 19:50:41 homematic-ccu2 user.debug multimac: A<: #7 HmBidcos Response 01
Aug 10 19:50:41 homematic-ccu2 user.debug rfd: (OEQ0310097) Response status: OK.
Aug 10 19:50:41 homematic-ccu2 user.debug rfd: Leaving install mode.
Aug 10 19:50:44 homematic-ccu2 user.debug multimac: C<: #28 TRX GetDutyCycle
Aug 10 19:50:44 homematic-ccu2 user.debug multimac: C< @19964996: bin:FD 00 03 01 1C 03 50 1E
Aug 10 19:50:44 homematic-ccu2 user.debug multimac: C> @19965097: #28 TRX Response Ack 02
Aug 10 19:50:44 homematic-ccu2 user.debug multimac: SubsystemBidcos::CheckDutyCycleEventThreshold( 1.0, 1.0 ) = 0
Aug 10 19:50:49 homematic-ccu2 user.debug rfd: Event: CENTRAL.PONG="hm-rpc.0"
Aug 10 19:50:49 homematic-ccu2 user.debug rfd: HSSXmlRpcEventDispatcher::Handle send 1 events
Aug 10 19:50:49 homematic-ccu2 user.debug rfd: HSSXmlRpcEventDispatcher::Handle send 1 events
Aug 10 19:50:49 homematic-ccu2 user.debug rfd: HSSXmlRpcEventDispatcher::Handle send completed
Aug 10 19:50:49 homematic-ccu2 user.debug rfd: HSSXmlRpcEventDispatcher::Handle send completed
Aug 10 19:50:50 homematic-ccu2 user.debug multimac: C> @19970728: #1 LLMAC RX @28531ms -51dBm B1 86 10 46 EE B4 00 00 00 0A 24 FD 0C 00 40
Aug 10 19:50:50 homematic-ccu2 user.debug multimac: Bidcos RX: #B1[BC|Ren|WMup] 46EEB4->000000 Info: 0A 24 FD 0C 00 40
Aug 10 19:50:50 homematic-ccu2 user.debug multimac: GetAckActionForIncomingTelegram(): Unknown peer, AckAction_NotForUs
Aug 10 19:50:50 homematic-ccu2 user.debug multimac: A<: #16 HmBidcos RxTelegram AuthNone #B1[BC|Ren|WMup] 46EEB4->000000 Info: 0A 24 FD 0C 00 40
Aug 10 19:50:54 homematic-ccu2 user.debug multimac: C<: #29 TRX GetDutyCycle
Aug 10 19:50:54 homematic-ccu2 user.debug multimac: C< @19974997: bin:FD 00 03 01 1D 03 D6 1D
Aug 10 19:50:54 homematic-ccu2 user.debug multimac: C> @19975098: #29 TRX Response Ack 02
Aug 10 19:50:54 homematic-ccu2 user.debug multimac: SubsystemBidcos::CheckDutyCycleEventThreshold( 1.0, 1.0 ) = 0
Aug 10 19:51:04 homematic-ccu2 user.debug multimac: C<: #30 TRX GetDutyCycle
Aug 10 19:51:04 homematic-ccu2 user.debug multimac: C< @19984997: bin:FD 00 03 01 1E 03 DC 1D
Aug 10 19:51:04 homematic-ccu2 user.debug multimac: C> @19985098: #30 TRX Response Ack 02
Aug 10 19:51:04 homematic-ccu2 user.debug multimac: SubsystemBidcos::CheckDutyCycleEventThreshold( 1.0, 1.0 ) = 0
Aug 10 19:51:14 homematic-ccu2 user.debug multimac: C<: #31 TRX GetDutyCycle
Aug 10 19:51:14 homematic-ccu2 user.debug multimac: C< @19994997: bin:FD 00 03 01 1F 03 5A 1E
Aug 10 19:51:14 homematic-ccu2 user.debug multimac: C> @19995098: #31 TRX Response Ack 02
Aug 10 19:51:14 homematic-ccu2 user.debug multimac: SubsystemBidcos::CheckDutyCycleEventThreshold( 1.0, 1.0 ) = 0
Aug 10 19:51:24 homematic-ccu2 user.debug multimac: C<: #32 TRX GetDutyCycle
Aug 10 19:51:24 homematic-ccu2 user.debug multimac: C< @20004997: bin:FD 00 03 01 20 03 D8 1E
Aug 10 19:51:24 homematic-ccu2 user.debug multimac: C> @20005098: #32 TRX Response Ack 02
Aug 10 19:51:24 homematic-ccu2 user.debug multimac: SubsystemBidcos::CheckDutyCycleEventThreshold( 1.0, 1.0 ) = 0
Aug 10 19:51:28 homematic-ccu2 user.debug multimac: C> @20008512: #2 LLMAC RX @ 1075ms -85dBm 7B 86 10 46 F1 4B 00 00 00 0A 29 05 0B 00 40
Aug 10 19:51:28 homematic-ccu2 user.debug multimac: Bidcos RX: #7B[BC|Ren|WMup] 46F14B->000000 Info: 0A 29 05 0B 00 40
Aug 10 19:51:28 homematic-ccu2 user.debug multimac: GetAckActionForIncomingTelegram(): Unknown peer, AckAction_NotForUs
Aug 10 19:51:28 homematic-ccu2 user.debug multimac: A<: #22 HmBidcos RxTelegram AuthNone #7B[BC|Ren|WMup] 46F14B->000000 Info: 0A 29 05 0B 00 40
Aug 10 19:51:34 homematic-ccu2 user.debug multimac: C<: #33 TRX GetDutyCycle
Aug 10 19:51:34 homematic-ccu2 user.debug multimac: C< @20014997: bin:FD 00 03 01 21 03 5E 1D
Aug 10 19:51:34 homematic-ccu2 user.debug multimac: C> @20015099: #33 TRX Response Ack 02
Aug 10 19:51:34 homematic-ccu2 user.debug multimac: SubsystemBidcos::CheckDutyCycleEventThreshold( 1.0, 1.0 ) = 0
Aug 10 19:51:44 homematic-ccu2 user.debug multimac: C<: #34 TRX GetDutyCycle
Aug 10 19:51:44 homematic-ccu2 user.debug multimac: C< @20024997: bin:FD 00 03 01 22 03 54 1D
Aug 10 19:51:44 homematic-ccu2 user.debug multimac: C> @20025098: #34 TRX Response Ack 02
Aug 10 19:51:44 homematic-ccu2 user.debug multimac: SubsystemBidcos::CheckDutyCycleEventThreshold( 1.0, 1.0 ) = 0
Aug 10 19:51:48 homematic-ccu2 user.debug multimac: A>: #8 HmBidcos SetAesKey.tmp D4 1D 8C D9 8F 00 B2 04 E9 80 09 98 EC F8 42 7E
Aug 10 19:51:48 homematic-ccu2 user.debug multimac: A<: #8 HmBidcos Response 01
Aug 10 19:51:48 homematic-ccu2 user.debug rfd: (OEQ0310097) Response status: OK.
Aug 10 19:51:48 homematic-ccu2 user.debug rfd: Leaving install mode.
Aug 10 19:51:54 homematic-ccu2 user.debug multimac: C<: #35 TRX GetDutyCycle
Aug 10 19:51:54 homematic-ccu2 user.debug multimac: C< @20034997: bin:FD 00 03 01 23 03 D2 1E
Aug 10 19:51:54 homematic-ccu2 user.debug multimac: C> @20035000: #35 TRX Response Ack 02
Aug 10 19:51:54 homematic-ccu2 user.debug multimac: SubsystemBidcos::CheckDutyCycleEventThreshold( 1.0, 1.0 ) = 0
Aug 10 19:52:04 homematic-ccu2 user.debug multimac: C<: #36 TRX GetDutyCycle
Aug 10 19:52:04 homematic-ccu2 user.debug multimac: C< @20044997: bin:FD 00 03 01 24 03 40 1D
Aug 10 19:52:04 homematic-ccu2 user.debug multimac: C> @20045098: #36 TRX Response Ack 02
Aug 10 19:52:04 homematic-ccu2 user.debug multimac: SubsystemBidcos::CheckDutyCycleEventThreshold( 1.0, 1.0 ) = 0
Aug 10 19:52:14 homematic-ccu2 user.debug multimac: C<: #37 TRX GetDutyCycle
Aug 10 19:52:14 homematic-ccu2 user.debug multimac: C< @20054997: bin:FD 00 03 01 25 03 C6 1E
Aug 10 19:52:14 homematic-ccu2 user.debug multimac: C> @20055099: #37 TRX Response Ack 02
Aug 10 19:52:14 homematic-ccu2 user.debug multimac: SubsystemBidcos::CheckDutyCycleEventThreshold( 1.0, 1.0 ) = 0
Aug 10 19:52:24 homematic-ccu2 user.debug multimac: C<: #38 TRX GetDutyCycle
Aug 10 19:52:24 homematic-ccu2 user.debug multimac: C< @20064997: bin:FD 00 03 01 26 03 CC 1E
Aug 10 19:52:24 homematic-ccu2 user.debug multimac: C> @20065099: #38 TRX Response Ack 02
Aug 10 19:52:24 homematic-ccu2 user.debug multimac: SubsystemBidcos::CheckDutyCycleEventThreshold( 1.0, 1.0 ) = 0
Aug 10 19:52:34 homematic-ccu2 user.debug multimac: C<: #39 TRX GetDutyCycle
Aug 10 19:52:34 homematic-ccu2 user.debug multimac: C< @20074997: bin:FD 00 03 01 27 03 4A 1D
Aug 10 19:52:34 homematic-ccu2 user.debug multimac: C> @20075099: #39 TRX Response Ack 02
Aug 10 19:52:34 homematic-ccu2 user.debug multimac: SubsystemBidcos::CheckDutyCycleEventThreshold( 1.0, 1.0 ) = 0
Aug 10 19:52:44 homematic-ccu2 user.debug multimac: C<: #40 TRX GetDutyCycle
Aug 10 19:52:44 homematic-ccu2 user.debug multimac: C< @20084998: bin:FD 00 03 01 28 03 68 1D
Aug 10 19:52:44 homematic-ccu2 user.debug multimac: C> @20085099: #40 TRX Response Ack 02
Aug 10 19:52:44 homematic-ccu2 user.debug multimac: SubsystemBidcos::CheckDutyCycleEventThreshold( 1.0, 1.0 ) = 0
Aug 10 19:52:53 homematic-ccu2 user.debug multimac: A>: #9 HmBidcos SetAesKey.tmp D4 1D 8C D9 8F 00 B2 04 E9 80 09 98 EC F8 42 7E
Aug 10 19:52:53 homematic-ccu2 user.debug multimac: A<: #9 HmBidcos Response 01
Aug 10 19:52:53 homematic-ccu2 user.debug rfd: (OEQ0310097) Response status: OK.
Aug 10 19:52:53 homematic-ccu2 user.debug rfd: Leaving install mode.
Aug 10 19:52:54 homematic-ccu2 user.debug multimac: C<: #41 TRX GetDutyCycle
Aug 10 19:52:54 homematic-ccu2 user.debug multimac: C< @20094998: bin:FD 00 03 01 29 03 EE 1E
Aug 10 19:52:54 homematic-ccu2 user.debug multimac: C> @20095100: #41 TRX Response Ack 02
Aug 10 19:52:54 homematic-ccu2 user.debug multimac: SubsystemBidcos::CheckDutyCycleEventThreshold( 1.0, 1.0 ) = 0
Aug 10 19:53:04 homematic-ccu2 user.debug multimac: C<: #42 TRX GetDutyCycle
Aug 10 19:53:04 homematic-ccu2 user.debug multimac: C< @20104999: bin:FD 00 03 01 2A 03 E4 1E
Aug 10 19:53:04 homematic-ccu2 user.debug multimac: C> @20105100: #42 TRX Response Ack 02
Aug 10 19:53:04 homematic-ccu2 user.debug multimac: SubsystemBidcos::CheckDutyCycleEventThreshold( 1.0, 1.0 ) = 0
Aug 10 19:53:14 homematic-ccu2 user.debug multimac: C<: #43 TRX GetDutyCycle
Aug 10 19:53:14 homematic-ccu2 user.debug multimac: C< @20114999: bin:FD 00 03 01 2B 03 62 1D
Aug 10 19:53:14 homematic-ccu2 user.debug multimac: C> @20115101: #43 TRX Response Ack 02
Aug 10 19:53:14 homematic-ccu2 user.debug multimac: SubsystemBidcos::CheckDutyCycleEventThreshold( 1.0, 1.0 ) = 0
Aug 10 19:53:24 homematic-ccu2 user.debug multimac: C<: #44 TRX GetDutyCycle
Aug 10 19:53:24 homematic-ccu2 user.debug multimac: C< @20124999: bin:FD 00 03 01 2C 03 F0 1E
Aug 10 19:53:24 homematic-ccu2 user.debug multimac: C> @20125101: #44 TRX Response Ack 02
Aug 10 19:53:24 homematic-ccu2 user.debug multimac: SubsystemBidcos::CheckDutyCycleEventThreshold( 1.0, 1.0 ) = 0
Aug 10 19:53:34 homematic-ccu2 user.debug multimac: C<: #45 TRX GetDutyCycle
Aug 10 19:53:34 homematic-ccu2 user.debug multimac: C< @20134999: bin:FD 00 03 01 2D 03 76 1D
Aug 10 19:53:34 homematic-ccu2 user.debug multimac: C> @20135100: #45 TRX Response Ack 02
Aug 10 19:53:34 homematic-ccu2 user.debug multimac: SubsystemBidcos::CheckDutyCycleEventThreshold( 1.0, 1.0 ) = 0
Aug 10 19:53:44 homematic-ccu2 user.debug multimac: C<: #46 TRX GetDutyCycle
Aug 10 19:53:44 homematic-ccu2 user.debug multimac: C< @20144999: bin:FD 00 03 01 2E 03 7C 1D
Aug 10 19:53:44 homematic-ccu2 user.debug multimac: C> @20145101: #46 TRX Response Ack 02
Aug 10 19:53:44 homematic-ccu2 user.debug multimac: SubsystemBidcos::CheckDutyCycleEventThreshold( 1.0, 1.0 ) = 0
Aug 10 19:53:54 homematic-ccu2 user.debug multimac: C<: #47 TRX GetDutyCycle
Aug 10 19:53:54 homematic-ccu2 user.debug multimac: C< @20154999: bin:FD 00 03 01 2F 03 FA 1E
Aug 10 19:53:54 homematic-ccu2 user.debug multimac: C> @20155100: #47 TRX Response Ack 02
Aug 10 19:53:54 homematic-ccu2 user.debug multimac: SubsystemBidcos::CheckDutyCycleEventThreshold( 1.0, 1.0 ) = 0
Aug 10 19:54:04 homematic-ccu2 user.debug multimac: C<: #48 TRX GetDutyCycle
Aug 10 19:54:04 homematic-ccu2 user.debug multimac: C< @20165000: bin:FD 00 03 01 30 03 38 1D
Aug 10 19:54:04 homematic-ccu2 user.debug multimac: C> @20165101: #48 TRX Response Ack 02
Aug 10 19:54:04 homematic-ccu2 user.debug multimac: SubsystemBidcos::CheckDutyCycleEventThreshold( 1.0, 1.0 ) = 0
Aug 10 19:54:07 homematic-ccu2 user.debug multimac: A>: #186 TRX GetDutyCycle
Aug 10 19:54:07 homematic-ccu2 user.debug multimac: A<: #186 TRX Response Ack 02
Aug 10 19:54:14 homematic-ccu2 user.debug multimac: C<: #49 TRX GetDutyCycle
Aug 10 19:54:14 homematic-ccu2 user.debug multimac: C< @20175000: bin:FD 00 03 01 31 03 BE 1E
Aug 10 19:54:14 homematic-ccu2 user.debug multimac: C> @20175102: #49 TRX Response Ack 02
Aug 10 19:54:14 homematic-ccu2 user.debug multimac: SubsystemBidcos::CheckDutyCycleEventThreshold( 1.0, 1.0 ) = 0
Aug 10 19:54:23 homematic-ccu2 user.debug multimac: C> @20184016: #3 LLMAC RX @14118ms -57dBm 7C 86 10 46 F1 4B 00 00 00 0A 29 05 0B 00 40
Aug 10 19:54:23 homematic-ccu2 user.debug multimac: Bidcos RX: #7C[BC|Ren|WMup] 46F14B->000000 Info: 0A 29 05 0B 00 40
Aug 10 19:54:23 homematic-ccu2 user.debug multimac: GetAckActionForIncomingTelegram(): Unknown peer, AckAction_NotForUs
Aug 10 19:54:23 homematic-ccu2 user.debug multimac: A<: #41 HmBidcos RxTelegram AuthNone #7C[BC|Ren|WMup] 46F14B->000000 Info: 0A 29 05 0B 00 40
Aug 10 19:54:24 homematic-ccu2 user.debug multimac: C<: #50 TRX GetDutyCycle
Aug 10 19:54:24 homematic-ccu2 user.debug multimac: C< @20185000: bin:FD 00 03 01 32 03 B4 1E
Aug 10 19:54:24 homematic-ccu2 user.debug multimac: C> @20185003: #50 TRX Response Ack 02
Aug 10 19:54:24 homematic-ccu2 user.debug multimac: SubsystemBidcos::CheckDutyCycleEventThreshold( 1.0, 1.0 ) = 0
Aug 10 19:54:34 homematic-ccu2 user.debug multimac: C<: #51 TRX GetDutyCycle
Aug 10 19:54:34 homematic-ccu2 user.debug multimac: C< @20195000: bin:FD 00 03 01 33 03 32 1D
Aug 10 19:54:34 homematic-ccu2 user.debug multimac: C> @20195101: #51 TRX Response Ack 02
Aug 10 19:54:34 homematic-ccu2 user.debug multimac: SubsystemBidcos::CheckDutyCycleEventThreshold( 1.0, 1.0 ) = 0


***** hmserver.log *****
Aug 10 19:48:55 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] @GenericFactory 
Aug 10 19:48:55 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] creating instance of HMServerConfiguration with no-arg constructor 
Aug 10 19:49:03 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [HMIPTRXWriterWorker] (1) *worker 
Aug 10 19:49:03 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [KeyServerWorker] (1) *worker 
Aug 10 19:49:03 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [KryoPersistenceWorker] (1) *worker 
Aug 10 19:49:03 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [TransactionSubsystemHandler] (1) *worker 
Aug 10 19:49:03 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [FirmwareLoaderFileSystem] (1) *worker 
Aug 10 19:49:03 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerPersistentDataLoader] (1)  
Aug 10 19:49:03 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerAdapterInitialization] (1)  
Aug 10 19:49:03 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [BackendCommandHandler] (1)  
Aug 10 19:49:03 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceInclusionAcceptHandler] (1)  
Aug 10 19:49:03 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [CheckDeviceExistHandler] (1)  
Aug 10 19:49:03 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [IncomingHMIPFrameHandler] (1)  
Aug 10 19:49:03 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceBackgroundUpdateSubsystem] (1)  
Aug 10 19:49:03 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceInclusionDefaultConfigurationChanger] (1)  
Aug 10 19:49:03 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [CyclicSmokeDetectorAwakening] (1)  
Aug 10 19:49:03 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerFirmwareUpdateInitialization] (1)  
Aug 10 19:49:03 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyNotificationHandler] (1) *worker 
Aug 10 19:49:03 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyAPIWorker] (1) *worker 
Aug 10 19:49:03 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyBackendNotificationHandler] (3) *worker 
Aug 10 19:49:03 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyBlindLevelCorrectionHandler] (1) *worker 
Aug 10 19:49:03 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyInitializion] (1)  
Aug 10 19:49:03 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: deploying 20 classes to Vert.x 
Aug 10 19:49:03 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: 20 VertxDeployers initialized 
Aug 10 19:49:03 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of CyclicSmokeDetectorAwakening succeeded (e384b0c7-0583-476d-84f1-e7f11efd3b97) 
Aug 10 19:49:04 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of CheckDeviceExistHandler succeeded (b99868b3-ea3d-486f-a60b-70aca142f67c) 
Aug 10 19:49:04 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of LegacyBlindLevelCorrectionHandler succeeded (18ba1b6e-94ae-47bd-b29e-5f8f881b382c) 
Aug 10 19:49:04 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of HMIPTRXWriterWorker succeeded (27d554ab-0c58-4523-a61e-0b95f544df5e) 
Aug 10 19:49:04 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of DeviceInclusionDefaultConfigurationChanger succeeded (d0a6d514-1863-47c8-aee8-fa2b25e6276f) 
Aug 10 19:49:04 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-7] SYSTEM: start of TransactionSubsystemHandler succeeded (9fd56cb2-e615-4099-8e28-5e57b0322dfb) 
Aug 10 19:49:04 de.eq3.cbcs.server.core.vertx.KeyServerWorker ERROR [vert.x-worker-thread-3] Missing key server configuration parameter (Network.Key) for  mode: KEYSERVER_LOCAL 
Aug 10 19:49:04 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-6] SYSTEM: start of KeyServerWorker succeeded (6a48d2d9-6ddb-4fde-92c6-caac8c0089d5) 
Aug 10 19:49:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-6] SYSTEM: start of KryoPersistenceWorker succeeded (51c0d525-9fc7-4bb8-8620-17f4426b5844) 
Aug 10 19:49:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-7] SYSTEM: start of LocalServerPersistentDataLoader succeeded (be9c6aac-cf1d-49b6-992b-c2184939709a) 
Aug 10 19:49:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of DeviceBackgroundUpdateSubsystem succeeded (0e3dcc51-65b8-4f46-b557-ea993e66d303) 
Aug 10 19:49:06 de.eq3.cbcs.server.core.otau.util.FirmwareLoaderFileSystem INFO  [vert.x-worker-thread-2] SYSTEM: Firmware update directory is set to /etc/config/firmware 
Aug 10 19:49:06 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of FirmwareLoaderFileSystem succeeded (448d67a0-0f25-493e-b6f5-b79d70357bc7) 
Aug 10 19:49:06 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of BackendCommandHandler succeeded (c7defec6-7456-49b5-99b9-ba18775394c0) 
Aug 10 19:49:06 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of LegacyNotificationHandler succeeded (d0465422-d5ba-4c60-86c3-f907c094c7bd) 
Aug 10 19:49:06 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-7] SYSTEM: start of DeviceInclusionAcceptHandler succeeded (24497343-3c52-480e-845f-fb7a1d133b29) 
Aug 10 19:49:06 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of IncomingHMIPFrameHandler succeeded (c55d6fd3-abe6-493d-98db-158a52e63dbe) 
Aug 10 19:49:06 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-7] SYSTEM: start of LegacyBackendNotificationHandler succeeded (e0b0d859-e5b2-4aa9-a6f6-effa040ecb5e) 
Aug 10 19:49:07 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of LegacyAPIWorker succeeded (2d03ee23-cb38-4334-a51d-b668c36e8654) 
Aug 10 19:49:07 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-6] SYSTEM: start of LocalServerAdapterInitialization succeeded (e0bbf199-a2eb-41ea-8069-fcb99b37be66) 
Aug 10 19:49:07 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] TRX adapter state 1: HMIP_TRX_App 
Aug 10 19:49:07 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] TRX adapter application is already running 
Aug 10 19:49:07 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] No NWK, try to set address ... 
Aug 10 19:49:07 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Try to set radio address 11650487... 
Aug 10 19:49:07 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Set max send attempts for 3014F711A061A7D7098E2351 to 3 
Aug 10 19:49:07 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Try to get application version... 
Aug 10 19:49:07 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Application version 2.8.6 
Aug 10 19:49:07 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Bootloader version 1.0.3 
Aug 10 19:49:07 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] hmos version 1.20.3 
Aug 10 19:49:07 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] MCU type: Si1002_8051 
Aug 10 19:49:07 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Duty Cycle: 1.0 
Aug 10 19:49:07 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] set DutyCycle limit to ffffffc8 
Aug 10 19:49:07 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Set Duty Cycle Limit 
Aug 10 19:49:07 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Current Security Counter: 39424 
Aug 10 19:49:07 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Update security counter to calculation: 105136 
Aug 10 19:49:07 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] TRX adapter has no linkpartner 
Aug 10 19:49:07 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Adapter with Access Point id 3014F711A061A7D7098E2351 initialized 
Aug 10 19:49:07 de.eq3.cbcs.server.local.base.internal.LocalServerAdapterInitialization INFO  [Thread-6] HMIPTRXInitialResponseListener said that Adapter was initialized 
Aug 10 19:49:08 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of LegacyInitializion succeeded (1caf1530-af02-4843-934b-69b3fd09d651) 
Aug 10 19:49:08 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of LocalServerFirmwareUpdateInitialization succeeded (52fa9e16-fba5-4364-bc6f-32fabcf941ad) 
Aug 10 19:49:08 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 
Aug 10 19:49:08 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-4] SYSTEM: Checking all devices on all accesspoints for updates 
Aug 10 19:49:08 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-4] SYSTEM: There are 0 APs queued with updatable devices 
Aug 10 19:49:08 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: initial deployment complete _____________________________________________________ 
Aug 10 19:49:10 de.eq3.cbcs.server.local.LocalServer INFO  [Thread-0] SYSTEM: Bind XML-RPC api to port 2010 
Aug 10 19:49:10 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Default MaxEventLoopExecuteTime: 2000000000 
Aug 10 19:49:10 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Default BlockedThreadCheckInterval: 1000 
Aug 10 19:49:10 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Default MaxWorkerExecuteTime: 60000000000 
Aug 10 19:49:10 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Default EventLoopPoolSize: 8 
Aug 10 19:49:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [BackendWorker] (1) *worker 
Aug 10 19:49:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [GroupRequestWorker] (1) *worker 
Aug 10 19:49:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [DiagramRequestWorker] (1) *worker 
Aug 10 19:49:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [StorageRequestWorker] (1) *worker 
Aug 10 19:49:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [DeviceFirmwareRequestWorker] (1) *worker 
Aug 10 19:49:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [EnergyPriceRequestWorker] (1) *worker 
Aug 10 19:49:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [CouplingRequestWorker] (1) *worker 
Aug 10 19:49:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [RegaClientWorker] (1) *worker 
Aug 10 19:49:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [GroupConfigurationPersistenceFileSystem] (1) *worker 
Aug 10 19:49:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: deploying 9 classes to Vert.x 
Aug 10 19:49:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: 9 VertxDeployers initialized 
Aug 10 19:49:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of BackendWorker succeeded (2ece4d00-914b-414f-8d4f-728bf2f90cc5) 
Aug 10 19:49:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of StorageRequestWorker succeeded (8051dd73-0fe1-4106-bc16-35ad870717b2) 
Aug 10 19:49:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of GroupConfigurationPersistenceFileSystem succeeded (d9bc4447-c843-46ad-8bb0-b8de2f448d5d) 
Aug 10 19:49:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of EnergyPriceRequestWorker succeeded (b6f2aa09-5ad0-4fc5-b99c-0ca486902144) 
Aug 10 19:49:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of RegaClientWorker succeeded (fe341a0c-e577-4295-a96c-79be55cedb48) 
Aug 10 19:49:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of CouplingRequestWorker succeeded (ca60fb57-7239-4a75-8ed5-d8d0ad598824) 
Aug 10 19:49:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of GroupRequestWorker succeeded (91447287-93cb-46d0-a70b-55e3478f8bc5) 
Aug 10 19:49:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of DiagramRequestWorker succeeded (ac1dfc23-6dcb-4ee9-96d8-e83cffccdf5d) 
Aug 10 19:49:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of DeviceFirmwareRequestWorker succeeded (ebf0c64e-be2a-4171-8a85-b4a91d236bc7) 
Aug 10 19:49:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: initial deployment complete _____________________________________________________ 
Aug 10 19:49:10 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Starting HMServer at 127.0.0.1:9292 
Aug 10 19:49:10 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Read Configuration 
Aug 10 19:49:11 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Create Bidcos Dispatcher 
Aug 10 19:49:11 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] InitBidCosCache 
Aug 10 19:49:13 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Create groupDefinitionProvider 
Aug 10 19:49:13 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Create VirtualDeviceHolder 
Aug 10 19:49:13 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Create VirtualDeviceHandlerRega 
Aug 10 19:49:13 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Create GroupAdministrationService 
Aug 10 19:49:13 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Create GroupDeviceDispatcher 
Aug 10 19:49:13 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Create GroupDeviceHandler 
Aug 10 19:49:14 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-2] @GroupDeviceHandler - initializing... 
Aug 10 19:49:14 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-2] --> created groupDeviceDispatcher (GroupDeviceService to BidCoS (via Dispatcher)) 
Aug 10 19:49:14 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-2] --> created virtualDeviceHandler (GroupDeviceService to ReGa) 
Aug 10 19:49:14 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-2] --> got groupDefinitionProvider 
Aug 10 19:49:14 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Create BidCosGroupMemberProvider 
Aug 10 19:49:14 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Init groupAdministrationService 
Aug 10 19:49:14 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Init Virtual OS Device 
Aug 10 19:49:14 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Init ESHLight Bridge 
Aug 10 19:49:15 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Create RrdDatalogging 
Aug 10 19:49:15 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Create MeasurementService 
Aug 10 19:49:15 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Init MeasurementService 
Aug 10 19:49:15 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Create HTTP Server 
Aug 10 19:49:15 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Create BidCos context and start handler 
Aug 10 19:49:15 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Create group context and start handler 
Aug 10 19:49:15 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 
Aug 10 19:49:15 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-2] init finished 
Aug 10 19:49:15 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO  [vert.x-worker-thread-2] Added InterfaceId: HmIP-RF_java 
Aug 10 19:49:16 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Starting HMServer done 
Aug 10 19:49:25 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 
Aug 10 19:49:25 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-1] Added InterfaceId: 1008 
Aug 10 19:49:25 de.eq3.ccu.virtualdevice.service.internal.rega.BackendWorker INFO  [vert.x-worker-thread-9] Execute BackendCommand: de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand 
Aug 10 19:49:35 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-3] (un)registerCallback on LegacyServiceHandler called from url: xmlrpc_bin://127.0.0.1:1999 
Aug 10 19:49:35 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-3] init finished 
Aug 10 19:49:35 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO  [vert.x-worker-thread-1] Added InterfaceId: 1009 
Aug 10 19:49:51 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-2] (un)registerCallback on LegacyServiceHandler called from url: http://192.168.2.77:12010 
Aug 10 19:49:51 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-2] init finished 
Aug 10 19:49:51 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO  [vert.x-worker-thread-4] Added InterfaceId: hm-rpc.1 
Aug 10 19:53:21 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-3] (un)registerCallback on LegacyServiceHandler called from url: http://192.168.2.77:12010 
Aug 10 19:53:21 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-3] init finished 
Aug 10 19:53:21 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO  [vert.x-worker-thread-4] Added InterfaceId: hm-rpc.1 
Aug 10 19:54:05 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-4] SYSTEM: 0 Accesspoints in Queue 
Aug 10 19:54:05 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-4] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Aug 10 19:54:05 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-4] SYSTEM: Eventlistener Handler utilization: 0/50 used 

Kann man da was rauslesen ob es da Kontakt zwischen beiden Geräten gibt?

VG

Familienvater
Beiträge: 6289
Registriert: 31.12.2006, 16:18
Wohnort: Rhein-Main

Re: Geräte anlernen klappt nicht

Beitrag von Familienvater » 10.08.2018, 21:10

Hi,

also ich würde sagen, das Funkmodul funkt (empfängt) auf jeden Fall, weil z.B. auch "fremde" HM-Pakete empfangen werden.

Aber vielleicht solltest Du den ioBroker mal ein bisschen einbremsen, und erst mal die Geräte an der Zentrale hinbekommen, dann kann man sich um die externen Logikschichten kümmern...

Und gibt dem Ding mehr Zeit, von den Zeitstempeln her würde ich behaupten, Du versucht es, bevor HmIP richtig oben ist...

Der Familienvater

deimos
Beiträge: 1342
Registriert: 20.06.2017, 10:38
Wohnort: Leimersheim
Kontaktdaten:

Re: Geräte anlernen klappt nicht

Beitrag von deimos » 10.08.2018, 21:55

Hi,

bist du sicher, dass du den richtigen Anlernbutton in der CCU verwendest? Im letzten Log meldet der rfd, also der Prozess für Homematic und nicht der für HmIP, dass der Anlernmodus verlassen wurde.

Viele Grüße
Alex

Antworten

Zurück zu „piVCCU“