CCU2 als Funk-LAN Gateway

mit der neuen 2514 bekomme ich nun folgende meldungen (inkl. vieler seltsamer Zeichen im Log):

02/01/19 08:17:32.968 HM-LGW "HM-LGW": Warning: Too large packet received: 4830622C30312C526576696C6F2D484D2D4C47572C302E302E322C434355324757303030310D0A
02/01/19 08:17:32.970 HM-LGW "HM-LGW": Error: First packet does not start with "S" or has wrong structure. Please check your AES key in homematicbidcos.conf. Stopping listening.
02/01/19 08:17:42.023 RPC Server (Port 2001): Error: Uninterpretable packet received. Closing connection. Packet was:   J    o megU O   JZ  .      ̩      ̨  =<5/  
 192.168.0.10
3t0.h2h2-16h2-15h2-14spdy/3.1spdy/3http/1.1


02/01/19 08:17:42.032 RPC Server (Port 2001): Error: Uninterpretable packet received. Closing connection. Packet was:    G U  $+  b  {NH ^ <      ̩      ̨  =<5/  
  kg93 192.168.0.10
3t0.h2h2-16h2-15h2-14spdy/3.1spdy/3http/1.1


02/01/19 08:17:42.039 RPC Server (Port 2001): Error: Uninterpretable packet received. Closing connection. Packet was:     k A	  
Őa @ /  X     5/  
Vw 192.168.0.103t0.h2h2-16h2-15h2-14spdy/3.1spdy/3http/1.1


02/01/19 08:17:42.898 RPC Server (Port 2001): Error: Uninterpretable packet received. Closing connection. Packet was:    a^   
M ʺcI  O   #.      ̩      ̨  =<5/  
 192.168.0.10
3t0.h2h2-16h2-15h2-14spdy/3.1spdy/3http/1.1


02/01/19 08:17:42.909 RPC Server (Port 2001): Error: Uninterpretable packet received. Closing connection. Packet was:   Kt, k ?s   ) 2T    <      ̩      ̨  =<5/  
  kg93 192.168.0.10
3t0.h2h2-16h2-15h2-14spdy/3.1spdy/3http/1.1


02/01/19 08:17:42.915 RPC Server (Port 2001): Error: Uninterpretable packet received. Closing connection. Packet was:    .    	rP 9  :   4     5/  
Vw 192.168.0.103t0.h2h2-16h2-15h2-14spdy/3.1spdy/3http/1.1


02/01/19 08:17:44.969 HM-LGW "HM-LGW": Error: No response received to packet: FD0003000003180A
02/01/19 08:17:44.969 HM-LGW "HM-LGW": Error: Unknown packet received in response to init packet. Reconnecting...
02/01/19 08:17:45.530 RPC Server (Port 2001): Error: Uninterpretable packet received. Closing connection. Packet was:   =   
d -       7 T.      ̩      ̨  =<5/  
 192.168.0.10
3t0.h2h2-16h2-15h2-14spdy/3.1spdy/3http/1.1


02/01/19 08:17:45.535 RPC Server (Port 2001): Error: Uninterpretable packet received. Closing connection. Packet was:     M>K oV  v  =A \    <      ̩      ̨  =<5/  
  kg93 192.168.0.10
3t0.h2h2-16h2-15h2-14spdy/3.1spdy/3http/1.1


02/01/19 08:17:45.542 RPC Server (Port 2001): Error: Uninterpretable packet received. Closing connection. Packet was:   Hh@  "Q 
 ٦           5/  
Vw 192.168.0.103t0.h2h2-16h2-15h2-14spdy/3.1spdy/3http/1.1


02/01/19 08:17:54.373 RPC Server (Port 2001): Error: Uninterpretable packet received. Closing connection. Packet was:     6 ˙j۝     P: QW4 .      ̩      ̨  =<5/  
 192.168.0.10
3t0.h2h2-16h2-15h2-14spdy/3.1spdy/3http/1.1


02/01/19 08:17:54.402 RPC Server (Port 2001): Error: Uninterpretable packet received. Closing connection. Packet was:   G @_#  n l  ָ8i IMe  <      ̩      ̨  =<5/  
  kg93 192.168.0.10
3t0.h2h2-16h2-15h2-14spdy/3.1spdy/3http/1.1


02/01/19 08:17:54.407 RPC Server (Port 2001): Error: Uninterpretable packet received. Closing connection. Packet was:       f "    r 7` 1Ïe    5/  
Vw 192.168.0.103t0.h2h2-16h2-15h2-14spdy/3.1spdy/3http/1.1

Hallo @nicx,

probier mal statt der HM-LGW-Konfiguration die HM-CFG-LAN-Konfiguration. Die Pakete sehen eher danach aus. Geht es damit?

Viele Grüße

Sathya

Hallo @nicx,

probier mal statt der HM-LGW-Konfiguration die HM-CFG-LAN-Konfiguration. Die Pakete sehen eher danach aus. Geht es damit?

Nein, doch HM-LGW, es wird nur ein Paket, welches mit Hxx, started vorab gesendet. Ich habe mir den Quelltext (https://github.com/jp112sdl/CCU2GW/blob/master/src/hmlangw.cpp) mal angesehen und den Homegearquelltext angepasst. Klappt es mit dem nächsten Nightly (Docker kann leider zwei Tage dauern)?

Viele Grüße

Sathya

1 Like

@sathya mit der nightly 2518 leider immer noch fehler, dazu noch ein abbruch von homegear mit “signal 11”:

02/06/19 08:16:16.684 RPC Server (Port 2001): Warning: SSL is not enabled for this RPC server. It is strongly recommended to disabl
e all unencrypted RPC servers when the connected clients support it.                                                               
02/06/19 08:16:16.684 RPC Server (Port 2001): Warning: RPC server has no authorization enabled. Everybody on your local network can
 login into this installation. It is strongly recommended to enable authorization on all RPC servers when the connected clients sup
port it.                                                                                                                           
02/06/19 08:16:16.685 RPC Server (Port 2002): Warning: RPC server has no authorization enabled. Everybody on your local network can
 login into this installation. It is strongly recommended to enable authorization on all RPC servers when the connected clients sup
port it.                                                                                                                           
02/06/19 08:16:16.708 RPC Server (Port 2002): Error: Could not load DH parameter file "/etc/homegear/dh1024.pem": No such file or d
irectory                                                                                                                           
02/06/19 08:16:16.730 RPC Server (Port 2003): Error: Could not load DH parameter file "/etc/homegear/dh1024.pem": No such file or d
irectory                                                                                                                           
02/06/19 08:16:16.744 Startup complete. Waiting for physical interfaces to connect.                                                
02/06/19 08:16:16.744 All physical interfaces are connected now.                                                                   
02/06/19 08:16:17.733 HM-LGW "HM-LGW": Warning: Too large packet received: 4832662C30312C526576696C6F2D484D2D4C47572C302E302E322C43
4355324757303030310D0A                                                                                                             
02/06/19 08:16:17.735 HM-LGW "HM-LGW": Error: First packet does not start with "S" or has wrong structure. Please check your AES ke
y in homematicbidcos.conf. Stopping listening.                                                                                     
02/06/19 08:16:18.621 Signal 11 received.                                                                                          
02/06/19 08:16:18.632 Homegear was terminated. Restarting (1)...

Hallo @nicx,

ich werde am Freitag mal eine CCU2 als Gateway umfunktionieren und es bei mir zum Laufen bringen.

Viele Grüße

Sathya

Hallo @nicx,

sollte im nächsten Nightly funktionieren :wink: (Revision bleibt 2518, da nur das BidCoS-Modul geändert wurde):

02/06/19 11:34:31.999 Debug: Connected to host 192.168.0.134 on port 2001. Client number is: 10
02/06/19 11:34:31.999 Debug: Connected to host 192.168.0.134 on port 2000. Client number is: 9
02/06/19 11:34:32.027 HM-LGW "My-HM-LGW": Info: Init packet received: H05,01,Revilo-HM-LGW,0.0.2,HGCCU00001
02/06/19 11:34:32.027 HM-LGW "My-HM-LGW": Debug: Packet received on port 2001: H05,01,Revilo-HM-LGW,0.0.2,HGCCU00001
02/06/19 11:34:32.027 HM-LGW "My-HM-LGW": Info: Keep alive init packet received: H05,01,Revilo-HM-LGW,0.0.2,HGCCU00001
02/06/19 11:34:32.054 HM-LGW "My-HM-LGW": Debug: Packet received on port 2000: S06,BidCoS-over-LAN-1.0\r\n
02/06/19 11:34:32.054 HM-LGW "My-HM-LGW": Debug: Packet received on port 2001: S06,SysCom-1.0
02/06/19 11:34:32.055 HM-LGW "My-HM-LGW": Debug: Sending (Port 2001): >00,0000
02/06/19 11:34:32.055 HM-LGW "My-HM-LGW": Debug: Sending (Port 2000): 3E30362C303030300D0A
02/06/19 11:34:32.055 HM-LGW "My-HM-LGW": Debug: Sending (Port 2001): L00,02,00FF,00
02/06/19 11:34:32.108 HM-LGW "My-HM-LGW": Debug: Packet received on port 2001: >L00
02/06/19 11:34:32.108 HM-LGW "My-HM-LGW": Debug: Keep alive response received on port 2001.
02/06/19 11:34:32.108 HM-LGW "My-HM-LGW": Debug: Sending (Port 2001): K01
02/06/19 11:34:32.136 HM-LGW "My-HM-LGW": Debug: Packet received on port 2001: >K01
02/06/19 11:34:32.136 HM-LGW "My-HM-LGW": Debug: Keep alive response received on port 2001.
02/06/19 11:34:33.055 HM-LGW "My-HM-LGW": Debug: Sending (Port 2000): FD0003000003180A
02/06/19 11:34:33.789 HM-LGW "My-HM-LGW": Debug: Packet received from HM-LGW on port 2000: FD000400000401993D
02/06/19 11:34:33.859 HM-LGW "My-HM-LGW": Debug: Packet received from HM-LGW on port 2000: FD000D000000436F5F4350555F417070D831
02/06/19 11:34:33.859 HM-LGW "My-HM-LGW": Debug: Co_CPU_App packet received.
02/06/19 11:34:33.860 HM-LGW "My-HM-LGW": Debug: Sending (Port 2000): FD00030001021E0C
02/06/19 11:34:33.890 HM-LGW "My-HM-LGW": Debug: Packet received from HM-LGW on port 2000: FD000A00010402010005010401C68A
02/06/19 11:34:33.890 HM-LGW "My-HM-LGW": Info: Firmware version: 1.4.1
02/06/19 11:34:33.890 HM-LGW "My-HM-LGW": Debug: Sending (Port 2000): FD000400020A003D10
02/06/19 11:34:33.920 HM-LGW "My-HM-LGW": Debug: Packet received from HM-LGW on port 2000: FD0004000204011916
02/06/19 11:34:33.921 HM-LGW "My-HM-LGW": Debug: Sending (Port 2000): FD000300030B9239
02/06/19 11:34:33.952 HM-LGW "My-HM-LGW": Debug: Packet received from HM-LGW on port 2000: FD000E000304024B455130313132393037E30A
02/06/19 11:34:33.952 HM-LGW "My-HM-LGW": Info: Serial number: KEQ0112907
02/06/19 11:34:33.952 HM-LGW "My-HM-LGW": Debug: Sending (Port 2000): FD000800040E5C5AB83902A578
02/06/19 11:34:33.983 HM-LGW "My-HM-LGW": Debug: Packet received from HM-LGW on port 2000: FD000400040401196E
02/06/19 11:34:33.983 HM-LGW "My-HM-LGW": Debug: Sending (Port 2000): FD001401050300112233445566778899AABBCCDDEEFF014C67
02/06/19 11:34:34.015 HM-LGW "My-HM-LGW": Debug: Packet received from HM-LGW on port 2000: FD0004010504010D7A
02/06/19 11:34:34.015 HM-LGW "My-HM-LGW": Debug: Sending (Port 2000): FD0006010600FC7D0C2E5960
02/06/19 11:34:34.047 HM-LGW "My-HM-LGW": Debug: Packet received from HM-LGW on port 2000: FD0004010604010D46
02/06/19 11:34:34.047 HM-LGW "My-HM-LGW": Debug: Sending (Port 2000): FD00030007068A17
02/06/19 11:34:34.078 HM-LGW "My-HM-LGW": Debug: Packet received from HM-LGW on port 2000: FD0004000704011952
02/06/19 11:34:34.078 HM-LGW "My-HM-LGW": Info: Init queue completed. Sending peers...
02/06/19 11:34:34.078 HM-LGW "My-HM-LGW": Debug: Sending peer to LGW "My-HM-LGW": Address 27775A, AES enabled 0, AES map 00.
02/06/19 11:34:34.078 HM-LGW "My-HM-LGW": Debug: Sending (Port 2000): FD000901080627775A000000B77E
02/06/19 11:34:34.111 HM-LGW "My-HM-LGW": Debug: Packet received from HM-LGW on port 2000: FD00100108040701010001FFFFFFFFFFFFFFFFCAAF
02/06/19 11:34:34.111 HM-LGW "My-HM-LGW": Debug: Sending (Port 2000): FD000901090627775A000000A778
02/06/19 11:34:34.143 HM-LGW "My-HM-LGW": Debug: Packet received from HM-LGW on port 2000: FD00100109040701010001FFFFFFFFFFFFFFFFCBA9
02/06/19 11:34:34.144 HM-LGW "My-HM-LGW": Debug: Sending (Port 2000): FD0009010A0A27775A0001029DBE
02/06/19 11:34:34.180 HM-LGW "My-HM-LGW": Debug: Packet received from HM-LGW on port 2000: FD0004010A04010DB6
02/06/19 11:34:34.180 HM-LGW "My-HM-LGW": Debug: Sending (Port 2000): FD0009010B0627775A0000008774
02/06/19 11:34:34.213 HM-LGW "My-HM-LGW": Debug: Packet received from HM-LGW on port 2000: FD0010010B040701010001FFFFFFFFFFFFFFFFC9A5
02/06/19 11:34:34.213 HM-LGW "My-HM-LGW": Debug: Sending (Port 2000): FD0009010C0627775A000000F766
02/06/19 11:34:34.245 HM-LGW "My-HM-LGW": Debug: Packet received from HM-LGW on port 2000: FD0010010C040701010001FFFFFFFFFFFFFFFFCEB7
02/06/19 11:34:34.245 HM-LGW "My-HM-LGW": Debug: Sending peer to LGW "My-HM-LGW": Address 2F4664, AES enabled 0, AES map 00.
02/06/19 11:34:34.246 HM-LGW "My-HM-LGW": Debug: Sending (Port 2000): FD0009010D062F4664000000B79B
02/06/19 11:34:34.278 HM-LGW "My-HM-LGW": Debug: Packet received from HM-LGW on port 2000: FD0010010D040701010002FFFFFFFFFFFFFFFFC511
02/06/19 11:34:34.279 HM-LGW "My-HM-LGW": Debug: Sending (Port 2000): FD0009010E062F46640000008791
02/06/19 11:34:34.311 HM-LGW "My-HM-LGW": Debug: Packet received from HM-LGW on port 2000: FD0010010E040701010002FFFFFFFFFFFFFFFFC61B
02/06/19 11:34:34.311 HM-LGW "My-HM-LGW": Debug: Sending (Port 2000): FD000B010F0A2F466400010203044537
02/06/19 11:34:34.348 HM-LGW "My-HM-LGW": Debug: Packet received from HM-LGW on port 2000: FD0004010F04010DF2
02/06/19 11:34:34.348 HM-LGW "My-HM-LGW": Debug: Sending (Port 2000): FD00090110062F4664000000E7D0
02/06/19 11:34:34.380 HM-LGW "My-HM-LGW": Debug: Packet received from HM-LGW on port 2000: FD00100110040701010002FFFFFFFFFFFFFFFFD85F
02/06/19 11:34:34.381 HM-LGW "My-HM-LGW": Debug: Sending (Port 2000): FD00090111062F466401000077C1
02/06/19 11:34:34.413 HM-LGW "My-HM-LGW": Debug: Packet received from HM-LGW on port 2000: FD00100111040701010002FFFFFFFFFFFFFFFFD959
02/06/19 11:34:34.413 HM-LGW "My-HM-LGW": Info: Peer sending completed.


02/06/19 11:34:34.795 HM-LGW "My-HM-LGW": Debug: Packet received from HM-LGW on port 2000: FD0013010005000053B2A6411C54F9FD000101FC25618CB7
02/06/19 11:34:34.795 Debug (My-HM-LGW): Packet 0DB2A6411C54F9FD000101FC2561 enters raisePacketReceived.
02/06/19 11:34:34.795 Debug (My-HM-LGW): Packet 0DB2A6411C54F9FD000101FC2561 is now passed to the EventHandler.
02/06/19 11:34:34.795 HomeMatic BidCoS packet received (My-HM-LGW, RSSI: -83 dBm): 0DB2A6411C54F9FD000101FC2561
02/06/19 11:34:34.795 Devlog (My-HM-LGW): Getting peer for packet 0DB2A6411C54F9FD000101FC2561.
02/06/19 11:34:34.795 Devlog (My-HM-LGW): Packet 0DB2A6411C54F9FD000101FC2561 is now passed to _receivedPackets.set.
02/06/19 11:34:34.796 Devlog (My-HM-LGW): _receivedPackets.set finished.
02/06/19 11:34:34.796 Debug (My-HM-LGW): Packet processing of packet 0DB2A6411C54F9FD000101FC2561 took 1 ms.


02/06/19 11:34:36.798 HM-LGW "My-HM-LGW": Debug: Sending (Port 2000): FD0003001208F433
02/06/19 11:34:36.828 HM-LGW "My-HM-LGW": Debug: Packet received from HM-LGW on port 2000: FD000500120402002450
02/06/19 11:34:36.828 HM-LGW "My-HM-LGW": Debug: Keep alive response received on port 2000.


02/06/19 11:34:38.515 HM-LGW "My-HM-LGW": Debug: Packet received from HM-LGW on port 2000: FD00130101050000513B84101B9187FD0001060154007609
02/06/19 11:34:38.515 Debug (My-HM-LGW): Packet 0D3B84101B9187FD000106015400 enters raisePacketReceived.
02/06/19 11:34:38.515 Debug (My-HM-LGW): Packet 0D3B84101B9187FD000106015400 is now passed to the EventHandler.
02/06/19 11:34:38.515 HomeMatic BidCoS packet received (My-HM-LGW, RSSI: -81 dBm): 0D3B84101B9187FD000106015400
02/06/19 11:34:38.515 Devlog (My-HM-LGW): Getting peer for packet 0D3B84101B9187FD000106015400.
02/06/19 11:34:38.516 Devlog (My-HM-LGW): Packet 0D3B84101B9187FD000106015400 is now passed to _receivedPackets.set.
02/06/19 11:34:38.516 Devlog (My-HM-LGW): _receivedPackets.set finished.
02/06/19 11:34:38.516 Debug (My-HM-LGW): Packet processing of packet 0D3B84101B9187FD000106015400 took 1 ms.


02/06/19 11:34:38.967 HM-LGW "My-HM-LGW": Debug: Packet received from HM-LGW on port 2000: FD001101020500004A1FA2581D94A81C4A100200FE25
02/06/19 11:34:38.967 Debug (My-HM-LGW): Packet 0B1FA2581D94A81C4A100200 enters raisePacketReceived.
02/06/19 11:34:38.967 Debug (My-HM-LGW): Packet 0B1FA2581D94A81C4A100200 is now passed to the EventHandler.
02/06/19 11:34:38.967 HomeMatic BidCoS packet received (My-HM-LGW, RSSI: -74 dBm): 0B1FA2581D94A81C4A100200
02/06/19 11:34:38.967 Devlog (My-HM-LGW): Getting peer for packet 0B1FA2581D94A81C4A100200.
02/06/19 11:34:38.967 Devlog (My-HM-LGW): Packet 0B1FA2581D94A81C4A100200 is now passed to _receivedPackets.set.
02/06/19 11:34:38.967 Devlog (My-HM-LGW): _receivedPackets.set finished.
02/06/19 11:34:38.967 Debug (My-HM-LGW): Packet processing of packet 0B1FA2581D94A81C4A100200 took 0 ms.


02/06/19 11:34:39.099 HM-LGW "My-HM-LGW": Debug: Packet received from HM-LGW on port 2000: FD00140103050000421F82021C4A101D94A80101000040DC59
02/06/19 11:34:39.099 Debug (My-HM-LGW): Packet 0E1F82021C4A101D94A80101000040 enters raisePacketReceived.
02/06/19 11:34:39.099 Debug (My-HM-LGW): Packet 0E1F82021C4A101D94A80101000040 is now passed to the EventHandler.
02/06/19 11:34:39.099 HomeMatic BidCoS packet received (My-HM-LGW, RSSI: -66 dBm): 0E1F82021C4A101D94A80101000040
02/06/19 11:34:39.099 Devlog (My-HM-LGW): Getting peer for packet 0E1F82021C4A101D94A80101000040.
02/06/19 11:34:39.099 Devlog (My-HM-LGW): Packet 0E1F82021C4A101D94A80101000040 is now passed to _receivedPackets.set.
02/06/19 11:34:39.099 Devlog (My-HM-LGW): _receivedPackets.set finished.
02/06/19 11:34:39.099 Debug (My-HM-LGW): Packet processing of packet 0E1F82021C4A101D94A80101000040 took 0 ms.


02/06/19 11:34:41.101 HM-LGW "My-HM-LGW": Debug: Sending (Port 2000): FD00030013087230
02/06/19 11:34:41.132 HM-LGW "My-HM-LGW": Debug: Packet received from HM-LGW on port 2000: FD00050013040200B053
02/06/19 11:34:41.132 HM-LGW "My-HM-LGW": Debug: Keep alive response received on port 2000.


02/06/19 11:34:41.464 HM-LGW "My-HM-LGW": Debug: Packet received from HM-LGW on port 2000: FD001101040500005195A2581D8D131DA44C00188E9F
02/06/19 11:34:41.464 Debug (My-HM-LGW): Packet 0B95A2581D8D131DA44C0018 enters raisePacketReceived.
02/06/19 11:34:41.465 Debug (My-HM-LGW): Packet 0B95A2581D8D131DA44C0018 is now passed to the EventHandler.
02/06/19 11:34:41.464 HomeMatic BidCoS packet received (My-HM-LGW, RSSI: -81 dBm): 0B95A2581D8D131DA44C0018
02/06/19 11:34:41.465 Devlog (My-HM-LGW): Getting peer for packet 0B95A2581D8D131DA44C0018.
02/06/19 11:34:41.465 Devlog (My-HM-LGW): Packet 0B95A2581D8D131DA44C0018 is now passed to _receivedPackets.set.
02/06/19 11:34:41.465 Devlog (My-HM-LGW): _receivedPackets.set finished.
02/06/19 11:34:41.465 Debug (My-HM-LGW): Packet processing of packet 0B95A2581D8D131DA44C0018 took 0 ms.


02/06/19 11:34:41.597 HM-LGW "My-HM-LGW": Debug: Packet received from HM-LGW on port 2000: FD00140105050000549582021DA44C1D8D13010112002EE5D0
02/06/19 11:34:41.597 Debug (My-HM-LGW): Packet 0E9582021DA44C1D8D13010112002E enters raisePacketReceived.
02/06/19 11:34:41.598 Debug (My-HM-LGW): Packet 0E9582021DA44C1D8D13010112002E is now passed to the EventHandler.
02/06/19 11:34:41.597 HomeMatic BidCoS packet received (My-HM-LGW, RSSI: -84 dBm): 0E9582021DA44C1D8D13010112002E
02/06/19 11:34:41.598 Devlog (My-HM-LGW): Getting peer for packet 0E9582021DA44C1D8D13010112002E.
02/06/19 11:34:41.598 Devlog (My-HM-LGW): Packet 0E9582021DA44C1D8D13010112002E is now passed to _receivedPackets.set.
02/06/19 11:34:41.598 Devlog (My-HM-LGW): _receivedPackets.set finished.
02/06/19 11:34:41.598 Debug (My-HM-LGW): Packet processing of packet 0E9582021DA44C1D8D13010112002E took 0 ms.


02/06/19 11:34:42.147 HM-LGW "My-HM-LGW": Debug: Sending (Port 2001): K02
02/06/19 11:34:42.175 HM-LGW "My-HM-LGW": Debug: Packet received on port 2001: >K02
02/06/19 11:34:42.175 HM-LGW "My-HM-LGW": Debug: Keep alive response received on port 2001.


02/06/19 11:34:42.810 HM-LGW "My-HM-LGW": Debug: Packet received from HM-LGW on port 2000: FD001301060500004AC684101C573BFD000106012700A093
02/06/19 11:34:42.810 Debug (My-HM-LGW): Packet 0DC684101C573BFD000106012700 enters raisePacketReceived.
02/06/19 11:34:42.810 Debug (My-HM-LGW): Packet 0DC684101C573BFD000106012700 is now passed to the EventHandler.
02/06/19 11:34:42.810 HomeMatic BidCoS packet received (My-HM-LGW, RSSI: -74 dBm): 0DC684101C573BFD000106012700
02/06/19 11:34:42.810 Devlog (My-HM-LGW): Getting peer for packet 0DC684101C573BFD000106012700.
02/06/19 11:34:42.811 Devlog (My-HM-LGW): Packet 0DC684101C573BFD000106012700 is now passed to _receivedPackets.set.
02/06/19 11:34:42.811 Devlog (My-HM-LGW): _receivedPackets.set finished.
02/06/19 11:34:42.811 Debug (My-HM-LGW): Packet processing of packet 0DC684101C573BFD000106012700 took 1 ms.


02/06/19 11:34:46.815 HM-LGW "My-HM-LGW": Debug: Sending (Port 2000): FD0003001408E033
02/06/19 11:34:46.846 HM-LGW "My-HM-LGW": Debug: Packet received from HM-LGW on port 2000: FD000500140402005C50
02/06/19 11:34:46.846 HM-LGW "My-HM-LGW": Debug: Keep alive response received on port 2000.


02/06/19 11:34:51.851 HM-LGW "My-HM-LGW": Debug: Sending (Port 2000): FD00030015086630
02/06/19 11:34:51.882 HM-LGW "My-HM-LGW": Debug: Packet received from HM-LGW on port 2000: FD00050015040200C853
02/06/19 11:34:51.882 HM-LGW "My-HM-LGW": Debug: Keep alive response received on port 2000.


02/06/19 11:34:52.186 HM-LGW "My-HM-LGW": Debug: Sending (Port 2001): K03
02/06/19 11:34:52.214 HM-LGW "My-HM-LGW": Debug: Packet received on port 2001: >K03
02/06/19 11:34:52.214 HM-LGW "My-HM-LGW": Debug: Keep alive response received on port 2001.

Ich habe leider kein Senden von Paketen testen können, da ich remote auf die CCU zugreife. Also bitte ich um einen Test. Auch interessant zu wissen wäre, ob sendFix in der Konfiguration true oder false sein muss.

Viele Grüße

Sathya

1 Like

Hi @sathya, wollte das eben testen, aber mit dem aktuellen nightly hängt Homegear in einer Rebbot Schleife fest:

02/08/19 10:05:09.174 Module HomeMatic BidCoS: Loading peer 53                                                                     
02/08/19 10:05:09.186 Module HomeMatic BidCoS: Loading peer 54                                                                     
02/08/19 10:05:09.188 Module HomeMatic BidCoS: Loading peer 56                                                                     
02/08/19 10:05:09.200 Module HomeMatic BidCoS: Loading peer 57                                                                     
02/08/19 10:05:09.202 Module HomeMatic BidCoS: Loading peer 58                                                                     
02/08/19 10:05:09.204 Module HomeMatic BidCoS: Loading peer 59                                                                     
02/08/19 10:05:09.206 Module HomeMatic BidCoS: Loading peer 60                                                                     
02/08/19 10:05:09.212 Module HomeMatic BidCoS: Loading peer 61                                                                     
02/08/19 10:05:09.224 Module HomeMatic BidCoS: Loading peer 62                                                                     
02/08/19 10:05:09.226 Module HomeMatic BidCoS: Loading peer 63                                                                     
02/08/19 10:05:09.228 Module HomeMatic BidCoS: Loading peer 65                                                                     
02/08/19 10:05:09.230 Module HomeMatic BidCoS: Loading peer 66                                                                     
02/08/19 10:05:09.236 Module HomeMatic BidCoS: Loading peer 67                                                                     
02/08/19 10:05:09.238 Module HomeMatic BidCoS: Loading peer 68                                                                     
02/08/19 10:05:09.240 Module HomeMatic BidCoS: Loading peer 69                                                                     
02/08/19 10:05:09.242 Module HomeMatic BidCoS: Loading peer 72                                                                     
02/08/19 10:05:09.247 Loading device 17                                                                                            
02/08/19 10:05:09.248 Loading device 14                                                                                            
02/08/19 10:05:09.249 Loading device 15                                                                                            
02/08/19 10:05:09.271 Loading device 4                                                                                             
02/08/19 10:05:09.273 RPC Server (Port 2001): Warning: SSL is not enabled for this RPC server. It is strongly recommended to disabl
e all unencrypted RPC servers when the connected clients support it.                                                               
02/08/19 10:05:09.273 RPC Server (Port 2001): Warning: RPC server has no authorization enabled. Everybody on your local network can
 login into this installation. It is strongly recommended to enable authorization on all RPC servers when the connected clients sup
port it.                                                                                                                           
02/08/19 10:05:09.274 RPC Server (Port 2002): Warning: RPC server has no authorization enabled. Everybody on your local network can
 login into this installation. It is strongly recommended to enable authorization on all RPC servers when the connected clients sup
port it.                                                                                                                           
02/08/19 10:05:09.367 Startup complete. Waiting for physical interfaces to connect.                                                
02/08/19 10:05:09.367 All physical interfaces are connected now.                                                                   
02/08/19 10:05:10.356 HM-LGW "HM-LGW": Warning: Connection to client number 13 closed (3).                                         
02/08/19 10:05:10.773 Signal 11 received.                                                                                          
02/08/19 10:05:10.804 Homegear was terminated. Restarting (1)...                                                                   

Nachtrag: es schein ein generelleres Problem mit dem aktuellen Nightly zu sein, wenn ich das Gateway auskommentiere passiert ebenfalls das gleiche…

und noch ein nachtrag: es liegt am modul bidcos, wenn das nicht aktiv ist läuft homegear ohne “signal 11” reboot schleife. Hier noch ein etwas ausfürlicheres Log:

02/08/19 10:20:47.670 All physical interfaces are connected now.
02/08/19 10:20:47.671 Starting UPnP server...
02/08/19 10:20:47.671 Info: UPnP server: Binding to address: 192.168.0.10
02/08/19 10:20:47.671 UPnP Server: Info: Started listening.
02/08/19 10:20:47.981 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-EG": Info: Initialization completed.
02/08/19 10:20:48.000 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-OG": Info: Initialization completed.
02/08/19 10:20:48.658 HM-LGW "HM-LGW": Warning: Connection to client number 11 closed (3).
02/08/19 10:20:48.659 HM-LGW "HM-LGW": Info: Keep alive init packet received: H9f,01,Revilo-HM-LGW,0.0.2,CCU2GW0001
02/08/19 10:20:48.871 IPC Server: Info: Connection accepted. Client number: 13
02/08/19 10:20:48.872 IPC Server: Info: Client 0 successfully registered RPC method "managementGetCommandStatus" (this method is registered by 1 client(s)).
02/08/19 10:20:48.872 IPC Server: Info: Client 0 successfully registered RPC method "managementSleep" (this method is registered by 1 client(s)).
02/08/19 10:20:48.872 IPC Server: Info: Client 0 successfully registered RPC method "managementDpkgPackageInstalled" (this method is registered by 1 client(s)).
02/08/19 10:20:48.872 IPC Server: Info: Client 0 successfully registered RPC method "managementGetConfigurationEntry" (this method is registered by 1 client(s)).
02/08/19 10:20:48.873 IPC Server: Info: Client 0 successfully registered RPC method "managementServiceCommand" (this method is registered by 1 client(s)).
02/08/19 10:20:48.873 IPC Server: Info: Client 0 successfully registered RPC method "managementReboot" (this method is registered by 1 client(s)).
02/08/19 10:20:48.873 IPC Server: Info: Client 0 successfully registered RPC method "managementSetConfigurationEntry" (this method is registered by 1 client(s)).
02/08/19 10:20:48.873 IPC Server: Info: Client 0 successfully registered RPC method "managementWriteCloudMaticConfig" (this method is registered by 1 client(s)).
02/08/19 10:20:48.874 IPC Server: Info: Client 0 successfully registered RPC method "managementSetUserPassword" (this method is registered by 1 client(s)).
02/08/19 10:20:48.874 IPC Server: Info: Client 0 successfully registered RPC method "managementAptUpdate" (this method is registered by 1 client(s)).
02/08/19 10:20:48.874 IPC Server: Info: Client 0 successfully registered RPC method "managementAptUpgrade" (this method is registered by 1 client(s)).
02/08/19 10:20:48.874 IPC Server: Info: Client 0 successfully registered RPC method "managementAptFullUpgrade" (this method is registered by 1 client(s)).
02/08/19 10:20:48.874 IPC Server: Info: Client 0 successfully registered RPC method "managementHomegearUpdateAvailable" (this method is registered by 1 client(s)).
02/08/19 10:20:48.874 IPC Server: Info: Client 0 successfully registered RPC method "managementSystemUpdateAvailable" (this method is registered by 1 client(s)).
02/08/19 10:20:48.875 IPC Server: Info: Client 0 successfully registered RPC method "managementCreateBackup" (this method is registered by 1 client(s)).
02/08/19 10:20:48.875 IPC Server: Info: Client 0 successfully registered RPC method "managementRestoreBackup" (this method is registered by 1 client(s)).
02/08/19 10:20:48.875 IPC Server: Info: Client 0 successfully registered RPC method "managementCaExists" (this method is registered by 1 client(s)).
02/08/19 10:20:48.876 IPC Server: Info: Client 0 successfully registered RPC method "managementCreateCa" (this method is registered by 1 client(s)).
02/08/19 10:20:48.876 IPC Server: Info: Client 0 successfully registered RPC method "managementCreateCert" (this method is registered by 1 client(s)).
02/08/19 10:20:48.876 IPC Server: Info: Client 0 successfully registered RPC method "managementDeleteCert" (this method is registered by 1 client(s)).
02/08/19 10:20:48.876 IPC Server: Info: Client 0 successfully registered RPC method "managementGetNetworkConfiguration" (this method is registered by 1 client(s)).
02/08/19 10:20:48.877 IPC Server: Info: Client 0 successfully registered RPC method "managementSetNetworkConfiguration" (this method is registered by 1 client(s)).
02/08/19 10:20:48.877 IPC Server: Info: Client 0 successfully registered RPC method "managementCopyDeviceDescriptionFile" (this method is registered by 1 client(s)).
02/08/19 10:20:48.938 IPC Server: Info: Connection accepted. Client number: 14
02/08/19 10:20:48.938 IPC Server: Info: Client 1 successfully registered RPC method "websshGetLastOutputs" (this method is registered by 1 client(s)).
02/08/19 10:20:48.939 IPC Server: Info: Client 1 successfully registered RPC method "websshInput" (this method is registered by 1 client(s)).
02/08/19 10:20:48.939 IPC Server: Info: Client 1 successfully registered RPC method "websshSetScreenSize" (this method is registered by 1 client(s)).
02/08/19 10:20:57.422 Signal 11 received.
02/08/19 10:20:57.480 Info: Process with id 8277 ended.
02/08/19 10:20:57.480 Homegear was terminated. Restarting (1)...

wenn du weitere Infos brauchst @sathya dann gerne :slight_smile:

Hallo @nicx,

welches Docker-Image bzw. welches Betriebssystem verwendest du? Schick mir mal den Coredump (/var/lib/homegear/core oder /var/log/homegear/core). Darin ist direkt sichtbar, warum er abstürzt. Üblicherweise ist irgendetwas noch nicht initialisiert (irgendein Zeiger auf den zugegriffen wird steht vermutlich noch auf nullptr), von daher wird es mit den HM-LGW-Änderungen zusammenhängen.

Viele Grüße

Sathya

@sathya Ich nutze das amd64 docker image auf einer Synology Diskstation.

root@ds# uname -a
Linux ds 4.4.59+ #23824 SMP PREEMPT Tue Dec 25 18:27:56 CST 2018 x86_64 GNU/Linux synology_apollolake_718+
root@ds#

Leider finde ich aber in keinem der beiden Verzeichnisse einen core dump. Wo könnte ich noch suchen?

Hallo @nicx,

find / -name core

Es kann natürlich sein, dass Docker keine schreibt, was doof wäre…

Gerade mal geschaut: https://dev.to/mizutani/how-to-get-core-file-of-segmentation-fault-process-in-docker-22ii

Hilft das? Docker macht das Ganze jetzt leider etwas kompliziert… Alternativ könntest du mir über eine PM eine Sicherung von /etc/homegear und von /var/lib/homegear schicken, dann kann ich bei mir schauen, ob ich das Problem direkt reproduziert bekomme.

Viele Grüße

Sathya

Link siehe PM, danke schon mal. Mit der Nighlty 2514 bestand das Problem übrigens noch nicht.

Hallo @nicx,

vielen Dank! Ich habe es mir angesehen, leider läuft es bei mir mit deiner Konfiguration…

Mit der Nighlty 2514 bestand das Problem übrigens noch nicht.

Das wird mit den neu eingebauten Änderungen für das HM-LGW zusammenhängen.

Bekommst du irgendwie Coredumps unter Docker aktiviert? Oder hast du alternativ irgendwo eine VM oder einen Raspberry Pi, wo du Homegear testweise installieren könntest, damit wir einen Coredump bekommen?

Was wir mit geringerem Aufwand noch probieren können: Du kannst mir einmal ein Log vom Absturz auf Loglevel 5 posten. Vielleicht zeigt das ja auch bereits in etwa die Absturzstelle.

Viele Grüße

Sathya

Nachtrag: Ich konnte es jetzt doch reproduzieren und schaue es mir gerade an.

… und Problem gefunden. Ist in 0.8.0-2522 gefixt. Vielen Dank!

Viele Grüße

Sathya

2 Likes

wow super, jetzt wollte ich mich eben an die docker-coredump thematik wagen… aber so ist es nachtürlich klasse :slight_smile: danke!

Rüclmeldung: mit der 2524 funktioniert es nun, zumindest sind die abstürze nicht mehr da und das lan gateway wird “connected” angezeigt. ich bezweifle alledings aufgrund dieser logmeldungen dass es auch wirklich funkitoniert:

02/13/19 08:48:49.146 Startup complete. Waiting for physical interfaces to connect.
02/13/19 08:48:49.146 All physical interfaces are connected now.
02/13/19 08:48:50.135 HM-LGW "HM-LGW": Warning: Connection to client number 11 closed (3).
02/13/19 08:48:50.136 HM-LGW "HM-LGW": Warning: !!!Not!!! sending (Port 2001): >00,0000
02/13/19 08:48:50.136 HM-LGW "HM-LGW": Warning: !!!Not!!! sending (Port 2001): L00,02,00FF,00
02/13/19 08:49:01.135 HM-LGW "HM-LGW": Warning: Connection closed. Trying to reconnect...
02/13/19 08:49:19.135 HM-LGW "HM-LGW": Error: No init packet received.
02/13/19 08:49:19.137 HM-LGW "HM-LGW": Warning: Connection to client number 28 closed (3).
02/13/19 08:49:30.138 HM-LGW "HM-LGW": Warning: Connection closed. Trying to reconnect...
02/13/19 08:49:49.137 HM-LGW "HM-LGW": Error: No init packet received.
02/13/19 08:49:49.139 HM-LGW "HM-LGW": Warning: Connection to client number 47 closed (3).
02/13/19 08:50:00.139 HM-LGW "HM-LGW": Warning: Connection closed. Trying to reconnect...
02/13/19 08:50:19.138 HM-LGW "HM-LGW": Error: No init packet received.
02/13/19 08:50:19.140 HM-LGW "HM-LGW": Warning: Connection to client number 59 closed (3).
02/13/19 08:50:30.141 HM-LGW "HM-LGW": Warning: Connection closed. Trying to reconnect...
02/13/19 08:50:49.140 HM-LGW "HM-LGW": Error: No init packet received.
02/13/19 08:50:49.142 HM-LGW "HM-LGW": Warning: Connection to client number 72 closed (3).
02/13/19 08:51:00.142 HM-LGW "HM-LGW": Warning: Connection closed. Trying to reconnect...

@sathya braucht es da noch nacharbeiten? kann ich dir dafür logs liefern?

Hallo @nicx,

natürlich schön, dass es jetzt nicht mehr abstürzt, aber doof, dass es immer noch nicht funktioniert - es sollte eigentlich. Ich habe es gerade noch einmal getestet, hier klappt die Verbindung zum Gateway und ich empfange Pakete.

Poste vielleicht noch einmal ein Log auf Loglevel 5. Vielleicht gibt das ja Aufschluss, was da schief läuft.

Viele Grüße

Sathya

hier das log mit level 5:

Zusammenfassung
02/14/19 14:08:32.985 Starting Homegear...
02/14/19 14:08:32.985 Starting Homegear...
02/14/19 14:08:32.986 Homegear version 0.8.0-2524
02/14/19 14:08:32.986 Homegear version 0.8.0-2524
02/14/19 14:08:32.986 Git commit SHA of libhomegear-base: -
02/14/19 14:08:32.986 Git commit SHA of libhomegear-base: -
02/14/19 14:08:32.986 Git branch of libhomegear-base:     -
02/14/19 14:08:32.986 Git branch of libhomegear-base:     -
02/14/19 14:08:32.986 Git commit SHA of Homegear:         -
02/14/19 14:08:32.986 Git commit SHA of Homegear:         -
02/14/19 14:08:32.986 Git branch of Homegear:             -
02/14/19 14:08:32.986 Git branch of Homegear:             -
02/14/19 14:08:32.986 Info: Setting allowed core file size to "18446744073709551615" for user with id 0 and group with id 0.
02/14/19 14:08:32.986 Info: Core file size now is "18446744073709551615".
02/14/19 14:08:32.986 Info: Setting maximum thread priority to "100" for user with id 0 and group with id 0.
02/14/19 14:08:32.986 Info: Maximum thread priority now is "100".
02/14/19 14:08:32.993 Info: Setting allowed core file size to "18446744073709551615" for user with id 0 and group with id 0.
02/14/19 14:08:32.993 Info: Core file size now is "18446744073709551615".
02/14/19 14:08:32.993 Info: Setting maximum thread priority to "100" for user with id 0 and group with id 0.
02/14/19 14:08:32.993 Info: Maximum thread priority now is "100".
02/14/19 14:08:33.340 Info: Backing up database...
02/14/19 14:08:33.477 Initializing database...
02/14/19 14:08:33.523 Debug: Loading licensing modules
02/14/19 14:08:33.524 Info: Loading licensing module mod_licensing.so
02/14/19 14:08:33.921 Module Licensing: Debug: Loading module...
02/14/19 14:08:33.921 Info: Loading licensing module mod_easy_licensing.so
02/14/19 14:08:34.076 Module EasyLicensing: Debug: Loading module...
02/14/19 14:08:34.077 Debug: Loading family modules
02/14/19 14:08:34.077 Info: Loading family module (type 1) mod_mbus.so
02/14/19 14:08:34.100 Info: Loading settings from /etc/homegear/families/m-bus.conf
02/14/19 14:08:34.100 Debug: Loading section "General"
02/14/19 14:08:34.101 Debug: Family setting moduleenabled set to false
02/14/19 14:08:34.101 Debug: Family setting securitymodewhitelist set to 7
02/14/19 14:08:34.101 Module M-Bus: Debug: Loading module...
02/14/19 14:08:34.101 Info: Loading family module (type 1) mod_knx.so
02/14/19 14:08:34.104 Info: Loading settings from /etc/homegear/families/knx.conf
02/14/19 14:08:34.104 Debug: Loading section "General"
02/14/19 14:08:34.104 Debug: Family setting moduleenabled set to false
02/14/19 14:08:34.104 Module KNX: Debug: Loading module...
02/14/19 14:08:34.104 Info: Loading family module (type 1) mod_easyled2.so
02/14/19 14:08:34.106 Info: Loading settings from /etc/homegear/families/easyled2.conf
02/14/19 14:08:34.106 Debug: Loading section "General"
02/14/19 14:08:34.106 Debug: Family setting moduleenabled set to false
02/14/19 14:08:34.106 Debug: Loading section "Main Interface"
02/14/19 14:08:34.106 Debug: deviceType set to easyled
02/14/19 14:08:34.106 Module EASYLed 2: Debug: Loading module...
02/14/19 14:08:34.106 Module EASYLed 2: Debug: Creating physical device. Type defined in easyled.conf is: easyled
02/14/19 14:08:34.106 Info: Loading family module (type 1) mod_zwave.so
02/14/19 14:08:34.300 Info: Loading settings from /etc/homegear/families/z-wave.conf
02/14/19 14:08:34.300 Debug: Loading section "General"
02/14/19 14:08:34.300 Module ZWave: Debug: Loading module...
02/14/19 14:08:34.311 Module ZWave: Joining parameters do not match: Speed for command: CHIMNEY_FAN_SPEED_REPORT
02/14/19 14:08:34.311 Module ZWave: Joining parameters do not match: State for command: CHIMNEY_FAN_STATE_REPORT
02/14/19 14:08:34.321 Module ZWave: Joining parameters do not match: Properties1 for command: NODE_ADD_DSK_REPORT
02/14/19 14:08:34.321 Module ZWave: Joining parameters do not match: Properties1 for command: NODE_ADD_KEYS_REPORT
02/14/19 14:08:34.322 Module ZWave: Joining parameters do not match: Test NodeID for command: POWERLEVEL_TEST_NODE_REPORT
02/14/19 14:08:34.322 Module ZWave: Joining parameters do not match: Timeout for command: PROTECTION_TIMEOUT_REPORT
02/14/19 14:08:34.323 Module ZWave: Joining parameters do not match: Local Grouping identifier for command: REMOTE_ASSOCIATION_CONFIGURATION_GET
02/14/19 14:08:34.323 Module ZWave: Joining parameters do not match: Dimming Duration for command: SCENE_ACTUATOR_CONF_REPORT
02/14/19 14:08:34.323 Module ZWave: Joining parameters do not match: Dimming Duration for command: SCENE_CONTROLLER_CONF_REPORT
02/14/19 14:08:34.331 Module ZWave: Joining parameters do not match: Level for command: THERMOSTAT_FAN_MODE_REPORT
02/14/19 14:08:34.335 Module ZWave: Joining parameters do not match: Duration for command: SWITCH_COLOR_REPORT
02/14/19 14:08:34.339 Module ZWave: Joining parameters do not match: Properties1 for command: MAILBOX_CONFIGURATION_REPORT
02/14/19 14:08:34.342 Info: Loading family module (type 1) mod_rsl.so
02/14/19 14:08:34.344 Info: Loading settings from /etc/homegear/families/rsl.conf
02/14/19 14:08:34.349 Module RSL: Debug: Loading module...
02/14/19 14:08:34.350 Info: Loading family module (type 1) mod_philipshue.so
02/14/19 14:08:34.352 Info: Loading settings from /etc/homegear/families/philipshue.conf
02/14/19 14:08:34.352 Debug: Loading section "General"
02/14/19 14:08:34.352 Debug: Family setting moduleenabled set to false
02/14/19 14:08:34.352 Debug: Family setting pollinginterval set to 3000
02/14/19 14:08:34.352 Module Philips hue: Debug: Loading module...
02/14/19 14:08:34.352 Info: Loading family module (type 1) mod_sonos.so
02/14/19 14:08:34.354 Info: Loading settings from /etc/homegear/families/sonos.conf
02/14/19 14:08:34.355 Debug: Loading section "General"
02/14/19 14:08:34.355 Debug: Family setting moduleenabled set to false
02/14/19 14:08:34.355 Debug: Family setting datapath set to /var/lib/homegear/audio
02/14/19 14:08:34.355 Debug: Family setting ttsusername set to 
02/14/19 14:08:34.355 Debug: Family setting ttskey set to 
02/14/19 14:08:34.355 Debug: Family setting readtimeout set to 5000
02/14/19 14:08:34.355 Debug: Family setting tempmaxage set to 720
02/14/19 14:08:34.355 Debug: Loading section "Event Server"
02/14/19 14:08:34.355 Debug: id set to My-Sonos-1234
02/14/19 14:08:34.355 Debug: deviceType set to eventserver
02/14/19 14:08:34.355 Debug: ttsProgram set to homegear -e rs DeviceScripts/Sonos/Polly.php
02/14/19 14:08:34.355 Module Sonos: Debug: Loading module...
02/14/19 14:08:34.355 Module Sonos: Debug: Creating physical device. Type defined in sonos.conf is: eventserver
02/14/19 14:08:34.355 Info: Loading family module (type 1) mod_easyled.so
02/14/19 14:08:34.357 Info: Loading settings from /etc/homegear/families/easyled.conf
02/14/19 14:08:34.357 Debug: Loading section "General"
02/14/19 14:08:34.357 Debug: Family setting moduleenabled set to false
02/14/19 14:08:34.357 Debug: Loading section "Main Interface"
02/14/19 14:08:34.357 Debug: deviceType set to easyled
02/14/19 14:08:34.357 Module EASYLed: Debug: Loading module...
02/14/19 14:08:34.357 Module EASYLed: Debug: Creating physical device. Type defined in easyled.conf is: easyled
02/14/19 14:08:34.357 Info: Loading family module (type 1) mod_intertechno.so
02/14/19 14:08:34.359 Info: Loading settings from /etc/homegear/families/intertechno.conf
02/14/19 14:08:34.359 Debug: Loading section "General"
02/14/19 14:08:34.359 Debug: Family setting moduleenabled set to false
02/14/19 14:08:34.360 Module Intertechno: Debug: Loading module...
02/14/19 14:08:34.360 Info: Loading family module (type 1) mod_ipcam.so
02/14/19 14:08:34.361 Info: Loading settings from /etc/homegear/families/ipcam.conf
02/14/19 14:08:34.361 Debug: Loading section "General"
02/14/19 14:08:34.361 Debug: Family setting moduleenabled set to false
02/14/19 14:08:34.361 Debug: Loading section "Event Server"
02/14/19 14:08:34.361 Debug: id set to My-IpCam
02/14/19 14:08:34.361 Debug: deviceType set to eventserver
02/14/19 14:08:34.362 Module IpCam: Debug: Loading module...
02/14/19 14:08:34.362 Module IpCam: Debug: Creating physical device. Type defined in ipcam.conf is: eventserver
02/14/19 14:08:34.362 Info: Loading family module (type 1) mod_ccu.so
02/14/19 14:08:34.388 Info: Loading settings from /etc/homegear/families/ccu.conf
02/14/19 14:08:34.388 Debug: Loading section "General"
02/14/19 14:08:34.388 Debug: Family setting moduleenabled set to false
02/14/19 14:08:34.388 Debug: Family setting eventserverportrange set to 9000 - 9010
02/14/19 14:08:34.388 Module CCU: Debug: Loading module...
02/14/19 14:08:34.388 Info: Loading family module (type 1) mod_enocean.so
02/14/19 14:08:34.391 Info: Loading settings from /etc/homegear/families/enocean.conf
02/14/19 14:08:34.391 Debug: Loading section "General"
02/14/19 14:08:34.391 Debug: Family setting moduleenabled set to false
02/14/19 14:08:34.391 Debug: Family setting roaming set to true
02/14/19 14:08:34.391 Module EnOcean: Debug: Loading module...
02/14/19 14:08:34.391 Info: Loading family module (type 1) mod_max.so
02/14/19 14:08:34.394 Info: Loading settings from /etc/homegear/families/max.conf
02/14/19 14:08:34.394 Debug: Loading section "General"
02/14/19 14:08:34.394 Debug: Family setting moduleenabled set to false
02/14/19 14:08:34.394 Module MAX: Debug: Loading module...
02/14/19 14:08:34.395 Info: Loading family module (type 1) mod_kodi.so
02/14/19 14:08:34.396 Info: Loading settings from /etc/homegear/families/kodi.conf
02/14/19 14:08:34.396 Debug: Loading section "General"
02/14/19 14:08:34.396 Debug: Family setting moduleenabled set to false
02/14/19 14:08:34.397 Module Kodi: Debug: Loading module...
02/14/19 14:08:34.397 Info: Loading family module (type 1) mod_easycam.so
02/14/19 14:08:34.414 Info: Loading settings from /etc/homegear/families/easycam.conf
02/14/19 14:08:34.415 Debug: Loading section "General"
02/14/19 14:08:34.415 Debug: Family setting moduleenabled set to false
02/14/19 14:08:34.415 Debug: Loading section "Event Server"
02/14/19 14:08:34.415 Debug: id set to My-Event-Server
02/14/19 14:08:34.415 Debug: deviceType set to eventserver
02/14/19 14:08:34.415 Module EasyCam: Debug: Loading module...
02/14/19 14:08:34.415 Module EasyCam: Debug: Creating physical device. Type defined in easycam.conf is: eventserver
02/14/19 14:08:34.415 Info: Loading family module (type 1) mod_homematicbidcos.so
02/14/19 14:08:34.420 Info: Loading settings from /etc/homegear/families/homematicbidcos.conf
02/14/19 14:08:34.420 Debug: Loading section "General"
02/14/19 14:08:34.420 Debug: Family setting moduleenabled set to true
02/14/19 14:08:34.420 Debug: Family setting centraladdress set to 0xfd1309
02/14/19 14:08:34.420 Debug: Family setting rfkey set to 1133009911997766ddeeaaddbbeeeeff
02/14/19 14:08:34.420 Debug: Family setting currentrfkeyindex set to 1
02/14/19 14:08:34.420 Debug: Family setting processbroadcastwithaesenabled set to false
02/14/19 14:08:34.420 Debug: Loading section "HomeMatic Wireless LAN Gateway"
02/14/19 14:08:34.420 Debug: id set to HM-LGW
02/14/19 14:08:34.420 Debug: default set to 0
02/14/19 14:08:34.420 Debug: deviceType set to hmlgw
02/14/19 14:08:34.420 Debug: host set to 192.168.0.19
02/14/19 14:08:34.420 Debug: port set to 2000
02/14/19 14:08:34.420 Debug: portKeepAlive set to 2001
02/14/19 14:08:34.420 Debug: responseDelay set to 60
02/14/19 14:08:34.420 Debug: Loading section "HM-CFG-LAN"
02/14/19 14:08:34.420 Debug: id set to HM-CFG-LAN-UG
02/14/19 14:08:34.420 Debug: default set to 0
02/14/19 14:08:34.421 Debug: deviceType set to hmcfglan
02/14/19 14:08:34.421 Debug: host set to 192.168.0.2
02/14/19 14:08:34.421 Debug: port set to 1000
02/14/19 14:08:34.421 Debug: lanKey set to 1E37117074A4337BB36B087C94AB1184
02/14/19 14:08:34.421 Debug: responseDelay set to 60
02/14/19 14:08:34.421 Debug: Loading section "HM-CFG-LAN"
02/14/19 14:08:34.421 Debug: id set to HM-CFG-LAN-EG
02/14/19 14:08:34.421 Debug: default set to 1
02/14/19 14:08:34.421 Debug: deviceType set to hmcfglan
02/14/19 14:08:34.421 Debug: host set to 192.168.0.3
02/14/19 14:08:34.421 Debug: port set to 1000
02/14/19 14:08:34.421 Debug: lanKey set to AE06C723E7E11EC99BBABA541D14722B
02/14/19 14:08:34.421 Debug: responseDelay set to 60
02/14/19 14:08:34.421 Debug: Loading section "HM-CFG-LAN"
02/14/19 14:08:34.421 Debug: id set to HM-CFG-LAN-OG
02/14/19 14:08:34.421 Debug: default set to 0
02/14/19 14:08:34.421 Debug: deviceType set to hmcfglan
02/14/19 14:08:34.421 Debug: host set to 192.168.0.4
02/14/19 14:08:34.421 Debug: port set to 1000
02/14/19 14:08:34.421 Debug: lanKey set to EE23EC801981CC5E3FCEF548F4145B8B
02/14/19 14:08:34.421 Debug: responseDelay set to 60
02/14/19 14:08:34.421 Module HomeMatic BidCoS: Debug: Loading module...
02/14/19 14:08:34.421 Module HomeMatic BidCoS: Debug: Creating physical device. Type defined in homematicbidcos.conf is: hmcfglan
02/14/19 14:08:34.421 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-EG": Info: Enabling AES encryption for communication with HM-CFG-LAN.
02/14/19 14:08:34.421 Module HomeMatic BidCoS: Debug: Creating physical device. Type defined in homematicbidcos.conf is: hmcfglan
02/14/19 14:08:34.421 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-OG": Info: Enabling AES encryption for communication with HM-CFG-LAN.
02/14/19 14:08:34.421 Module HomeMatic BidCoS: Debug: Creating physical device. Type defined in homematicbidcos.conf is: hmcfglan
02/14/19 14:08:34.421 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-UG": Info: Enabling AES encryption for communication with HM-CFG-LAN.
02/14/19 14:08:34.421 Module HomeMatic BidCoS: Debug: Creating physical device. Type defined in homematicbidcos.conf is: hmlgw
02/14/19 14:08:34.421 HM-LGW "HM-LGW": Info: No security key specified in homematicbidcos.conf.
02/14/19 14:08:34.421 Info: Loading family module (type 1) mod_miscellaneous.so
02/14/19 14:08:34.423 Info: Loading settings from /etc/homegear/families/miscellaneous.conf
02/14/19 14:08:34.423 Module Miscellaneous: Debug: Loading module...
02/14/19 14:08:34.423 Info: Loading family module (type 1) mod_insteon.so
02/14/19 14:08:34.426 Info: Loading settings from /etc/homegear/families/insteon.conf
02/14/19 14:08:34.426 Debug: Loading section "General"
02/14/19 14:08:34.426 Debug: Family setting moduleenabled set to false
02/14/19 14:08:34.426 Module Insteon: Debug: Loading module...
02/14/19 14:08:34.426 Info: Loading family module (type 1) mod_beckhoff.so
02/14/19 14:08:34.452 Info: Loading settings from /etc/homegear/families/beckhoff.conf
02/14/19 14:08:34.452 Debug: Loading section "General"
02/14/19 14:08:34.452 Debug: Family setting moduleenabled set to false
02/14/19 14:08:34.452 Module Beckhoff: Debug: Loading module...
02/14/19 14:08:34.452 Info: Loading family module (type 1) mod_homematicwired.so
02/14/19 14:08:34.455 Info: Loading settings from /etc/homegear/families/homematicwired.conf
02/14/19 14:08:34.455 Debug: Loading section "General"
02/14/19 14:08:34.455 Debug: Family setting moduleenabled set to false
02/14/19 14:08:34.455 Module HomeMatic Wired: Debug: Loading module...
02/14/19 14:08:34.455 Info: Loading family module (type 1) mod_rs2w.so
02/14/19 14:08:34.457 Info: Loading settings from /etc/homegear/families/rs2w.conf
02/14/19 14:08:34.457 Module RS2W: Debug: Loading module...
02/14/19 14:08:34.457 Warning: Running as root. The authors of Homegear recommend running Homegear as user.
02/14/19 14:08:34.480 Starting script engine server...
02/14/19 14:08:34.481 Script Engine Server: Debug: Waiting for script engine server's client threads to finish.
02/14/19 14:08:34.485 Initializing licensing controller...
02/14/19 14:08:34.583 Loading licensing controller data...
02/14/19 14:08:34.583 Loading devices...
02/14/19 14:08:34.583 Loading XML RPC devices...
02/14/19 14:08:34.584 Loading XML RPC device /etc/homegear/devices/0/rf_s_4_ba.xml
02/14/19 14:08:34.586 Loading XML RPC device /etc/homegear/devices/0/rf_ao.xml
02/14/19 14:08:34.612 Loading XML RPC device /etc/homegear/devices/0/rf_sen_db.xml
02/14/19 14:08:34.614 Loading XML RPC device /etc/homegear/devices/0/rf_pb-2-wm55_le_v1_3.xml
02/14/19 14:08:34.614 Loading XML RPC device /etc/homegear/devices/0/rf_dis_ep_wm55_le_v1_0.xml
02/14/19 14:08:34.615 Loading XML RPC device /etc/homegear/devices/0/rf_s_mega168.xml
02/14/19 14:08:34.616 Loading XML RPC device /etc/homegear/devices/0/rf_rc-4-3_single_on.xml
02/14/19 14:08:34.617 Loading XML RPC device /etc/homegear/devices/0/rf_sec_sir_wm.xml
02/14/19 14:08:34.621 Loading XML RPC device /etc/homegear/devices/0/rf_sec_sfa.xml
02/14/19 14:08:34.623 Loading XML RPC device /etc/homegear/devices/0/rf_cm.xml
02/14/19 14:08:34.625 Loading XML RPC device /etc/homegear/devices/0/rf_s550ia.xml
02/14/19 14:08:34.626 Loading XML RPC device /etc/homegear/devices/0/rf_tc_it_wm-w-eu.xml
02/14/19 14:08:34.635 Loading XML RPC device /etc/homegear/devices/0/rf_hm-wds100-c6-o-2.xml
02/14/19 14:08:34.636 Loading XML RPC device /etc/homegear/devices/0/rf_pbi.xml
02/14/19 14:08:34.636 Loading XML RPC device /etc/homegear/devices/0/rf_dim_1t_dr.xml
02/14/19 14:08:34.641 Loading XML RPC device /etc/homegear/devices/0/rf_s.xml
02/14/19 14:08:34.643 Loading XML RPC device /etc/homegear/devices/0/rf_dim_2l_644_le_v2_4.xml
02/14/19 14:08:34.648 Loading XML RPC device /etc/homegear/devices/0/rf_s_ba.xml
02/14/19 14:08:34.649 Loading XML RPC device /etc/homegear/devices/0/rf_cf.xml
02/14/19 14:08:34.652 Loading XML RPC device /etc/homegear/devices/0/rf_scd_v1_0.xml
02/14/19 14:08:34.652 Loading XML RPC device /etc/homegear/devices/0/rf_sen_mdir_v1_5.xml
02/14/19 14:08:34.653 Loading XML RPC device /etc/homegear/devices/0/rf_rc_12.xml
02/14/19 14:08:34.653 Loading XML RPC device /etc/homegear/devices/0/rf_wds30_ot2.xml
02/14/19 14:08:34.653 Loading XML RPC device /etc/homegear/devices/0/rf_rd_le_v1_3.xml
02/14/19 14:08:34.654 Loading XML RPC device /etc/homegear/devices/0/rf_winmatic.xml
02/14/19 14:08:34.655 Loading XML RPC device /etc/homegear/devices/0/rf_es_tx_wm.xml
02/14/19 14:08:34.656 Loading XML RPC device /etc/homegear/devices/0/rf_sen_ep.xml
02/14/19 14:08:34.656 Loading XML RPC device /etc/homegear/devices/0/rf_dis_ep_wm55.xml
02/14/19 14:08:34.657 Loading XML RPC device /etc/homegear/devices/0/rf_rc_dis.xml
02/14/19 14:08:34.657 Loading XML RPC device /etc/homegear/devices/0/rf_rc_single_on.xml
02/14/19 14:08:34.658 Loading XML RPC device /etc/homegear/devices/0/rf_em_8.xml
02/14/19 14:08:34.659 Loading XML RPC device /etc/homegear/devices/0/rf_wds_v1_0.xml
02/14/19 14:08:34.659 Loading XML RPC device /etc/homegear/devices/0/rf_ddc.xml
02/14/19 14:08:34.660 Loading XML RPC device /etc/homegear/devices/0/rf_rhs_le_v1_6.xml
02/14/19 14:08:34.661 Loading XML RPC device /etc/homegear/devices/0/rf_dim_1pwm_644.xml
02/14/19 14:08:34.667 Loading XML RPC device /etc/homegear/devices/0/rf_sc_le_v1_6.xml
02/14/19 14:08:34.667 Loading XML RPC device /etc/homegear/devices/0/rf_dim_t.xml
02/14/19 14:08:34.669 Loading XML RPC device /etc/homegear/devices/0/rf_bl_644.xml
02/14/19 14:08:34.672 Loading XML RPC device /etc/homegear/devices/0/rf_keymatic.xml
02/14/19 14:08:34.673 Loading XML RPC device /etc/homegear/devices/0/rf_sec_sco.xml
02/14/19 14:08:34.673 Loading XML RPC device /etc/homegear/devices/0/rf_rgbw.xml
02/14/19 14:08:34.676 Loading XML RPC device /etc/homegear/devices/0/rf_rc-4-2.xml
02/14/19 14:08:34.676 Loading XML RPC device /etc/homegear/devices/0/rf_ks550.xml
02/14/19 14:08:34.677 Loading XML RPC device /etc/homegear/devices/0/rf_cfm.xml
02/14/19 14:08:34.680 Loading XML RPC device /etc/homegear/devices/0/rf_sec_sd_schueco.xml
02/14/19 14:08:34.680 Loading XML RPC device /etc/homegear/devices/0/rf_cc_vd.xml
02/14/19 14:08:34.680 Loading XML RPC device /etc/homegear/devices/0/rf_rc-sec4-2.xml
02/14/19 14:08:34.681 Loading XML RPC device /etc/homegear/devices/0/rf_s_1conf_644_le_v2_3.xml
02/14/19 14:08:34.682 Loading XML RPC device /etc/homegear/devices/0/rf_dim_1pwm_644_le_v2_4.xml
02/14/19 14:08:34.688 Loading XML RPC device /etc/homegear/devices/0/rf_st_6_sh.xml
02/14/19 14:08:34.689 Loading XML RPC device /etc/homegear/devices/0/rf_rep.xml
02/14/19 14:08:34.691 Loading XML RPC device /etc/homegear/devices/0/rf_sec_mdir_v1_5.xml
02/14/19 14:08:34.692 Loading XML RPC device /etc/homegear/devices/0/rf_s_1conf_644_le_v2_1.xml
02/14/19 14:08:34.693 Loading XML RPC device /etc/homegear/devices/0/rf_bl_conf_644_e_v2_1.xml
02/14/19 14:08:34.696 Loading XML RPC device /etc/homegear/devices/0/rf_ou_led16_le_v1_0.xml
02/14/19 14:08:34.696 Loading XML RPC device /etc/homegear/devices/0/rf_rhs.xml
02/14/19 14:08:34.697 Loading XML RPC device /etc/homegear/devices/0/rf_s_2conf_644.xml
02/14/19 14:08:34.698 Loading XML RPC device /etc/homegear/devices/0/rf_dw.xml
02/14/19 14:08:34.723 Loading XML RPC device /etc/homegear/devices/0/rf_sc.xml
02/14/19 14:08:34.723 Loading XML RPC device /etc/homegear/devices/0/rf_dim_1l_644.xml
02/14/19 14:08:34.728 Loading XML RPC device /etc/homegear/devices/0/rf_sec_mdir.xml
02/14/19 14:08:34.729 Loading XML RPC device /etc/homegear/devices/0/rf_dim_1l_644_le_v2_4.xml
02/14/19 14:08:34.734 Loading XML RPC device /etc/homegear/devices/0/rf_s_8_ba.xml
02/14/19 14:08:34.735 Loading XML RPC device /etc/homegear/devices/0/rf_dim_1t_fm_lf.xml
02/14/19 14:08:34.738 Loading XML RPC device /etc/homegear/devices/0/rf_rc-key4-2.xml
02/14/19 14:08:34.739 Loading XML RPC device /etc/homegear/devices/0/rf_sci_3.xml
02/14/19 14:08:34.739 Loading XML RPC device /etc/homegear/devices/0/rf_tis_le_v1_0.xml
02/14/19 14:08:34.740 Loading XML RPC device /etc/homegear/devices/0/rf_rc.xml
02/14/19 14:08:34.740 Loading XML RPC device /etc/homegear/devices/0/rf_resc_win_pcb_sc.xml
02/14/19 14:08:34.742 Loading XML RPC device /etc/homegear/devices/0/rf_em_8_bit.xml
02/14/19 14:08:34.742 Loading XML RPC device /etc/homegear/devices/0/rf_sen_mdir.xml
02/14/19 14:08:34.743 Loading XML RPC device /etc/homegear/devices/0/rf_dis_wm55.xml
02/14/19 14:08:34.743 Loading XML RPC device /etc/homegear/devices/0/rf_cc_rt_dn.xml
02/14/19 14:08:34.747 Loading XML RPC device /etc/homegear/devices/0/rf_bl_conf_644.xml
02/14/19 14:08:34.750 Loading XML RPC device /etc/homegear/devices/0/rf_fs_ba.xml
02/14/19 14:08:34.751 Loading XML RPC device /etc/homegear/devices/0/rf_rc_2_fm.xml
02/14/19 14:08:34.752 Loading XML RPC device /etc/homegear/devices/0/rf_dim_2t_644_le_v2_4.xml
02/14/19 14:08:34.758 Loading XML RPC device /etc/homegear/devices/0/rf_sen_wa_od.xml
02/14/19 14:08:34.758 Loading XML RPC device /etc/homegear/devices/0/rf_sc_e_v1_7.xml
02/14/19 14:08:34.759 Loading XML RPC device /etc/homegear/devices/0/rf_bl_le_v2_3.xml
02/14/19 14:08:34.761 Loading XML RPC device /etc/homegear/devices/0/rf_dim_1tconf_644_le_v2_4.xml
02/14/19 14:08:34.767 Loading XML RPC device /etc/homegear/devices/0/rf_s_1conf_644.xml
02/14/19 14:08:34.768 Loading XML RPC device /etc/homegear/devices/0/rf_cc_tc_le_v1_9.xml
02/14/19 14:08:34.773 Loading XML RPC device /etc/homegear/devices/0/rf_bl_conf_644_e_v2_0.xml
02/14/19 14:08:34.776 Loading XML RPC device /etc/homegear/devices/0/rf_dim_1tconf_644.xml
02/14/19 14:08:34.781 Loading XML RPC device /etc/homegear/devices/0/rf_sec_sd_2.xml
02/14/19 14:08:34.782 Loading XML RPC device /etc/homegear/devices/0/rf_dim_1t_644.xml
02/14/19 14:08:34.788 Loading XML RPC device /etc/homegear/devices/0/rf_s_644.xml
02/14/19 14:08:34.789 Loading XML RPC device /etc/homegear/devices/0/rf_pb-2.xml
02/14/19 14:08:34.789 Loading XML RPC device /etc/homegear/devices/0/rf_wds40_th_i_2.xml
02/14/19 14:08:34.790 Loading XML RPC device /etc/homegear/devices/0/rf_dim_2l_644.xml
02/14/19 14:08:34.795 Loading XML RPC device /etc/homegear/devices/0/rf_wds_v1_1.xml
02/14/19 14:08:34.796 Loading XML RPC device /etc/homegear/devices/0/rf_es_tx_wm_le_v1_0.xml
02/14/19 14:08:34.796 Loading XML RPC device /etc/homegear/devices/0/rf_d_le_v1_7.xml
02/14/19 14:08:34.798 Loading XML RPC device /etc/homegear/devices/0/rf_es_pmsw.xml
02/14/19 14:08:34.801 Loading XML RPC device /etc/homegear/devices/0/rf_cc_tc.xml
02/14/19 14:08:34.806 Loading XML RPC device /etc/homegear/devices/0/rf_tis.xml
02/14/19 14:08:34.807 Loading XML RPC device /etc/homegear/devices/0/rf_4dis.xml
02/14/19 14:08:34.807 Loading XML RPC device /etc/homegear/devices/0/rf_swi.xml
02/14/19 14:08:34.807 Loading XML RPC device /etc/homegear/devices/0/rf_pb-2-wm55_ge_v1_4.xml
02/14/19 14:08:34.808 Loading XML RPC device /etc/homegear/devices/0/rf_s_le_v2_3.xml
02/14/19 14:08:34.809 Loading XML RPC device /etc/homegear/devices/0/rf_ja_conf_644.xml
02/14/19 14:08:34.812 Loading XML RPC device /etc/homegear/devices/0/rf_dim_2pwm.xml
02/14/19 14:08:34.828 Loading XML RPC device /etc/homegear/devices/0/rf_rc_19.xml
02/14/19 14:08:34.829 Loading XML RPC device /etc/homegear/devices/0/rf_rhs_e_v1_7.xml
02/14/19 14:08:34.830 Loading XML RPC device /etc/homegear/devices/0/rf_ws550.xml
02/14/19 14:08:34.830 Loading XML RPC device /etc/homegear/devices/0/rf_cfm_tw.xml
02/14/19 14:08:34.833 Loading XML RPC device /etc/homegear/devices/0/rf_rd.xml
02/14/19 14:08:34.833 Loading XML RPC device /etc/homegear/devices/0/rf_s_le_v1_5.xml
02/14/19 14:08:34.834 Loading XML RPC device /etc/homegear/devices/0/rf_bl.xml
02/14/19 14:08:34.837 Loading XML RPC device /etc/homegear/devices/0/rf_dim_2t_644.xml
02/14/19 14:08:34.842 Loading XML RPC device /etc/homegear/devices/0/rf_sec_sd.xml
02/14/19 14:08:34.842 Loading XML RPC device /etc/homegear/devices/0/rf_roto_wdf_solar.xml
02/14/19 14:08:34.846 Loading XML RPC device /etc/homegear/devices/0/rf_d.xml
02/14/19 14:08:34.848 Loading XML RPC device /etc/homegear/devices/0/rf_ash550.xml
02/14/19 14:08:34.848 Loading XML RPC device /etc/homegear/devices/0/rf_dim_t_le_v1_9.xml
02/14/19 14:08:34.851 Loading XML RPC device /etc/homegear/devices/0/rf_d_le_v1_9.xml
02/14/19 14:08:34.853 Loading XML RPC device /etc/homegear/devices/0/rf_sen_li.xml
02/14/19 14:08:34.853 Loading XML RPC device /etc/homegear/devices/0/rf_es_pmsw_le_v2_4.xml
02/14/19 14:08:34.856 Loading XML RPC device /etc/homegear/devices/0/rf_oligo_smart_iq.xml
02/14/19 14:08:34.872 Loading XML RPC device /etc/homegear/devices/0/rf_ou_led16_ge_v1_1.xml
02/14/19 14:08:34.873 Loading XML RPC device /etc/homegear/devices/0/rf_dim_1t_644_le_v2_4.xml
02/14/19 14:08:34.878 Loading XML RPC device /etc/homegear/devices/0/rf_sen_mdir_wm55.xml
02/14/19 14:08:34.879 Loading XML RPC device /etc/homegear/devices/0/rf_cc_rt_dn_bom.xml
02/14/19 14:08:34.882 Loading device 5
02/14/19 14:08:34.883 Module HomeMatic BidCoS: Info: Central address set to 0xFD1309.
02/14/19 14:08:34.883 Module HomeMatic BidCoS: Loading peer 1
02/14/19 14:08:34.887 Debug: Could not set parameter LOWBAT on channel 0 for peer 1. Parameter does not exist.
02/14/19 14:08:34.887 Module HomeMatic BidCoS: Loading peer 2
02/14/19 14:08:34.890 Module HomeMatic BidCoS: Loading peer 3
02/14/19 14:08:34.893 Debug: Could not set parameter LOWBAT on channel 0 for peer 3. Parameter does not exist.
02/14/19 14:08:34.894 Module HomeMatic BidCoS: Loading peer 4
02/14/19 14:08:34.897 Debug: Could not set parameter LOWBAT on channel 0 for peer 4. Parameter does not exist.
02/14/19 14:08:34.897 Module HomeMatic BidCoS: Loading peer 5
02/14/19 14:08:34.901 Debug: Could not set parameter LOWBAT on channel 0 for peer 5. Parameter does not exist.
02/14/19 14:08:34.901 Module HomeMatic BidCoS: Loading peer 6
02/14/19 14:08:34.905 Debug: Could not set parameter LOWBAT on channel 0 for peer 6. Parameter does not exist.
02/14/19 14:08:34.905 Module HomeMatic BidCoS: Loading peer 7
02/14/19 14:08:34.909 Debug: Could not set parameter LOWBAT on channel 0 for peer 7. Parameter does not exist.
02/14/19 14:08:34.909 Module HomeMatic BidCoS: Loading peer 8
02/14/19 14:08:34.915 Debug: Could not set parameter LOWBAT on channel 0 for peer 8. Parameter does not exist.
02/14/19 14:08:34.915 Module HomeMatic BidCoS: Loading peer 11
02/14/19 14:08:34.917 Module HomeMatic BidCoS: Loading peer 20
02/14/19 14:08:34.919 Module HomeMatic BidCoS: Loading peer 21
02/14/19 14:08:34.921 Module HomeMatic BidCoS: Loading peer 22
02/14/19 14:08:34.926 Module HomeMatic BidCoS: Loading peer 23
02/14/19 14:08:34.932 Module HomeMatic BidCoS: Loading peer 24
02/14/19 14:08:34.934 Module HomeMatic BidCoS: Loading peer 25
02/14/19 14:08:34.937 Module HomeMatic BidCoS: Loading peer 26
02/14/19 14:08:34.942 Module HomeMatic BidCoS: Loading peer 27
02/14/19 14:08:34.944 Module HomeMatic BidCoS: Loading peer 28
02/14/19 14:08:34.946 Module HomeMatic BidCoS: Loading peer 29
02/14/19 14:08:34.948 Module HomeMatic BidCoS: Loading peer 30
02/14/19 14:08:34.954 Module HomeMatic BidCoS: Loading peer 31
02/14/19 14:08:34.960 Module HomeMatic BidCoS: Loading peer 33
02/14/19 14:08:34.966 Module HomeMatic BidCoS: Loading peer 34
02/14/19 14:08:34.972 Module HomeMatic BidCoS: Loading peer 37
02/14/19 14:08:34.978 Module HomeMatic BidCoS: Loading peer 39
02/14/19 14:08:34.983 Module HomeMatic BidCoS: Loading peer 41
02/14/19 14:08:34.989 Module HomeMatic BidCoS: Loading peer 43
02/14/19 14:08:34.991 Module HomeMatic BidCoS: Loading peer 44
02/14/19 14:08:34.993 Module HomeMatic BidCoS: Loading peer 45
02/14/19 14:08:34.995 Module HomeMatic BidCoS: Loading peer 46
02/14/19 14:08:34.997 Module HomeMatic BidCoS: Loading peer 47
02/14/19 14:08:34.999 Module HomeMatic BidCoS: Loading peer 51
02/14/19 14:08:35.013 Module HomeMatic BidCoS: Loading peer 52
02/14/19 14:08:35.015 Module HomeMatic BidCoS: Loading peer 53
02/14/19 14:08:35.027 Module HomeMatic BidCoS: Loading peer 54
02/14/19 14:08:35.029 Module HomeMatic BidCoS: Loading peer 56
02/14/19 14:08:35.041 Module HomeMatic BidCoS: Loading peer 57
02/14/19 14:08:35.043 Module HomeMatic BidCoS: Loading peer 58
02/14/19 14:08:35.045 Module HomeMatic BidCoS: Loading peer 59
02/14/19 14:08:35.047 Module HomeMatic BidCoS: Loading peer 60
02/14/19 14:08:35.053 Module HomeMatic BidCoS: Loading peer 61
02/14/19 14:08:35.065 Module HomeMatic BidCoS: Loading peer 62
02/14/19 14:08:35.067 Module HomeMatic BidCoS: Loading peer 63
02/14/19 14:08:35.070 Module HomeMatic BidCoS: Loading peer 65
02/14/19 14:08:35.072 Module HomeMatic BidCoS: Loading peer 66
02/14/19 14:08:35.077 Module HomeMatic BidCoS: Loading peer 67
02/14/19 14:08:35.080 Module HomeMatic BidCoS: Loading peer 68
02/14/19 14:08:35.082 Module HomeMatic BidCoS: Loading peer 69
02/14/19 14:08:35.084 Module HomeMatic BidCoS: Loading peer 72
02/14/19 14:08:35.086 Info: Not initializing device family HomeMatic Wired, because it is disabled in it's configuration file.
02/14/19 14:08:35.087 Debug: Disposing central...
02/14/19 14:08:35.087 Info: Disposing family module mod_homematicwired.so
02/14/19 14:08:35.087 Debug: Deleting factory pointer of module mod_homematicwired.so
02/14/19 14:08:35.087 Debug: Closing dynamic library module mod_homematicwired.so
02/14/19 14:08:35.087 Debug: Dynamic library mod_homematicwired.so disposed
02/14/19 14:08:35.087 Info: Not initializing device family Insteon, because it is disabled in it's configuration file.
02/14/19 14:08:35.087 Debug: Disposing central...
02/14/19 14:08:35.087 Info: Disposing family module mod_insteon.so
02/14/19 14:08:35.087 Debug: Deleting factory pointer of module mod_insteon.so
02/14/19 14:08:35.087 Debug: Closing dynamic library module mod_insteon.so
02/14/19 14:08:35.087 Debug: Dynamic library mod_insteon.so disposed
02/14/19 14:08:35.087 Info: Not initializing device family MAX!, because it is disabled in it's configuration file.
02/14/19 14:08:35.087 Debug: Disposing central...
02/14/19 14:08:35.087 Info: Disposing family module mod_max.so
02/14/19 14:08:35.087 Debug: Deleting factory pointer of module mod_max.so
02/14/19 14:08:35.087 Debug: Closing dynamic library module mod_max.so
02/14/19 14:08:35.088 Debug: Dynamic library mod_max.so disposed
02/14/19 14:08:35.088 Info: Not initializing device family Philips hue, because it is disabled in it's configuration file.
02/14/19 14:08:35.088 Debug: Disposing central...
02/14/19 14:08:35.088 Info: Disposing family module mod_philipshue.so
02/14/19 14:08:35.088 Debug: Deleting factory pointer of module mod_philipshue.so
02/14/19 14:08:35.088 Debug: Closing dynamic library module mod_philipshue.so
02/14/19 14:08:35.088 Debug: Dynamic library mod_philipshue.so disposed
02/14/19 14:08:35.088 Info: Not initializing device family Sonos, because it is disabled in it's configuration file.
02/14/19 14:08:35.088 Debug: Disposing central...
02/14/19 14:08:35.088 Info: Disposing family module mod_sonos.so
02/14/19 14:08:35.088 Debug: Deleting factory pointer of module mod_sonos.so
02/14/19 14:08:35.088 Debug: Closing dynamic library module mod_sonos.so
02/14/19 14:08:35.088 Debug: Dynamic library mod_sonos.so disposed
02/14/19 14:08:35.088 Info: Not initializing device family EASYCam, because it is disabled in it's configuration file.
02/14/19 14:08:35.088 Debug: Disposing central...
02/14/19 14:08:35.088 Info: Disposing family module mod_easycam.so
02/14/19 14:08:35.088 Debug: Deleting factory pointer of module mod_easycam.so
02/14/19 14:08:35.088 Debug: Closing dynamic library module mod_easycam.so
02/14/19 14:08:35.088 Debug: Dynamic library mod_easycam.so disposed
02/14/19 14:08:35.088 Info: Not initializing device family EASYLed, because it is disabled in it's configuration file.
02/14/19 14:08:35.088 Debug: Disposing central...
02/14/19 14:08:35.088 Info: Disposing family module mod_easyled.so
02/14/19 14:08:35.088 Debug: Deleting factory pointer of module mod_easyled.so
02/14/19 14:08:35.088 Debug: Closing dynamic library module mod_easyled.so
02/14/19 14:08:35.088 Debug: Dynamic library mod_easyled.so disposed
02/14/19 14:08:35.088 Info: Not initializing device family Kodi, because it is disabled in it's configuration file.
02/14/19 14:08:35.088 Debug: Disposing central...
02/14/19 14:08:35.088 Info: Disposing family module mod_kodi.so
02/14/19 14:08:35.088 Debug: Deleting factory pointer of module mod_kodi.so
02/14/19 14:08:35.088 Debug: Closing dynamic library module mod_kodi.so
02/14/19 14:08:35.088 Debug: Dynamic library mod_kodi.so disposed
02/14/19 14:08:35.088 Info: Not initializing device family IPCam, because it is disabled in it's configuration file.
02/14/19 14:08:35.088 Debug: Disposing central...
02/14/19 14:08:35.089 Info: Disposing family module mod_ipcam.so
02/14/19 14:08:35.089 Debug: Deleting factory pointer of module mod_ipcam.so
02/14/19 14:08:35.089 Debug: Closing dynamic library module mod_ipcam.so
02/14/19 14:08:35.089 Debug: Dynamic library mod_ipcam.so disposed
02/14/19 14:08:35.089 Info: Not initializing device family Beckhoff, because it is disabled in it's configuration file.
02/14/19 14:08:35.089 Debug: Disposing central...
02/14/19 14:08:35.089 Info: Disposing family module mod_beckhoff.so
02/14/19 14:08:35.089 Debug: Deleting factory pointer of module mod_beckhoff.so
02/14/19 14:08:35.089 Debug: Closing dynamic library module mod_beckhoff.so
02/14/19 14:08:35.089 Debug: Dynamic library mod_beckhoff.so disposed
02/14/19 14:08:35.089 Info: Not initializing device family KNX, because it is disabled in it's configuration file.
02/14/19 14:08:35.089 Debug: Disposing central...
02/14/19 14:08:35.089 Info: Disposing family module mod_knx.so
02/14/19 14:08:35.089 Debug: Deleting factory pointer of module mod_knx.so
02/14/19 14:08:35.089 Debug: Closing dynamic library module mod_knx.so
02/14/19 14:08:35.089 Debug: Dynamic library mod_knx.so disposed
02/14/19 14:08:35.089 Info: Not initializing device family EnOcean, because it is disabled in it's configuration file.
02/14/19 14:08:35.089 Debug: Disposing central...
02/14/19 14:08:35.089 Info: Disposing family module mod_enocean.so
02/14/19 14:08:35.089 Debug: Deleting factory pointer of module mod_enocean.so
02/14/19 14:08:35.089 Debug: Closing dynamic library module mod_enocean.so
02/14/19 14:08:35.089 Debug: Dynamic library mod_enocean.so disposed
02/14/19 14:08:35.089 Info: Not initializing device family Intertechno, because it is disabled in it's configuration file.
02/14/19 14:08:35.089 Debug: Disposing central...
02/14/19 14:08:35.089 Info: Disposing family module mod_intertechno.so
02/14/19 14:08:35.089 Debug: Deleting factory pointer of module mod_intertechno.so
02/14/19 14:08:35.089 Debug: Closing dynamic library module mod_intertechno.so
02/14/19 14:08:35.089 Debug: Dynamic library mod_intertechno.so disposed
02/14/19 14:08:35.089 Loading XML RPC devices...
02/14/19 14:08:35.090 Loading XML RPC device /etc/homegear/devices/17/0154-0100-0101.xml
02/14/19 14:08:35.091 Loading XML RPC device /etc/homegear/devices/17/zwave.xml
02/14/19 14:08:35.091 Loading XML RPC device /etc/homegear/devices/17/010f-0801-1001.xml
02/14/19 14:08:35.092 Loading device 17
02/14/19 14:08:35.093 Info: Not initializing device family EASYLed 2, because it is disabled in it's configuration file.
02/14/19 14:08:35.093 Debug: Disposing central...
02/14/19 14:08:35.093 Info: Disposing family module mod_easyled2.so
02/14/19 14:08:35.093 Debug: Deleting factory pointer of module mod_easyled2.so
02/14/19 14:08:35.093 Debug: Closing dynamic library module mod_easyled2.so
02/14/19 14:08:35.093 Debug: Dynamic library mod_easyled2.so disposed
02/14/19 14:08:35.093 Loading XML RPC devices...
02/14/19 14:08:35.093 Loading XML RPC device /etc/homegear/devices/19/Socket.xml
02/14/19 14:08:35.093 Loading XML RPC device /etc/homegear/devices/19/Plug.xml
02/14/19 14:08:35.094 Loading device 14
02/14/19 14:08:35.094 Loading XML RPC devices...
02/14/19 14:08:35.094 Loading XML RPC device /etc/homegear/devices/20/Device.xml
02/14/19 14:08:35.094 Loading device 15
02/14/19 14:08:35.094 Info: Not initializing device family M-Bus, because it is disabled in it's configuration file.
02/14/19 14:08:35.094 Debug: Disposing central...
02/14/19 14:08:35.094 Info: Disposing family module mod_mbus.so
02/14/19 14:08:35.094 Debug: Deleting factory pointer of module mod_mbus.so
02/14/19 14:08:35.094 Debug: Closing dynamic library module mod_mbus.so
02/14/19 14:08:35.094 Debug: Dynamic library mod_mbus.so disposed
02/14/19 14:08:35.094 Info: Not initializing device family CCU, because it is disabled in it's configuration file.
02/14/19 14:08:35.094 Debug: Disposing central...
02/14/19 14:08:35.094 Info: Disposing family module mod_ccu.so
02/14/19 14:08:35.094 Debug: Deleting factory pointer of module mod_ccu.so
02/14/19 14:08:35.094 Debug: Closing dynamic library module mod_ccu.so
02/14/19 14:08:35.095 Debug: Dynamic library mod_ccu.so disposed
02/14/19 14:08:35.095 Loading XML RPC devices...
02/14/19 14:08:35.095 Loading XML RPC device /etc/homegear/devices/254/VirtualWindowContact.xml
02/14/19 14:08:35.095 Loading XML RPC device /etc/homegear/devices/254/VirtualDimmer.xml
02/14/19 14:08:35.110 Loading XML RPC device /etc/homegear/devices/254/OpenWeatherMap.xml
02/14/19 14:08:35.110 Loading device 4
02/14/19 14:08:35.111 Initializing RPC client...
02/14/19 14:08:35.111 Starting XML RPC server FamilyRPCServer listening on ::1:2000...
02/14/19 14:08:35.112 RPC Server (Port 2000): Info: Enabling basic authentication for WebSockets.
02/14/19 14:08:35.112 Starting XML RPC server RPCServer1 listening on :::2001...
02/14/19 14:08:35.112 RPC Server (Port 2000): Info: RPC Server started listening on address ::1 and port 2000
02/14/19 14:08:35.113 RPC Server (Port 2001): Warning: SSL is not enabled for this RPC server. It is strongly recommended to disable all unencrypted RPC servers when the connected clients support it.
02/14/19 14:08:35.113 RPC Server (Port 2001): Warning: RPC server has no authorization enabled. Everybody on your local network can login into this installation. It is strongly recommended to enable authorization on all RPC servers when the connected clients support it.
02/14/19 14:08:35.113 RPC Server (Port 2001): Info: Enabling session authentication for WebSockets.
02/14/19 14:08:35.113 Starting XML RPC server RPCServer2 listening on :::2002, SSL enabled...
02/14/19 14:08:35.113 RPC Server (Port 2001): Info: RPC Server started listening on address :: and port 2001
02/14/19 14:08:35.114 RPC Server (Port 2002): Warning: RPC server has no authorization enabled. Everybody on your local network can login into this installation. It is strongly recommended to enable authorization on all RPC servers when the connected clients support it.
02/14/19 14:08:35.114 RPC Server (Port 2002): Info: Enabling session authentication for WebSockets.
02/14/19 14:08:35.175 Starting XML RPC server RPCServer3 listening on :::2003, SSL enabled, authentication enabled...
02/14/19 14:08:35.175 RPC Server (Port 2002): Info: RPC Server started listening on address :: and port 2002
02/14/19 14:08:35.176 RPC Server (Port 2003): Info: Enabling basic authentication.
02/14/19 14:08:35.176 RPC Server (Port 2003): Info: Enabling client certificate authentication.
02/14/19 14:08:35.176 RPC Server (Port 2003): Info: Enabling session authentication for WebSockets.
02/14/19 14:08:35.197 Initializing event handler...
02/14/19 14:08:35.197 RPC Server (Port 2003): Info: RPC Server started listening on address :: and port 2003
02/14/19 14:08:35.197 Loading events...
02/14/19 14:08:35.198 Start listening for packets...
02/14/19 14:08:35.198 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-EG": Debug: Connecting to HM-CFG-LAN with hostname 192.168.0.3 on port 1000...
02/14/19 14:08:35.198 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-OG": Debug: Connecting to HM-CFG-LAN with hostname 192.168.0.4 on port 1000...
02/14/19 14:08:35.198 Debug: Calling getFileDescriptor...
02/14/19 14:08:35.199 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-UG": Debug: Connecting to HM-CFG-LAN with hostname 192.168.0.2 on port 1000...
02/14/19 14:08:35.199 Debug: Calling getFileDescriptor...
02/14/19 14:08:35.199 Debug: Connecting to host 192.168.0.4 on port 1000...
02/14/19 14:08:35.199 HM-LGW "HM-LGW": Connecting to HM-LGW with hostname 192.168.0.19 on port 2000...
02/14/19 14:08:35.199 Debug: Connecting to host 192.168.0.3 on port 1000...
02/14/19 14:08:35.199 Starting Node-BLUE server...
02/14/19 14:08:35.199 Node-BLUE Server: Debug: Waiting for flows engine server's client threads to finish.
02/14/19 14:08:35.200 Debug: Calling getFileDescriptor...
02/14/19 14:08:35.200 Debug: Connecting to host 192.168.0.19 on port 2001...
02/14/19 14:08:35.200 Debug: Calling getFileDescriptor...
02/14/19 14:08:35.200 Debug: Connecting to host 192.168.0.19 on port 2000...
02/14/19 14:08:35.202 Debug: Connected to host 192.168.0.19 on port 2000. Client number is: 8
02/14/19 14:08:35.202 HM-LGW "HM-LGW": Warning: Connection to client number 8 closed (3).
02/14/19 14:08:35.203 Debug: Connected to host 192.168.0.3 on port 1000. Client number is: 5
02/14/19 14:08:35.204 Debug: Connected to host 192.168.0.4 on port 1000. Client number is: 7
02/14/19 14:08:35.205 Debug: Connected to host 192.168.0.19 on port 2001. Client number is: 9
02/14/19 14:08:35.206 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-EG": HM-CFG-LAN IV is: 3C1E0F070984C2610A05824120100804
02/14/19 14:08:35.206 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-EG": Homegear IV is: CA38B2AD1382195E5F4CA4E5330A5EE9
02/14/19 14:08:35.206 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-EG": Debug: Sending: VCA38B2AD1382195E5F4CA4E5330A5EE9
02/14/19 14:08:35.206 HM-LGW "HM-LGW": Debug: Packet received on port 2001: H4d,01,Revilo-HM-LGW,0.0.2,CCU2GW0001
02/14/19 14:08:35.206 HM-LGW "HM-LGW": Info: Keep alive init packet received: H4d,01,Revilo-HM-LGW,0.0.2,CCU2GW0001
02/14/19 14:08:35.206 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-OG": HM-CFG-LAN IV is: 9249A4520984C2610201804020100804
02/14/19 14:08:35.206 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-OG": Homegear IV is: F813600108B8FFBEE356774F7957D842
02/14/19 14:08:35.206 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-OG": Debug: Sending: VF813600108B8FFBEE356774F7957D842
02/14/19 14:08:35.213 Debug: Calling getFileDescriptor...
02/14/19 14:08:35.213 Debug: Connecting to host 192.168.0.2 on port 1000...
02/14/19 14:08:35.213 Starting IPC server...
02/14/19 14:08:35.213 IPC Server: Debug: Waiting for IPC server's client threads to finish.
02/14/19 14:08:35.217 Startup complete. Waiting for physical interfaces to connect.
02/14/19 14:08:35.217 Info: Waiting for physical interfaces to connect (0 of 180s).
02/14/19 14:08:35.217 All physical interfaces are connected now.
02/14/19 14:08:35.218 Starting UPnP server...
02/14/19 14:08:35.218 Info: UPnP server: Binding to address: 192.168.0.10
02/14/19 14:08:35.218 UPnP Server: Info: Started listening.
02/14/19 14:08:35.232 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-EG": Debug: Sending (encrypted): AFD1309
02/14/19 14:08:35.232 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-EG": Debug: Sending (encrypted): C
Y01,01,1133009911997766DDEEAADDBBEEEEFF
02/14/19 14:08:35.233 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-OG": Debug: Sending (encrypted): AFD1309
02/14/19 14:08:35.233 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-OG": Debug: Sending (encrypted): C
Y01,01,1133009911997766DDEEAADDBBEEEEFF
02/14/19 14:08:35.360 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-OG": Debug: Sending (encrypted): Y02,00,
02/14/19 14:08:35.360 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-EG": Debug: Sending (encrypted): Y02,00,
02/14/19 14:08:35.367 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-OG": Debug: Sending (encrypted): Y03,00,
02/14/19 14:08:35.367 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-EG": Debug: Sending (encrypted): Y03,00,
02/14/19 14:08:35.381 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-EG": Debug: Sending (encrypted): T23F824D4,02,00,00000000
02/14/19 14:08:35.381 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-EG": Debug: Sending (encrypted): +234EA5,00,00,
02/14/19 14:08:35.381 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-EG": Debug: Sending (encrypted): +234EE5,00,00,
02/14/19 14:08:35.381 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-OG": Debug: Sending (encrypted): T23F824D4,02,00,00000000
02/14/19 14:08:35.381 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-EG": Debug: Sending (encrypted): +234F97,00,00,
02/14/19 14:08:35.381 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-EG": Debug: Sending (encrypted): +2351D8,00,00,
02/14/19 14:08:35.381 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-OG": Debug: Sending (encrypted): +234ED1,00,00,
02/14/19 14:08:35.381 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-OG": Debug: Sending (encrypted): +28C1D0,00,00,
02/14/19 14:08:35.381 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-OG": Debug: Sending (encrypted): +28C219,00,00,
02/14/19 14:08:35.381 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-OG": Debug: Sending (encrypted): +2904C7,00,00,
02/14/19 14:08:35.381 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-OG": Debug: Sending (encrypted): +29D7DE,00,00,
02/14/19 14:08:35.381 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-OG": Debug: Sending (encrypted): +2B8B4C,00,00,
02/14/19 14:08:35.381 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-OG": Debug: Sending (encrypted): +2EF479,00,00,
02/14/19 14:08:35.381 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-OG": Debug: Sending (encrypted): +3531DF,00,00,
02/14/19 14:08:35.381 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-OG": Debug: Sending (encrypted): +3A88CD,00,00,
02/14/19 14:08:35.381 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-OG": Debug: Sending (encrypted): +52D567,00,00,
02/14/19 14:08:35.381 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-OG": Debug: Sending (encrypted): +52DA00,00,00,
02/14/19 14:08:35.382 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-OG": Debug: Sending (encrypted): +52DB61,00,00,
02/14/19 14:08:35.382 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-OG": Debug: Sending (encrypted): +5325D9,00,00,
02/14/19 14:08:35.382 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-OG": Debug: Sending (encrypted): +55061E,00,00,
02/14/19 14:08:35.382 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-OG": Debug: Sending (encrypted): +55DD49,00,00,
02/14/19 14:08:35.382 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-OG": Debug: Sending (encrypted): +634284,00,00,
02/14/19 14:08:35.382 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-OG": Debug: Sending (encrypted): +6343BC,00,00,
02/14/19 14:08:35.382 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-OG": Debug: Sending (encrypted): +634564,00,00,
02/14/19 14:08:35.382 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-OG": Debug: Sending (encrypted): +6654DB,00,00,
02/14/19 14:08:35.382 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-OG": Info: Initialization completed.
02/14/19 14:08:35.382 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-EG": Debug: Sending (encrypted): +26AB30,00,00,
02/14/19 14:08:35.382 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-EG": Debug: Sending (encrypted): +28C08F,00,00,
02/14/19 14:08:35.382 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-EG": Debug: Sending (encrypted): +28C09E,00,00,
02/14/19 14:08:35.382 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-EG": Debug: Sending (encrypted): +28C15D,00,00,
02/14/19 14:08:35.382 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-EG": Debug: Sending (encrypted): +28C1CC,00,00,
02/14/19 14:08:35.382 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-EG": Debug: Sending (encrypted): +28C1EF,00,00,
02/14/19 14:08:35.382 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-EG": Debug: Sending (encrypted): +28C218,00,00,
02/14/19 14:08:35.382 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-EG": Debug: Sending (encrypted): +28C21A,00,00,
02/14/19 14:08:35.382 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-EG": Debug: Sending (encrypted): +2904EC,00,00,
02/14/19 14:08:35.382 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-EG": Debug: Sending (encrypted): +29AF04,00,00,
02/14/19 14:08:35.382 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-EG": Debug: Sending (encrypted): +29AF8C,00,00,
02/14/19 14:08:35.382 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-EG": Debug: Sending (encrypted): +2D4A8F,00,00,
02/14/19 14:08:35.382 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-EG": Debug: Sending (encrypted): +3531D7,00,00,
02/14/19 14:08:35.382 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-EG": Debug: Sending (encrypted): +4DC304,00,00,
02/14/19 14:08:35.382 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-EG": Debug: Sending (encrypted): +5086E1,00,00,
02/14/19 14:08:35.382 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-EG": Debug: Sending (encrypted): +52DA15,00,00,
02/14/19 14:08:35.382 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-EG": Debug: Sending (encrypted): +52DAA5,00,00,
02/14/19 14:08:35.382 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-EG": Debug: Sending (encrypted): +54AD66,00,00,
02/14/19 14:08:35.382 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-EG": Debug: Sending (encrypted): +5505EE,00,00,
02/14/19 14:08:35.382 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-EG": Debug: Sending (encrypted): +5505F4,00,00,
02/14/19 14:08:35.382 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-EG": Debug: Sending (encrypted): +55064C,00,00,
02/14/19 14:08:35.382 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-EG": Debug: Sending (encrypted): +551837,00,00,
02/14/19 14:08:35.382 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-EG": Debug: Sending (encrypted): +5D20FC,00,00,
02/14/19 14:08:35.382 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-EG": Debug: Sending (encrypted): +5F94AF,00,00,
02/14/19 14:08:35.382 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-EG": Debug: Sending (encrypted): +602C5F,00,00,
02/14/19 14:08:35.382 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-EG": Info: Initialization completed.
02/14/19 14:08:35.569 IPC Server: Info: Connection accepted. Client number: 13
02/14/19 14:08:35.569 IPC Server: Info: Client number 0 is calling RPC method: registerRpcMethod
(String) managementGetCommandStatus
(Array length=1)
{
  (Array length=1)
  {
    (Array length=0)
    {
    }
  }
}
02/14/19 14:08:35.569 IPC Server: Info: Client 0 successfully registered RPC method "managementGetCommandStatus" (this method is registered by 1 client(s)).
02/14/19 14:08:35.569 IPC Server: Response: 
(void)
02/14/19 14:08:35.569 IPC Server: Info: Client number 0 is calling RPC method: registerRpcMethod
(String) managementSleep
(Array length=1)
{
  (Array length=2)
  {
    (String) 
    (Integer64) 0
  }
}
02/14/19 14:08:35.569 IPC Server: Info: Client 0 successfully registered RPC method "managementSleep" (this method is registered by 1 client(s)).
02/14/19 14:08:35.569 IPC Server: Response: 
(void)
02/14/19 14:08:35.570 IPC Server: Info: Client number 0 is calling RPC method: registerRpcMethod
(String) managementDpkgPackageInstalled
(Array length=1)
{
  (Array length=2)
  {
    (String) 
    (String) 
  }
}
02/14/19 14:08:35.570 IPC Server: Info: Client 0 successfully registered RPC method "managementDpkgPackageInstalled" (this method is registered by 1 client(s)).
02/14/19 14:08:35.570 IPC Server: Response: 
(void)
02/14/19 14:08:35.570 IPC Server: Info: Client number 0 is calling RPC method: registerRpcMethod
(String) managementGetConfigurationEntry
(Array length=1)
{
  (Array length=3)
  {
    (String) 
    (String) 
    (String) 
  }
}
02/14/19 14:08:35.570 IPC Server: Info: Client 0 successfully registered RPC method "managementGetConfigurationEntry" (this method is registered by 1 client(s)).
02/14/19 14:08:35.570 IPC Server: Response: 
(void)
02/14/19 14:08:35.570 IPC Server: Info: Client number 0 is calling RPC method: registerRpcMethod
(String) managementServiceCommand
(Array length=1)
{
  (Array length=3)
  {
    (String) 
    (String) 
    (String) 
  }
}
02/14/19 14:08:35.570 IPC Server: Info: Client 0 successfully registered RPC method "managementServiceCommand" (this method is registered by 1 client(s)).
02/14/19 14:08:35.570 IPC Server: Response: 
(void)
02/14/19 14:08:35.570 IPC Server: Info: Client number 0 is calling RPC method: registerRpcMethod
(String) managementReboot
(Array length=1)
{
  (Array length=1)
  {
    (String) 
  }
}
02/14/19 14:08:35.570 IPC Server: Info: Client 0 successfully registered RPC method "managementReboot" (this method is registered by 1 client(s)).
02/14/19 14:08:35.570 IPC Server: Response: 
(void)
02/14/19 14:08:35.570 IPC Server: Info: Client number 0 is calling RPC method: registerRpcMethod
(String) managementSetConfigurationEntry
(Array length=1)
{
  (Array length=4)
  {
    (String) 
    (String) 
    (String) 
    (String) 
  }
}
02/14/19 14:08:35.571 IPC Server: Info: Client 0 successfully registered RPC method "managementSetConfigurationEntry" (this method is registered by 1 client(s)).
02/14/19 14:08:35.571 IPC Server: Response: 
(void)
02/14/19 14:08:35.571 IPC Server: Info: Client number 0 is calling RPC method: registerRpcMethod
(String) managementWriteCloudMaticConfig
(Array length=1)
{
  (Array length=6)
  {
    (String) 
    (String) 
    (String) 
    (String) 
    (String) 
    (String) 
  }
}
02/14/19 14:08:35.571 IPC Server: Info: Client 0 successfully registered RPC method "managementWriteCloudMaticConfig" (this method is registered by 1 client(s)).
02/14/19 14:08:35.571 IPC Server: Response: 
(void)
02/14/19 14:08:35.571 IPC Server: Info: Client number 0 is calling RPC method: registerRpcMethod
(String) managementSetUserPassword
(Array length=1)
{
  (Array length=3)
  {
    (void)
    (String) 
    (String) 
  }
}
02/14/19 14:08:35.571 IPC Server: Info: Client 0 successfully registered RPC method "managementSetUserPassword" (this method is registered by 1 client(s)).
02/14/19 14:08:35.571 IPC Server: Response: 
(void)
02/14/19 14:08:35.571 IPC Server: Info: Client number 0 is calling RPC method: registerRpcMethod
(String) managementAptUpdate
(Array length=1)
{
  (Array length=1)
  {
    (String) 
  }
}
02/14/19 14:08:35.571 IPC Server: Info: Client 0 successfully registered RPC method "managementAptUpdate" (this method is registered by 1 client(s)).
02/14/19 14:08:35.571 IPC Server: Response: 
(void)
02/14/19 14:08:35.571 IPC Server: Info: Client number 0 is calling RPC method: registerRpcMethod
(String) managementAptUpgrade
(Array length=1)
{
  (Array length=1)
  {
    (String) 
  }
}
02/14/19 14:08:35.571 IPC Server: Info: Client 0 successfully registered RPC method "managementAptUpgrade" (this method is registered by 1 client(s)).
02/14/19 14:08:35.571 IPC Server: Response: 
(void)
02/14/19 14:08:35.572 IPC Server: Info: Client number 0 is calling RPC method: registerRpcMethod
(String) managementAptFullUpgrade
(Array length=1)
{
  (Array length=1)
  {
    (String) 
  }
}
02/14/19 14:08:35.572 IPC Server: Info: Client 0 successfully registered RPC method "managementAptFullUpgrade" (this method is registered by 1 client(s)).
02/14/19 14:08:35.572 IPC Server: Response: 
(void)
02/14/19 14:08:35.572 IPC Server: Info: Client number 0 is calling RPC method: registerRpcMethod
(String) managementHomegearUpdateAvailable
(Array length=1)
{
  (Array length=1)
  {
    (Boolean) 0
  }
}
02/14/19 14:08:35.572 IPC Server: Info: Client 0 successfully registered RPC method "managementHomegearUpdateAvailable" (this method is registered by 1 client(s)).
02/14/19 14:08:35.572 IPC Server: Response: 
(void)
02/14/19 14:08:35.572 IPC Server: Info: Client number 0 is calling RPC method: registerRpcMethod
(String) managementSystemUpdateAvailable
(Array length=1)
{
  (Array length=1)
  {
    (Boolean) 0
  }
}
02/14/19 14:08:35.572 IPC Server: Info: Client 0 successfully registered RPC method "managementSystemUpdateAvailable" (this method is registered by 1 client(s)).
02/14/19 14:08:35.572 IPC Server: Response: 
(void)
02/14/19 14:08:35.572 IPC Server: Info: Client number 0 is calling RPC method: registerRpcMethod
(String) managementCreateBackup
(Array length=1)
{
  (Array length=1)
  {
    (String) 
  }
}
02/14/19 14:08:35.572 IPC Server: Info: Client 0 successfully registered RPC method "managementCreateBackup" (this method is registered by 1 client(s)).
02/14/19 14:08:35.572 IPC Server: Response: 
(void)
02/14/19 14:08:35.572 IPC Server: Info: Client number 0 is calling RPC method: registerRpcMethod
(String) managementRestoreBackup
(Array length=1)
{
  (Array length=2)
  {
    (String) 
    (String) 
  }
}
02/14/19 14:08:35.572 IPC Server: Info: Client 0 successfully registered RPC method "managementRestoreBackup" (this method is registered by 1 client(s)).
02/14/19 14:08:35.572 IPC Server: Response: 
(void)
02/14/19 14:08:35.573 IPC Server: Info: Client number 0 is calling RPC method: registerRpcMethod
(String) managementCaExists
(Array length=1)
{
  (Array length=1)
  {
    (Boolean) 0
  }
}
02/14/19 14:08:35.573 IPC Server: Info: Client 0 successfully registered RPC method "managementCaExists" (this method is registered by 1 client(s)).
02/14/19 14:08:35.573 IPC Server: Response: 
(void)
02/14/19 14:08:35.573 IPC Server: Info: Client number 0 is calling RPC method: registerRpcMethod
(String) managementCreateCa
(Array length=1)
{
  (Array length=1)
  {
    (Boolean) 0
  }
}
02/14/19 14:08:35.573 IPC Server: Info: Client 0 successfully registered RPC method "managementCreateCa" (this method is registered by 1 client(s)).
02/14/19 14:08:35.573 IPC Server: Response: 
(void)
02/14/19 14:08:35.574 IPC Server: Info: Client number 0 is calling RPC method: registerRpcMethod
(String) managementCreateCert
(Array length=1)
{
  (Array length=2)
  {
    (Struct length=0)
    {
    }
    (String) 
  }
}
02/14/19 14:08:35.574 IPC Server: Info: Client 0 successfully registered RPC method "managementCreateCert" (this method is registered by 1 client(s)).
02/14/19 14:08:35.574 IPC Server: Response: 
(void)
02/14/19 14:08:35.574 IPC Server: Info: Client number 0 is calling RPC method: registerRpcMethod
(String) managementDeleteCert
(Array length=1)
{
  (Array length=2)
  {
    (Struct length=0)
    {
    }
    (String) 
  }
}
02/14/19 14:08:35.574 IPC Server: Info: Client 0 successfully registered RPC method "managementDeleteCert" (this method is registered by 1 client(s)).
02/14/19 14:08:35.574 IPC Server: Response: 
(void)
02/14/19 14:08:35.574 IPC Server: Info: Client number 0 is calling RPC method: registerRpcMethod
(String) managementGetNetworkConfiguration
(Array length=1)
{
  (Array length=1)
  {
    (Struct length=0)
    {
    }
  }
}
02/14/19 14:08:35.574 IPC Server: Info: Client 0 successfully registered RPC method "managementGetNetworkConfiguration" (this method is registered by 1 client(s)).
02/14/19 14:08:35.575 IPC Server: Response: 
(void)
02/14/19 14:08:35.575 IPC Server: Info: Client number 0 is calling RPC method: registerRpcMethod
(String) managementSetNetworkConfiguration
(Array length=1)
{
  (Array length=2)
  {
    (void)
    (Struct length=0)
    {
    }
  }
}
02/14/19 14:08:35.575 IPC Server: Info: Client 0 successfully registered RPC method "managementSetNetworkConfiguration" (this method is registered by 1 client(s)).
02/14/19 14:08:35.575 IPC Server: Response: 
(void)
02/14/19 14:08:35.575 IPC Server: Info: Client number 0 is calling RPC method: registerRpcMethod
(String) managementCopyDeviceDescriptionFile
(Array length=1)
{
  (Array length=3)
  {
    (Boolean) 0
    (String) 
    (Integer64) 0
  }
}
02/14/19 14:08:35.575 IPC Server: Info: Client 0 successfully registered RPC method "managementCopyDeviceDescriptionFile" (this method is registered by 1 client(s)).
02/14/19 14:08:35.575 IPC Server: Response: 
(void)
02/14/19 14:08:36.088 IPC Server: Info: Connection accepted. Client number: 14
02/14/19 14:08:36.088 IPC Server: Info: Client number 1 is calling RPC method: registerRpcMethod
(String) websshGetLastOutputs
(Array length=1)
{
  (Array length=1)
  {
    (Array length=0)
    {
    }
  }
}
02/14/19 14:08:36.088 IPC Server: Info: Client 1 successfully registered RPC method "websshGetLastOutputs" (this method is registered by 1 client(s)).
02/14/19 14:08:36.088 IPC Server: Response: 
(void)
02/14/19 14:08:36.088 IPC Server: Info: Client number 1 is calling RPC method: registerRpcMethod
(String) websshInput
(Array length=1)
{
  (Array length=2)
  {
    (void)
    (String) 
  }
}
02/14/19 14:08:36.088 IPC Server: Info: Client 1 successfully registered RPC method "websshInput" (this method is registered by 1 client(s)).
02/14/19 14:08:36.088 IPC Server: Response: 
(void)
02/14/19 14:08:36.089 IPC Server: Info: Client number 1 is calling RPC method: registerRpcMethod
(String) websshSetScreenSize
(Array length=1)
{
  (Array length=2)
  {
    (void)
    (Integer64) 0
  }
}
02/14/19 14:08:36.089 IPC Server: Info: Client 1 successfully registered RPC method "websshSetScreenSize" (this method is registered by 1 client(s)).
02/14/19 14:08:36.089 IPC Server: Response: 
(void)
02/14/19 14:08:36.817 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-EG": Debug: Packet received from HM-CFG-LAN (encrypted): E3531D7,0000,4C9E9D0D,FF,FFBA,30865E3531D700000013FF4500684C
02/14/19 14:08:36.818 Debug (HM-CFG-LAN-EG): Packet 0F30865E3531D700000013FF4500684C enters raisePacketReceived.
02/14/19 14:08:36.818 Debug (HM-CFG-LAN-EG): Packet 0F30865E3531D700000013FF4500684C is now passed to the EventHandler.
02/14/19 14:08:36.818 HomeMatic BidCoS packet received (HM-CFG-LAN-EG, RSSI: -70 dBm): 0F30865E3531D700000013FF4500684C
02/14/19 14:08:36.818 Module HomeMatic BidCoS: Info: BOOT on channel 1 of HomeMatic BidCoS peer 27 with serial number MEQ0026179 was set to 0x00.
02/14/19 14:08:36.818 Module HomeMatic BidCoS: Info: ENERGY_COUNTER on channel 1 of HomeMatic BidCoS peer 27 with serial number MEQ0026179 was set to 0x13FF45.
02/14/19 14:08:36.818 Module HomeMatic BidCoS: Info: POWER on channel 1 of HomeMatic BidCoS peer 27 with serial number MEQ0026179 was set to 0x00684C.
02/14/19 14:08:36.818 Debug (HM-CFG-LAN-EG): Packet processing of packet 0F30865E3531D700000013FF4500684C took 0 ms.
02/14/19 14:08:36.819 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-OG": Debug: Packet received from HM-CFG-LAN (encrypted): E3531D7,0000,33326129,FF,FFAE,30865E3531D700000013FF4500684C
02/14/19 14:08:36.826 Debug (HM-CFG-LAN-OG): Packet 0F30865E3531D700000013FF4500684C enters raisePacketReceived.
02/14/19 14:08:36.826 Debug (HM-CFG-LAN-OG): Packet 0F30865E3531D700000013FF4500684C is now passed to the EventHandler.
02/14/19 14:08:36.826 HomeMatic BidCoS packet received (HM-CFG-LAN-OG, RSSI: -82 dBm): 0F30865E3531D700000013FF4500684C
02/14/19 14:08:36.827 Debug (HM-CFG-LAN-OG): Packet processing of packet 0F30865E3531D700000013FF4500684C took 1 ms.
02/14/19 14:08:41.821 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-EG": Debug: Sending (encrypted): T23F824D9,02,00,00000000
02/14/19 14:08:41.829 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-OG": Debug: Sending (encrypted): T23F824D9,02,00,00000000
02/14/19 14:08:43.250 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-EG": Debug: Packet received from HM-CFG-LAN (encrypted): E234F97,0000,4C9EB628,FF,FFCE,FE8610234F970000000AB4E20B0700
02/14/19 14:08:43.250 Debug (HM-CFG-LAN-EG): Packet 0FFE8610234F970000000AB4E20B0700 enters raisePacketReceived.
02/14/19 14:08:43.250 Debug (HM-CFG-LAN-EG): Packet 0FFE8610234F970000000AB4E20B0700 is now passed to the EventHandler.
02/14/19 14:08:43.250 HomeMatic BidCoS packet received (HM-CFG-LAN-EG, RSSI: -50 dBm): 0FFE8610234F970000000AB4E20B0700
02/14/19 14:08:43.250 Module HomeMatic BidCoS: Info: ACTUAL_TEMPERATURE on channel 4 of HomeMatic BidCoS peer 31 with serial number KEQ0574517 was set to 0x00E2.
02/14/19 14:08:43.250 Module HomeMatic BidCoS: Info: BATTERY_STATE on channel 4 of HomeMatic BidCoS peer 31 with serial number KEQ0574517 was set to 0x0B.
02/14/19 14:08:43.250 Module HomeMatic BidCoS: Info: BOOST_STATE on channel 4 of HomeMatic BidCoS peer 31 with serial number KEQ0574517 was set to 0x00.
02/14/19 14:08:43.250 Module HomeMatic BidCoS: Info: CONTROL_MODE on channel 4 of HomeMatic BidCoS peer 31 with serial number KEQ0574517 was set to 0x00.
02/14/19 14:08:43.250 Module HomeMatic BidCoS: Info: FAULT_REPORTING on channel 4 of HomeMatic BidCoS peer 31 with serial number KEQ0574517 was set to 0x00.
02/14/19 14:08:43.251 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-OG": Debug: Packet received from HM-CFG-LAN (encrypted): E234F97,0000,33327A44,FF,FFBC,FE8610234F970000000AB4E20B0700
02/14/19 14:08:43.251 Debug (HM-CFG-LAN-OG): Packet 0FFE8610234F970000000AB4E20B0700 enters raisePacketReceived.
02/14/19 14:08:43.251 Debug (HM-CFG-LAN-OG): Packet 0FFE8610234F970000000AB4E20B0700 is now passed to the EventHandler.
02/14/19 14:08:43.251 HomeMatic BidCoS packet received (HM-CFG-LAN-OG, RSSI: -68 dBm): 0FFE8610234F970000000AB4E20B0700
02/14/19 14:08:43.251 Debug (HM-CFG-LAN-OG): Packet processing of packet 0FFE8610234F970000000AB4E20B0700 took 0 ms.
02/14/19 14:08:43.446 Module HomeMatic BidCoS: Info: PARTY_START_TIME on channel 4 of HomeMatic BidCoS peer 31 with serial number KEQ0574517 was set to 0x00.
02/14/19 14:08:43.447 Module HomeMatic BidCoS: Info: SET_TEMPERATURE on channel 4 of HomeMatic BidCoS peer 31 with serial number KEQ0574517 was set to 0x2D.
02/14/19 14:08:43.447 Module HomeMatic BidCoS: Info: VALVE_STATE on channel 4 of HomeMatic BidCoS peer 31 with serial number KEQ0574517 was set to 0x07.
02/14/19 14:08:43.447 Debug (HM-CFG-LAN-EG): Packet processing of packet 0FFE8610234F970000000AB4E20B0700 took 197 ms.
02/14/19 14:08:44.231 Debug: Calling getFileDescriptor...
02/14/19 14:08:44.231 Debug: Connecting to host 192.168.0.2 on port 1000...
02/14/19 14:08:44.479 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-EG": Debug: Packet received from HM-CFG-LAN (encrypted): E234EE5,0000,4C9EBAF5,FF,FFCE,A68610234EE50000000AB4E20C0700
02/14/19 14:08:44.479 Debug (HM-CFG-LAN-EG): Packet 0FA68610234EE50000000AB4E20C0700 enters raisePacketReceived.
02/14/19 14:08:44.479 Debug (HM-CFG-LAN-EG): Packet 0FA68610234EE50000000AB4E20C0700 is now passed to the EventHandler.
02/14/19 14:08:44.479 HomeMatic BidCoS packet received (HM-CFG-LAN-EG, RSSI: -50 dBm): 0FA68610234EE50000000AB4E20C0700
02/14/19 14:08:44.479 Module HomeMatic BidCoS: Info: ACTUAL_TEMPERATURE on channel 4 of HomeMatic BidCoS peer 30 with serial number KEQ0574710 was set to 0x00E2.
02/14/19 14:08:44.479 Module HomeMatic BidCoS: Info: BATTERY_STATE on channel 4 of HomeMatic BidCoS peer 30 with serial number KEQ0574710 was set to 0x0C.
02/14/19 14:08:44.479 Module HomeMatic BidCoS: Info: BOOST_STATE on channel 4 of HomeMatic BidCoS peer 30 with serial number KEQ0574710 was set to 0x00.
02/14/19 14:08:44.479 Module HomeMatic BidCoS: Info: CONTROL_MODE on channel 4 of HomeMatic BidCoS peer 30 with serial number KEQ0574710 was set to 0x00.
02/14/19 14:08:44.479 Module HomeMatic BidCoS: Info: FAULT_REPORTING on channel 4 of HomeMatic BidCoS peer 30 with serial number KEQ0574710 was set to 0x00.
02/14/19 14:08:44.480 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-OG": Debug: Packet received from HM-CFG-LAN (encrypted): E234EE5,0000,33327F11,FF,FFC3,A68610234EE50000000AB4E20C0700
02/14/19 14:08:44.480 Debug (HM-CFG-LAN-OG): Packet 0FA68610234EE50000000AB4E20C0700 enters raisePacketReceived.
02/14/19 14:08:44.480 Debug (HM-CFG-LAN-OG): Packet 0FA68610234EE50000000AB4E20C0700 is now passed to the EventHandler.
02/14/19 14:08:44.480 HomeMatic BidCoS packet received (HM-CFG-LAN-OG, RSSI: -61 dBm): 0FA68610234EE50000000AB4E20C0700
02/14/19 14:08:44.480 Debug (HM-CFG-LAN-OG): Packet processing of packet 0FA68610234EE50000000AB4E20C0700 took 0 ms.
02/14/19 14:08:44.519 Module HomeMatic BidCoS: Info: PARTY_START_TIME on channel 4 of HomeMatic BidCoS peer 30 with serial number KEQ0574710 was set to 0x00.
02/14/19 14:08:44.519 Module HomeMatic BidCoS: Info: SET_TEMPERATURE on channel 4 of HomeMatic BidCoS peer 30 with serial number KEQ0574710 was set to 0x2D.
02/14/19 14:08:44.519 Module HomeMatic BidCoS: Info: VALVE_STATE on channel 4 of HomeMatic BidCoS peer 30 with serial number KEQ0574710 was set to 0x07.
02/14/19 14:08:44.520 Debug (HM-CFG-LAN-EG): Packet processing of packet 0FA68610234EE50000000AB4E20C0700 took 41 ms.
02/14/19 14:08:46.203 HM-LGW "HM-LGW": Warning: Connection closed. Trying to reconnect...
02/14/19 14:08:47.511 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-OG": Debug: Packet received from HM-CFG-LAN (encrypted): E234ED1,0000,33328AEA,FF,FFD9,E98610234ED10000000AACEB0D0700
02/14/19 14:08:47.511 Debug (HM-CFG-LAN-OG): Packet 0FE98610234ED10000000AACEB0D0700 enters raisePacketReceived.
02/14/19 14:08:47.511 Debug (HM-CFG-LAN-OG): Packet 0FE98610234ED10000000AACEB0D0700 is now passed to the EventHandler.
02/14/19 14:08:47.511 HomeMatic BidCoS packet received (HM-CFG-LAN-OG, RSSI: -39 dBm): 0FE98610234ED10000000AACEB0D0700
02/14/19 14:08:47.511 Module HomeMatic BidCoS: Info: ACTUAL_TEMPERATURE on channel 4 of HomeMatic BidCoS peer 60 with serial number KEQ0574725 was set to 0x00EB.
02/14/19 14:08:47.512 Module HomeMatic BidCoS: Info: BATTERY_STATE on channel 4 of HomeMatic BidCoS peer 60 with serial number KEQ0574725 was set to 0x0D.
02/14/19 14:08:47.512 Module HomeMatic BidCoS: Info: BOOST_STATE on channel 4 of HomeMatic BidCoS peer 60 with serial number KEQ0574725 was set to 0x00.
02/14/19 14:08:47.512 Module HomeMatic BidCoS: Info: CONTROL_MODE on channel 4 of HomeMatic BidCoS peer 60 with serial number KEQ0574725 was set to 0x00.
02/14/19 14:08:47.512 Module HomeMatic BidCoS: Info: FAULT_REPORTING on channel 4 of HomeMatic BidCoS peer 60 with serial number KEQ0574725 was set to 0x00.
02/14/19 14:08:47.513 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-EG": Debug: Packet received from HM-CFG-LAN (encrypted): E234ED1,0000,4C9EC6CE,FF,FFBC,E98610234ED10000000AACEB0D0700
02/14/19 14:08:47.513 Debug (HM-CFG-LAN-EG): Packet 0FE98610234ED10000000AACEB0D0700 enters raisePacketReceived.
02/14/19 14:08:47.513 Debug (HM-CFG-LAN-EG): Packet 0FE98610234ED10000000AACEB0D0700 is now passed to the EventHandler.
02/14/19 14:08:47.513 HomeMatic BidCoS packet received (HM-CFG-LAN-EG, RSSI: -68 dBm): 0FE98610234ED10000000AACEB0D0700
02/14/19 14:08:47.513 Debug (HM-CFG-LAN-EG): Packet processing of packet 0FE98610234ED10000000AACEB0D0700 took 0 ms.
02/14/19 14:08:49.052 Module HomeMatic BidCoS: Info: PARTY_START_TIME on channel 4 of HomeMatic BidCoS peer 60 with serial number KEQ0574725 was set to 0x00.
02/14/19 14:08:49.052 Module HomeMatic BidCoS: Info: SET_TEMPERATURE on channel 4 of HomeMatic BidCoS peer 60 with serial number KEQ0574725 was set to 0x2B.
02/14/19 14:08:49.052 Module HomeMatic BidCoS: Info: VALVE_STATE on channel 4 of HomeMatic BidCoS peer 60 with serial number KEQ0574725 was set to 0x07.
02/14/19 14:08:49.052 Debug (HM-CFG-LAN-OG): Packet processing of packet 0FE98610234ED10000000AACEB0D0700 took 1541 ms.
02/14/19 14:08:49.052 Info (HM-CFG-LAN-OG): Packet processing took longer than 1 second (1541 ms).
02/14/19 14:08:50.978 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-EG": Debug: Packet received from HM-CFG-LAN (encrypted): E5F94AF,0000,4C9ED459,FF,FFC2,5286105F94AF0000000AA0DA0C0000
02/14/19 14:08:50.978 Debug (HM-CFG-LAN-EG): Packet 0F5286105F94AF0000000AA0DA0C0000 enters raisePacketReceived.
02/14/19 14:08:50.978 Debug (HM-CFG-LAN-EG): Packet 0F5286105F94AF0000000AA0DA0C0000 is now passed to the EventHandler.
02/14/19 14:08:50.978 HomeMatic BidCoS packet received (HM-CFG-LAN-EG, RSSI: -62 dBm): 0F5286105F94AF0000000AA0DA0C0000
02/14/19 14:08:50.978 Module HomeMatic BidCoS: Info: ACTUAL_TEMPERATURE on channel 4 of HomeMatic BidCoS peer 33 with serial number OEQ1697949 was set to 0x00DA.
02/14/19 14:08:50.978 Module HomeMatic BidCoS: Info: BATTERY_STATE on channel 4 of HomeMatic BidCoS peer 33 with serial number OEQ1697949 was set to 0x0C.
02/14/19 14:08:50.978 Module HomeMatic BidCoS: Info: BOOST_STATE on channel 4 of HomeMatic BidCoS peer 33 with serial number OEQ1697949 was set to 0x00.
02/14/19 14:08:50.978 Module HomeMatic BidCoS: Info: CONTROL_MODE on channel 4 of HomeMatic BidCoS peer 33 with serial number OEQ1697949 was set to 0x00.
02/14/19 14:08:50.978 Module HomeMatic BidCoS: Info: FAULT_REPORTING on channel 4 of HomeMatic BidCoS peer 33 with serial number OEQ1697949 was set to 0x00.
02/14/19 14:08:50.978 Module HomeMatic BidCoS: Info: PARTY_START_TIME on channel 4 of HomeMatic BidCoS peer 33 with serial number OEQ1697949 was set to 0x00.
02/14/19 14:08:50.978 Module HomeMatic BidCoS: Info: SET_TEMPERATURE on channel 4 of HomeMatic BidCoS peer 33 with serial number OEQ1697949 was set to 0x28.
02/14/19 14:08:50.978 Module HomeMatic BidCoS: Info: VALVE_STATE on channel 4 of HomeMatic BidCoS peer 33 with serial number OEQ1697949 was set to 0x00.
02/14/19 14:08:50.978 Debug (HM-CFG-LAN-EG): Packet processing of packet 0F5286105F94AF0000000AA0DA0C0000 took 0 ms.
02/14/19 14:08:50.979 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-OG": Debug: Packet received from HM-CFG-LAN (encrypted): E5F94AF,0000,33329875,FF,FFC2,5286105F94AF0000000AA0DA0C0000
02/14/19 14:08:50.979 Debug (HM-CFG-LAN-OG): Packet 0F5286105F94AF0000000AA0DA0C0000 enters raisePacketReceived.
02/14/19 14:08:50.979 Debug (HM-CFG-LAN-OG): Packet 0F5286105F94AF0000000AA0DA0C0000 is now passed to the EventHandler.
02/14/19 14:08:50.979 HomeMatic BidCoS packet received (HM-CFG-LAN-OG, RSSI: -62 dBm): 0F5286105F94AF0000000AA0DA0C0000
02/14/19 14:08:50.979 Debug (HM-CFG-LAN-OG): Packet processing of packet 0F5286105F94AF0000000AA0DA0C0000 took 0 ms.
02/14/19 14:08:53.249 Debug: Calling getFileDescriptor...
02/14/19 14:08:53.249 Debug: Connecting to host 192.168.0.2 on port 1000...
02/14/19 14:08:55.980 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-OG": Debug: Sending (encrypted): K
02/14/19 14:08:55.982 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-EG": Debug: Sending (encrypted): K
02/14/19 14:08:56.007 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-OG": Debug: Packet received from HM-CFG-LAN (encrypted): HHM-LAN-IF,03C5,HEQ0400391,1535C5,FD1309,3332AC25,0013,01
02/14/19 14:08:56.009 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-EG": Debug: Packet received from HM-CFG-LAN (encrypted): HHM-LAN-IF,03C5,HEQ0400155,1536AE,FD1309,4C9EE80B,001D,01
02/14/19 14:08:57.979 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-EG": Debug: Packet received from HM-CFG-LAN (encrypted): E2351D8,0000,4C9EEFBA,FF,FFCB,3386102351D80000000A90BC0F0040
02/14/19 14:08:57.979 Debug (HM-CFG-LAN-EG): Packet 0F3386102351D80000000A90BC0F0040 enters raisePacketReceived.
02/14/19 14:08:57.979 Debug (HM-CFG-LAN-EG): Packet 0F3386102351D80000000A90BC0F0040 is now passed to the EventHandler.
02/14/19 14:08:57.979 HomeMatic BidCoS packet received (HM-CFG-LAN-EG, RSSI: -53 dBm): 0F3386102351D80000000A90BC0F0040
02/14/19 14:08:57.980 Module HomeMatic BidCoS: Info: ACTUAL_TEMPERATURE on channel 4 of HomeMatic BidCoS peer 23 with serial number KEQ0652771 was set to 0x00BC.
02/14/19 14:08:57.980 Module HomeMatic BidCoS: Info: BATTERY_STATE on channel 4 of HomeMatic BidCoS peer 23 with serial number KEQ0652771 was set to 0x0F.
02/14/19 14:08:57.980 Module HomeMatic BidCoS: Info: BOOST_STATE on channel 4 of HomeMatic BidCoS peer 23 with serial number KEQ0652771 was set to 0x00.
02/14/19 14:08:57.980 Module HomeMatic BidCoS: Info: CONTROL_MODE on channel 4 of HomeMatic BidCoS peer 23 with serial number KEQ0652771 was set to 0x01.
02/14/19 14:08:57.980 Module HomeMatic BidCoS: Info: FAULT_REPORTING on channel 4 of HomeMatic BidCoS peer 23 with serial number KEQ0652771 was set to 0x00.
02/14/19 14:08:57.980 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-OG": Debug: Packet received from HM-CFG-LAN (encrypted): E2351D8,0000,3332B3D5,FF,FFB1,3386102351D80000000A90BC0F0040
02/14/19 14:08:57.980 Debug (HM-CFG-LAN-OG): Packet 0F3386102351D80000000A90BC0F0040 enters raisePacketReceived.
02/14/19 14:08:57.980 Debug (HM-CFG-LAN-OG): Packet 0F3386102351D80000000A90BC0F0040 is now passed to the EventHandler.
02/14/19 14:08:57.980 HomeMatic BidCoS packet received (HM-CFG-LAN-OG, RSSI: -79 dBm): 0F3386102351D80000000A90BC0F0040
02/14/19 14:08:57.980 Debug (HM-CFG-LAN-OG): Packet processing of packet 0F3386102351D80000000A90BC0F0040 took 0 ms.
02/14/19 14:08:57.998 Module HomeMatic BidCoS: Info: PARTY_START_TIME on channel 4 of HomeMatic BidCoS peer 23 with serial number KEQ0652771 was set to 0x00.
02/14/19 14:08:57.999 Module HomeMatic BidCoS: Info: SET_TEMPERATURE on channel 4 of HomeMatic BidCoS peer 23 with serial number KEQ0652771 was set to 0x24.
02/14/19 14:08:57.999 Module HomeMatic BidCoS: Info: VALVE_STATE on channel 4 of HomeMatic BidCoS peer 23 with serial number KEQ0652771 was set to 0x00.
02/14/19 14:08:57.999 Debug (HM-CFG-LAN-EG): Packet processing of packet 0F3386102351D80000000A90BC0F0040 took 20 ms.
02/14/19 14:09:02.267 Debug: Calling getFileDescriptor...
02/14/19 14:09:02.267 Debug: Connecting to host 192.168.0.2 on port 1000...
02/14/19 14:09:05.200 HM-LGW "HM-LGW": Error: No init packet received.
02/14/19 14:09:05.200 HM-LGW "HM-LGW": Info: No AES key specified in homematicbidcos.conf for communication with your HM-LGW. Disabling AES.
02/14/19 14:09:05.200 HM-LGW "HM-LGW": Connecting to HM-LGW with hostname 192.168.0.19 on port 2000...
02/14/19 14:09:05.200 Debug: Calling getFileDescriptor...
02/14/19 14:09:05.200 Debug: Connecting to host 192.168.0.19 on port 2000...
02/14/19 14:09:05.201 Debug: Connected to host 192.168.0.19 on port 2000. Client number is: 24
02/14/19 14:09:05.201 Debug: Calling getFileDescriptor...
02/14/19 14:09:05.201 Debug: Connecting to host 192.168.0.19 on port 2001...
02/14/19 14:09:05.202 Debug: Connected to host 192.168.0.19 on port 2001. Client number is: 25
02/14/19 14:09:05.202 HM-LGW "HM-LGW": Connected to HM-LGW with hostname 192.168.0.19 on port 2000.
02/14/19 14:09:05.202 HM-LGW "HM-LGW": Warning: Connection to client number 24 closed (3).
02/14/19 14:09:07.639 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-OG": Debug: Packet received from HM-CFG-LAN (encrypted): E29D7DE,0000,3332D98D,FF,FFC4,35861029D7DE0000000A90C60E0000
02/14/19 14:09:07.639 Debug (HM-CFG-LAN-OG): Packet 0F35861029D7DE0000000A90C60E0000 enters raisePacketReceived.
02/14/19 14:09:07.639 Debug (HM-CFG-LAN-OG): Packet 0F35861029D7DE0000000A90C60E0000 is now passed to the EventHandler.
02/14/19 14:09:07.639 HomeMatic BidCoS packet received (HM-CFG-LAN-OG, RSSI: -60 dBm): 0F35861029D7DE0000000A90C60E0000
02/14/19 14:09:07.639 Module HomeMatic BidCoS: Info: ACTUAL_TEMPERATURE on channel 4 of HomeMatic BidCoS peer 41 with serial number LEQ0257160 was set to 0x00C6.
02/14/19 14:09:07.640 Module HomeMatic BidCoS: Info: BATTERY_STATE on channel 4 of HomeMatic BidCoS peer 41 with serial number LEQ0257160 was set to 0x0E.
02/14/19 14:09:07.640 Module HomeMatic BidCoS: Info: BOOST_STATE on channel 4 of HomeMatic BidCoS peer 41 with serial number LEQ0257160 was set to 0x00.
02/14/19 14:09:07.640 Module HomeMatic BidCoS: Info: CONTROL_MODE on channel 4 of HomeMatic BidCoS peer 41 with serial number LEQ0257160 was set to 0x00.
02/14/19 14:09:07.640 Module HomeMatic BidCoS: Info: FAULT_REPORTING on channel 4 of HomeMatic BidCoS peer 41 with serial number LEQ0257160 was set to 0x00.
02/14/19 14:09:07.640 Module HomeMatic BidCoS: Info: PARTY_START_TIME on channel 4 of HomeMatic BidCoS peer 41 with serial number LEQ0257160 was set to 0x00.
02/14/19 14:09:07.640 Module HomeMatic BidCoS: Info: SET_TEMPERATURE on channel 4 of HomeMatic BidCoS peer 41 with serial number LEQ0257160 was set to 0x24.
02/14/19 14:09:07.640 Module HomeMatic BidCoS: Info: VALVE_STATE on channel 4 of HomeMatic BidCoS peer 41 with serial number LEQ0257160 was set to 0x00.
02/14/19 14:09:07.640 Debug (HM-CFG-LAN-OG): Packet processing of packet 0F35861029D7DE0000000A90C60E0000 took 1 ms.
02/14/19 14:09:07.640 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-EG": Debug: Packet received from HM-CFG-LAN (encrypted): E29D7DE,0000,4C9F1571,FF,FFB8,35861029D7DE0000000A90C60E0000
02/14/19 14:09:07.640 Debug (HM-CFG-LAN-EG): Packet 0F35861029D7DE0000000A90C60E0000 enters raisePacketReceived.
02/14/19 14:09:07.640 Debug (HM-CFG-LAN-EG): Packet 0F35861029D7DE0000000A90C60E0000 is now passed to the EventHandler.
02/14/19 14:09:07.640 HomeMatic BidCoS packet received (HM-CFG-LAN-EG, RSSI: -72 dBm): 0F35861029D7DE0000000A90C60E0000
02/14/19 14:09:07.640 Debug (HM-CFG-LAN-EG): Packet processing of packet 0F35861029D7DE0000000A90C60E0000 took 0 ms.
02/14/19 14:09:09.913 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-OG": Debug: Packet received from HM-CFG-LAN (encrypted): E634564,0000,3332E26F,FF,FFC1,DE865A63456400000090C62C
02/14/19 14:09:09.913 Debug (HM-CFG-LAN-OG): Packet 0CDE865A63456400000090C62C enters raisePacketReceived.
02/14/19 14:09:09.913 Debug (HM-CFG-LAN-OG): Packet 0CDE865A63456400000090C62C is now passed to the EventHandler.
02/14/19 14:09:09.913 HomeMatic BidCoS packet received (HM-CFG-LAN-OG, RSSI: -63 dBm): 0CDE865A63456400000090C62C
02/14/19 14:09:09.913 Module HomeMatic BidCoS: Info: ACTUAL_HUMIDITY on channel 2 of HomeMatic BidCoS peer 56 with serial number OEQ1676498 was set to 0x2C.
02/14/19 14:09:09.913 Module HomeMatic BidCoS: Info: ACTUAL_TEMPERATURE on channel 2 of HomeMatic BidCoS peer 56 with serial number OEQ1676498 was set to 0x00C6.
02/14/19 14:09:09.913 Module HomeMatic BidCoS: Info: SET_TEMPERATURE on channel 2 of HomeMatic BidCoS peer 56 with serial number OEQ1676498 was set to 0x24.
02/14/19 14:09:09.913 Debug (HM-CFG-LAN-OG): Packet processing of packet 0CDE865A63456400000090C62C took 0 ms.
02/14/19 14:09:09.914 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN-EG": Debug: Packet received from HM-CFG-LAN (encrypted): E634564,0000,4C9F1E53,FF,FFB7,DE865A63456400000090C62C
02/14/19 14:09:09.914 Debug (HM-CFG-LAN-EG): Packet 0CDE865A63456400000090C62C enters raisePacketReceived.
02/14/19 14:09:09.914 Debug (HM-CFG-LAN-EG): Packet 0CDE865A63456400000090C62C is now passed to the EventHandler.
02/14/19 14:09:09.914 HomeMatic BidCoS packet received (HM-CFG-LAN-EG, RSSI: -73 dBm): 0CDE865A63456400000090C62C
02/14/19 14:09:09.914 Debug (HM-CFG-LAN-EG): Packet processing of packet 0CDE865A63456400000090C62C took 0 ms.