Das verstehe ich nicht, wieso wolltest Du dann eine CCU hinzufügen?
Das war auch mal meine Strategie, nur mit openHAB. Mittlerweile ist aber es nur noch die UI und ein paar Automatisierungen, nichts Kritisches mehr. Alles, was von Homegear unterstützt wird, ist nach Homegear gewandert. 
ich will ja wie oben geschrieben keine echte ccu hinzufügen, sondern eine auf ein funk-gateway umgeflashte ccu-hardware. und das geht eben stand heute nicht mit homegear. zur zeit habe ich 3 stück lan config gateways mit homegear im einsatz, damit kann man aber keine firmware updates von hm geräten durchführen. da wäre dieses umgeflahste gateway für mich die perfekte kombination.
ich bleibe für alles “kritische” inkl. der automatisierungen auf jeden fall bei home assistant, bin hiervon schlicht begeistert. vor allem auch von der entwicklungsgeschwindigkeit und der community
und ich habe immer noch keinen pi rumliegen… und möchte auch nicht extra einen kaufen den ich dann zusätzlich administrieren muss. 
Hallo @nicx
ich habe jetzt ins nächste Nightly mal eingebaut, dass kein lanKey benötigt wird. Probier mal, ob’s klappt. Das ist jetzt ungetestet. Falls nicht, bitte die Logausgabe posten ;-).
Viele Grüße
Sathya
danke schon mal @sathya, aber leider funktioniert es nicht. Ich bekomme jetzt nur noch diese Fehlermeldung:
01/28/19 15:12:45.777 HM-LGW "HM-LGW": Error: No security key specified in homematicbidcos.conf.
aber das GW ist laut Admin UI im Status “nicht verbunden”.
Von wann ist das nightly, was du installiert hast? Du willst 0.8.0-2508…
Bis jetzt ist nur die debian stretch-amd64-Variante und debian jessie-armhf vom 28.1., alle Anderen noch vom 27.1.: https://homegear.eu/downloads.html?version=0.8
ok das erklärt es vielleicht: ich habe 0.8.0-2505 von heute morgen. ich nutze Docker, d.h. evtl. hab ich nen tag Versatz drin. ich versuche es morgen wieder
so jetzt mit der 2508 sieht es ein wenig anders aus, hier die logausgabe:
01/29/19 07:35:30.106 HM-LGW "HM-LGW": Warning: Too large packet received: 4830332C30312C526576696C6F2D484D2D4C47572C302E302E322C434355324757303030310D0A
01/29/19 07:35:30.107 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.
01/29/19 07:35:42.106 HM-LGW "HM-LGW": Error: No response received to packet: FD0003000003180A
01/29/19 07:35:42.106 HM-LGW "HM-LGW": Error: Unknown packet received in response to init packet. Reconnecting...
Das Gateway wird in der UI dann natürlich als nicht connected angezeigt. Auch ein reconnect passiert nicht, d.h. diese Meldungen erscheinen nicht wieder.
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
@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 (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
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
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