Openhab Kommunikation funktioniert nicht für ein Thing

TheBlueKL · June 16, 2018, 5:12pm

Hallo,

bei mir läuft Openhab2 (2.3 stable) und Homegear(version 0.7.19-1846) auf dem Raspi 3.
Per Homegear lasse ich mittels HM-MOD-RPI-PCB die Homematic Aktoren einbinden.
Nach einem konfigurationsfehler ging jetzt das einlesen von 3 Geräten.
1 Heiz.Thermostat HG-HM-CC-RT-DN
2 Rolladenschalter HM-LC-Bl1PBU-FM

Die weiteren Geräte bekomme ich jetzt trotz Abmelden in der alten Zentrale und Werksreset nicht mehr angemeldet. Neue “jungfreuliche” muss ich erst noch fertig machen.

Das Fritzbox Binding scheint zu laufen. Diese Geräte sind da und online.

Jedoch reagieren die angelernten Geräte auch nicht in openHAB.

Mich stören die Errors auch. Kann mir jemand erklären was da evtl. los ist? Das hält sich dran…
Warum wiederholt sich ständif (Module HomeMatic BidCoS: HM-MOD-RPI-PCB “My-HM-MOD-RPI-PCB”: Error: No response received to packet: FD0003000003180A) +++

Warum connected sich mein NAS (192.168.2.9:53673) hier?
06/16/18 17:39:37.298 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.2.9:53673 accepted. Client number: 32
06/16/18 17:39:37.299 RPC Server (Port 2001): Info: RPC server client id for client number 32 is: 3

tail -n 1000 -f /var/log/homegear/homegear.log

06/16/18 17:38:32.011 Starting Homegear...
06/16/18 17:38:32.011 Homegear version 0.7.19-1846
06/16/18 17:38:32.011 Git commit SHA of libhomegear-base: -
06/16/18 17:38:32.011 Git branch of libhomegear-base:     -
06/16/18 17:38:32.011 Git commit SHA of Homegear:         -
06/16/18 17:38:32.011 Git branch of Homegear:             -
06/16/18 17:38:32.012 Info: Setting allowed core file size to "4294967295" for user with id 0 and group with id 0.
06/16/18 17:38:32.012 Info: Core file size now is "4294967295".
06/16/18 17:38:32.012 Info: Setting maximum thread priority to "4294967295" for user with id 0 and group with id 0.
06/16/18 17:38:32.012 Info: Maximum thread priority now is "4294967295".
06/16/18 17:38:32.023 Info: Backing up database...
06/16/18 17:38:34.400 Initializing database...
06/16/18 17:38:34.410 Info: Loading family module mod_homematicbidcos.so
06/16/18 17:38:34.434 /etc/homegear/families/homematicbidcos.conf
06/16/18 17:38:34.436 Info: Loading family module mod_miscellaneous.so
06/16/18 17:38:34.442 /etc/homegear/families/miscellaneous.conf
06/16/18 17:38:34.443 Info: Loading family module mod_homematicwired.so
06/16/18 17:38:34.454 /etc/homegear/families/homematicwired.conf
06/16/18 17:38:34.455 Info: Setting up physical interfaces and GPIOs...
06/16/18 17:38:34.458 Info: Dropping privileges to user homegear (110) and group homegear (115)
06/16/18 17:38:34.459 Info: Homegear is (now) running as user with id 110 and group with id 115.
06/16/18 17:38:34.473 Starting script engine server...
06/16/18 17:38:34.488 Initializing licensing controller...
06/16/18 17:38:34.489 Loading licensing controller data...
06/16/18 17:38:34.489 Loading devices...
06/16/18 17:38:34.489 Loading XML RPC devices...
06/16/18 17:38:35.402 Loading device 1
06/16/18 17:38:35.403 Module HomeMatic BidCoS: Info: Central address set to 0xFDxxxx.
06/16/18 17:38:35.404 Module HomeMatic BidCoS: Loading peer 1
06/16/18 17:38:35.422 Module HomeMatic BidCoS: Loading peer 2
06/16/18 17:38:35.432 Module HomeMatic BidCoS: Loading peer 3
06/16/18 17:38:35.442 Loading XML RPC devices...
06/16/18 17:38:35.493 Loading device 2
06/16/18 17:38:35.494 Loading XML RPC devices...
06/16/18 17:38:35.495 Loading device 3
06/16/18 17:38:35.496 Initializing RPC client...
06/16/18 17:38:35.496 Starting XML RPC server RPCServer1 listening on :::2001...
06/16/18 17:38:35.499 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.
06/16/18 17:38:35.499 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.
06/16/18 17:38:35.500 Starting XML RPC server RPCServer2 listening on :::2002, SSL enabled...
06/16/18 17:38:35.500 RPC Server (Port 2001): Info: RPC Server started listening on address :: and port 2001
06/16/18 17:38:35.503 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.
06/16/18 17:38:35.539 Starting XML RPC server RPCServer3 listening on :::2003, SSL enabled, authentication enabled...
06/16/18 17:38:35.540 RPC Server (Port 2002): Info: RPC Server started listening on address :: and port 2002
06/16/18 17:38:35.573 Starting CLI server...
06/16/18 17:38:35.573 RPC Server (Port 2003): Info: RPC Server started listening on address :: and port 2003
06/16/18 17:38:35.573 Initializing event handler...
06/16/18 17:38:35.574 Loading events...
06/16/18 17:38:35.574 Start listening for packets...
06/16/18 17:38:37.575 Starting Node-BLUE server...
06/16/18 17:38:37.584 Starting IPC server...
06/16/18 17:38:37.592 Startup complete. Waiting for physical interfaces to connect.
06/16/18 17:38:37.592 Info: Waiting for physical interfaces to connect (0 of 180s).
06/16/18 17:38:37.593 All physical interfaces are connected now.
06/16/18 17:38:37.593 Starting UPnP server...
06/16/18 17:38:37.594 Info: UPnP server: Binding to address: 192.168.xx.xx
06/16/18 17:38:37.594 UPnP Server: Info: Started listening.
06/16/18 17:38:37.877 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.xx.xx:60438 accepted. Client number: 13
06/16/18 17:38:37.878 RPC Server (Port 2001): Info: RPC server client id for client number 13 is: 0
06/16/18 17:38:37.879 RPC Server (Port 2001): Info: Client number 13 is calling RPC method: ping (2) Parameters:
(String) c28e855a
06/16/18 17:38:44.576 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No response received to packet: FD0003000003180A
06/16/18 17:38:44.576 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: Unknown packet received in response to init packet. Reconnecting...
06/16/18 17:38:46.146 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
06/16/18 17:38:48.148 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Connected to HM-MOD-RPI-PCB.
06/16/18 17:38:52.887 RPC Server (Port 2001): Info: Client number 13 is calling RPC method: init (2) Parameters:
(String) binary://192.168.2.51:9126
06/16/18 17:38:52.888 Info: Client with IP ::ffff:192.168.xx.xx is calling "init".
06/16/18 17:38:52.896 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.xx.xx:60446 accepted. Client number: 16
06/16/18 17:38:52.896 RPC Server (Port 2001): Info: RPC server client id for client number 16 is: 1
06/16/18 17:38:52.898 RPC Server (Port 2001): Info: Client number 16 is calling RPC method: init (2) Parameters:
(String) binary://192.168.xx.xx:9126
(String) RF-c28e855a
(Integer) 34
06/16/18 17:38:52.898 Info: Client with IP ::ffff:192.168.xx.xx is calling "init".
06/16/18 17:38:52.899 Info: Adding server "binary://192.168.xx.xx".
06/16/18 17:38:52.899 Info: Calling init methods on server "binary://192.168.xx.xx".
06/16/18 17:38:52.903 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.xx.xx:60448 accepted. Client number: 17
06/16/18 17:38:52.904 RPC Server (Port 2001): Info: RPC server client id for client number 17 is: 2
06/16/18 17:38:52.905 RPC Server (Port 2001): Info: Client number 17 is calling RPC method: ping (2) Parameters:
(String) c28e855a
06/16/18 17:38:52.974 RPC Server (Port 2001): Info: Client number 17 is calling RPC method: getParamset (2) Parameters:
(String) OEQ1713396:0
(String) MASTER
06/16/18 17:38:53.004 RPC Server (Port 2001): Info: Client number 17 is calling RPC method: getParamset (2) Parameters:
(String) OEQ1713396:0
(String) VALUES
06/16/18 17:38:53.036 RPC Server (Port 2001): Info: Client number 17 is calling RPC method: getParamset (2) Parameters:
(String) OEQ1713396:4
(String) MASTER
06/16/18 17:38:53.039 RPC Server (Port 2001): Info: Client number 17 is calling RPC method: getParamset (2) Parameters:
(String) OEQ1713396:4
(String) VALUES
06/16/18 17:38:53.066 RPC Server (Port 2001): Info: Client number 17 is calling RPC method: getParamset (2) Parameters:
(String) OEQ1300941:0
(String) MASTER
06/16/18 17:38:53.070 RPC Server (Port 2001): Info: Client number 17 is calling RPC method: getParamset (2) Parameters:
(String) OEQ1300941:0
(String) VALUES
06/16/18 17:38:53.078 RPC Server (Port 2001): Info: Client number 17 is calling RPC method: getParamset (2) Parameters:
(String) OEQ1300941:1
(String) MASTER
06/16/18 17:38:53.081 RPC Server (Port 2001): Info: Client number 17 is calling RPC method: getParamset (2) Parameters:
(String) OEQ1300941:1
(String) VALUES
06/16/18 17:38:53.091 RPC Server (Port 2001): Info: Client number 17 is calling RPC method: getParamset (2) Parameters:
(String) OEQ1301294:0
(String) MASTER
06/16/18 17:38:53.094 RPC Server (Port 2001): Info: Client number 17 is calling RPC method: getParamset (2) Parameters:
(String) OEQ1301294:0
(String) VALUES
06/16/18 17:38:53.103 RPC Server (Port 2001): Info: Client number 17 is calling RPC method: getParamset (2) Parameters:
(String) OEQ1301294:1
(String) MASTER
06/16/18 17:38:53.106 RPC Server (Port 2001): Info: Client number 17 is calling RPC method: getParamset (2) Parameters:
(String) OEQ1301294:1
(String) VALUES
06/16/18 17:38:54.285 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No response received to packet: FD0003000003180A
06/16/18 17:38:54.286 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: Unknown packet received in response to init packet. Reconnecting...
06/16/18 17:38:55.856 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
06/16/18 17:38:57.857 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Connected to HM-MOD-RPI-PCB.
06/16/18 17:39:03.995 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No response received to packet: FD0003000003180A
06/16/18 17:39:03.995 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: Unknown packet received in response to init packet. Reconnecting...
06/16/18 17:39:05.571 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
06/16/18 17:39:07.572 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Connected to HM-MOD-RPI-PCB.
06/16/18 17:39:07.912 RPC Server (Port 2001): Info: Client number 17 is calling RPC method: ping (2) Parameters:
(String) c28e855a
06/16/18 17:39:13.709 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No response received to packet: FD0003000003180A
06/16/18 17:39:13.709 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: Unknown packet received in response to init packet. Reconnecting...
06/16/18 17:39:15.285 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
06/16/18 17:39:17.286 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Connected to HM-MOD-RPI-PCB.
06/16/18 17:39:22.916 RPC Server (Port 2001): Info: Client number 17 is calling RPC method: ping (2) Parameters:
(String) c28e855a
06/16/18 17:39:23.423 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No response received to packet: FD0003000003180A
06/16/18 17:39:23.424 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: Unknown packet received in response to init packet. Reconnecting...
06/16/18 17:39:24.999 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
06/16/18 17:39:27.000 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Connected to HM-MOD-RPI-PCB.
06/16/18 17:39:33.138 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No response received to packet: FD0003000003180A
06/16/18 17:39:33.138 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: Unknown packet received in response to init packet. Reconnecting...
06/16/18 17:39:34.713 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
06/16/18 17:39:36.714 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Connected to HM-MOD-RPI-PCB.
06/16/18 17:39:37.298 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.2.9:53673 accepted. Client number: 32
06/16/18 17:39:37.299 RPC Server (Port 2001): Info: RPC server client id for client number 32 is: 3
06/16/18 17:39:37.920 RPC Server (Port 2001): Info: Client number 17 is calling RPC method: ping (2) Parameters:
(String) c28e855a
06/16/18 17:39:42.852 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No response received to packet: FD0003000003180A
06/16/18 17:39:42.852 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: Unknown packet received in response to init packet. Reconnecting...
06/16/18 17:39:44.427 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
06/16/18 17:39:46.432 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Connected to HM-MOD-RPI-PCB.
06/16/18 17:39:52.570 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No response received to packet: FD0003000003180A
06/16/18 17:39:52.570 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: Unknown packet received in response to init packet. Reconnecting...
06/16/18 17:39:52.924 RPC Server (Port 2001): Info: Client number 17 is calling RPC method: ping (2) Parameters:
(String) c28e855a

tail -n 1000 -f /var/log/homegear/homegear.err

06/16/18 17:38:35.499 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.
06/16/18 17:38:35.499 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.
06/16/18 17:38:35.503 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.
06/16/18 17:38:44.576 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No response received to packet: FD0003000003180A
06/16/18 17:38:44.576 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: Unknown packet received in response to init packet. Reconnecting...
06/16/18 17:38:46.147 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
06/16/18 17:38:54.285 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No response received to packet: FD0003000003180A
06/16/18 17:38:54.286 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: Unknown packet received in response to init packet. Reconnecting...
06/16/18 17:38:55.857 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
06/16/18 17:39:03.995 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No response received to packet: FD0003000003180A
06/16/18 17:39:03.995 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: Unknown packet received in response to init packet. Reconnecting...
06/16/18 17:39:05.571 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
06/16/18 17:39:13.709 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No response received to packet: FD0003000003180A
06/16/18 17:39:13.710 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: Unknown packet received in response to init packet. Reconnecting...
06/16/18 17:39:15.285 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
06/16/18 17:39:23.424 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No response received to packet: FD0003000003180A
06/16/18 17:39:23.424 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: Unknown packet received in response to init packet. Reconnecting...
06/16/18 17:39:24.999 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
06/16/18 17:39:33.138 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No response received to packet: FD0003000003180A
06/16/18 17:39:33.138 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: Unknown packet received in response to init packet. Reconnecting...
06/16/18 17:39:34.713 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
06/16/18 17:39:42.852 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No response received to packet: FD0003000003180A
06/16/18 17:39:42.852 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: Unknown packet received in response to init packet. Reconnecting...
06/16/18 17:39:44.431 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
06/16/18 17:39:52.570 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No response received to packet: FD0003000003180A
06/16/18 17:39:52.570 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: Unknown packet received in response to init packet. Reconnecting...
06/16/18 17:39:54.146 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
06/16/18 17:40:02.284 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No response received to packet: FD0003000003180A
06/16/18 17:40:02.285 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: Unknown packet received in response to init packet. Reconnecting...
06/16/18 17:40:03.860 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
06/16/18 17:40:11.998 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No response received to packet: FD0003000003180A
06/16/18 17:40:11.999 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: Unknown packet received in response to init packet. Reconnecting...
06/16/18 17:40:13.574 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
06/16/18 17:40:21.713 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No response received to packet: FD0003000003180A
06/16/18 17:40:21.713 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: Unknown packet received in response to init packet. Reconnecting...
06/16/18 17:40:23.288 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
06/16/18 17:40:31.427 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No response received to packet: FD0003000003180A
06/16/18 17:40:31.427 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: Unknown packet received in response to init packet. Reconnecting...
06/16/18 17:40:33.002 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
06/16/18 17:40:41.141 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No response received to packet: FD0003000003180A
06/16/18 17:40:41.141 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: Unknown packet received in response to init packet. Reconnecting...
06/16/18 17:40:42.713 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
06/16/18 17:40:50.852 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No response received to packet: FD0003000003180A
06/16/18 17:40:50.852 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: Unknown packet received in response to init packet. Reconnecting...
06/16/18 17:40:52.425 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
06/16/18 17:41:00.563 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No response received to packet: FD0003000003180A
06/16/18 17:41:00.564 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: Unknown packet received in response to init packet. Reconnecting...
06/16/18 17:41:02.139 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
06/16/18 17:41:10.277 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No response received to packet: FD0003000003180A
06/16/18 17:41:10.278 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: Unknown packet received in response to init packet. Reconnecting...

Ich hoffe jemand kann mir da weiter helfen.
Vielen Dank schon mal.

Klaus

pmayer · June 16, 2018, 6:10pm

Hm,

habe leider selbst kein HM-MOD-RPI-PCB, aber kannst du mal schauen ob die aktuelle Firmware drauf ist?

Siehe: OpenHabian und Homegear auf Pi2 mit HM-MOD-RPI-PCB - GELÖST

TheBlueKL · June 16, 2018, 10:01pm

Die sollte drauf sein. Hatte ich schon gemacht.
Hab’s trotzdem nochmal gemacht…

[23:06:33] root@openHABianPi:/home/openhabian/hmcfgusb# ./flash-hmmoduart -U /dev/ttyAMA0 coprocessor_update.eq3
HM-MOD-UART flasher version 0.103-git

Reading firmware from coprocessor_update.eq3...
Firmware with 43 blocks successfully read.

Initializing HM-MOD-UART...
HM-MOD-UART opened.

Flashing 43 blocks: |

Firmware update successfull!
[23:07:31] root@openHABianPi:/home/openhabian/hmcfgusb#

Ich konnte dann einen Kontakt HM-Sec-SCo anlernen.

(Family)> ls
         ID │ Name                      │  Address │ Serial Number │ Type │ Type String               │ Firmware │ Config Pending │ Unreach │ Low Bat
────────────┼───────────────────────────┼──────────┼───────────────┼──────┼───────────────────────────┼──────────┼────────────────┼─────────┼────────
            │                           │          │               │      │                           │          │                │         │
          1 │                           │   613E03 │    OEQ1713396 │ 0095 │ HM-CC-RT-DN               │      1.4 │             No │      No │      No
          2 │                           │   5F0D7B │    OEQ1301294 │ 006A │ HM-LC-Bl1PBU-FM           │      2.B │             No │      No │      No
          3 │                           │   5F0ECE │    OEQ1300941 │ 006A │ HM-LC-Bl1PBU-FM           │      2.B │             No │      No │      No
          4 │                           │   5CF54B │    OEQ1432219 │ 00C7 │ HM-Sec-SCo                │      1.0 │             No │      No │      No
────────────┴───────────────────────────┴──────────┴───────────────┴──────┴───────────────────────────┴──────────┴────────────────┴─────────┴────────

Jetzt sieht die homegear.log anders aus…

06/16/18 23:30:38.679 (Shutdown) => Shutdown complete.
06/16/18 23:31:24.014 Starting Homegear...
06/16/18 23:31:24.014 Homegear version 0.7.19-1846
06/16/18 23:31:24.014 Git commit SHA of libhomegear-base: -
06/16/18 23:31:24.014 Git branch of libhomegear-base:     -
06/16/18 23:31:24.015 Git commit SHA of Homegear:         -
06/16/18 23:31:24.015 Git branch of Homegear:             -
06/16/18 23:31:24.017 Info: Setting allowed core file size to "4294967295" for user with id 0 and group with id 0.
06/16/18 23:31:24.017 Info: Core file size now is "4294967295".
06/16/18 23:31:24.017 Info: Setting maximum thread priority to "4294967295" for user with id 0 and group with id 0.
06/16/18 23:31:24.017 Info: Maximum thread priority now is "4294967295".
06/16/18 23:31:24.039 Info: Backing up database...
06/16/18 23:31:26.451 Initializing database...
06/16/18 23:31:26.461 Info: Loading family module mod_homematicbidcos.so
06/16/18 23:31:26.485 /etc/homegear/families/homematicbidcos.conf
06/16/18 23:31:26.488 Info: Loading family module mod_miscellaneous.so
06/16/18 23:31:26.494 /etc/homegear/families/miscellaneous.conf
06/16/18 23:31:26.495 Info: Loading family module mod_homematicwired.so
06/16/18 23:31:26.507 /etc/homegear/families/homematicwired.conf
06/16/18 23:31:26.508 Info: Setting up physical interfaces and GPIOs...
06/16/18 23:31:26.511 Info: Dropping privileges to user homegear (110) and group homegear (115)
06/16/18 23:31:26.512 Info: Homegear is (now) running as user with id 110 and group with id 115.
06/16/18 23:31:26.527 Starting script engine server...
06/16/18 23:31:26.537 Initializing licensing controller...
06/16/18 23:31:26.537 Loading licensing controller data...
06/16/18 23:31:26.537 Loading devices...
06/16/18 23:31:26.538 Loading XML RPC devices...
06/16/18 23:31:27.438 Loading device 1
06/16/18 23:31:27.438 Module HomeMatic BidCoS: Info: Central address set to 0xFD5D95.
06/16/18 23:31:27.439 Module HomeMatic BidCoS: Loading peer 1
06/16/18 23:31:27.457 Module HomeMatic BidCoS: Loading peer 2
06/16/18 23:31:27.500 Module HomeMatic BidCoS: Loading peer 3
06/16/18 23:31:27.511 Module HomeMatic BidCoS: Loading peer 4
06/16/18 23:31:27.514 Loading XML RPC devices...
06/16/18 23:31:27.565 Loading device 2
06/16/18 23:31:27.566 Loading XML RPC devices...
06/16/18 23:31:27.568 Loading device 3
06/16/18 23:31:27.569 Initializing RPC client...
06/16/18 23:31:27.569 Starting XML RPC server RPCServer1 listening on :::2001...
06/16/18 23:31:27.573 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.
06/16/18 23:31:27.573 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.
06/16/18 23:31:27.574 Starting XML RPC server RPCServer2 listening on :::2002, SSL enabled...
06/16/18 23:31:27.574 RPC Server (Port 2001): Info: RPC Server started listening on address :: and port 2001
06/16/18 23:31:27.578 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.
06/16/18 23:31:27.614 Starting XML RPC server RPCServer3 listening on :::2003, SSL enabled, authentication enabled...
06/16/18 23:31:27.615 RPC Server (Port 2002): Info: RPC Server started listening on address :: and port 2002
06/16/18 23:31:27.649 Starting CLI server...
06/16/18 23:31:27.649 RPC Server (Port 2003): Info: RPC Server started listening on address :: and port 2003
06/16/18 23:31:27.649 Initializing event handler...
06/16/18 23:31:27.650 Loading events...
06/16/18 23:31:27.651 Start listening for packets...
06/16/18 23:31:29.652 Starting Node-BLUE server...
06/16/18 23:31:29.662 Starting IPC server...
06/16/18 23:31:29.670 Startup complete. Waiting for physical interfaces to connect.
06/16/18 23:31:29.671 Info: Waiting for physical interfaces to connect (0 of 180s).
06/16/18 23:31:29.671 All physical interfaces are connected now.
06/16/18 23:31:29.671 Starting UPnP server...
06/16/18 23:31:29.673 Info: UPnP server: Binding to address: 192.168.2.51
06/16/18 23:31:29.673 UPnP Server: Info: Started listening.
06/16/18 23:31:32.090 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Info: Firmware version: 1.4.1
06/16/18 23:31:32.096 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Info: Serial number: PEQ0174929
06/16/18 23:31:32.110 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Info: Init queue completed. Sending peers...
06/16/18 23:31:32.333 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Info: Peer sending completed.
06/16/18 23:31:38.213 HomeMatic BidCoS packet received (My-HM-MOD-RPI-PCB, RSSI: -22 dBm): 0F5F8610613E030000000A24E50E0040
06/16/18 23:31:38.213 Module HomeMatic BidCoS: Info: ACTUAL_TEMPERATURE on channel 4 of HomeMatic BidCoS peer 1 with serial number OEQ1713396 was set to 0x00E5.
06/16/18 23:31:38.214 Module HomeMatic BidCoS: Info: BATTERY_STATE on channel 4 of HomeMatic BidCoS peer 1 with serial number OEQ1713396 was set to 0x0E.
06/16/18 23:31:38.214 Module HomeMatic BidCoS: Info: BOOST_STATE on channel 4 of HomeMatic BidCoS peer 1 with serial number OEQ1713396 was set to 0x00.
06/16/18 23:31:38.214 Module HomeMatic BidCoS: Info: CONTROL_MODE on channel 4 of HomeMatic BidCoS peer 1 with serial number OEQ1713396 was set to 0x01.
06/16/18 23:31:38.214 Module HomeMatic BidCoS: Info: FAULT_REPORTING on channel 4 of HomeMatic BidCoS peer 1 with serial number OEQ1713396 was set to 0x00.
06/16/18 23:31:38.235 Module HomeMatic BidCoS: Info: PARTY_START_TIME on channel 4 of HomeMatic BidCoS peer 1 with serial number OEQ1713396 was set to 0x00.
06/16/18 23:31:38.235 Module HomeMatic BidCoS: Info: VALVE_STATE on channel 4 of HomeMatic BidCoS peer 1 with serial number OEQ1713396 was set to 0x00.
06/16/18 23:31:40.186 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.2.51:57086 accepted. Client number: 13
06/16/18 23:31:40.187 RPC Server (Port 2001): Info: RPC server client id for client number 13 is: 0
06/16/18 23:31:40.189 RPC Server (Port 2001): Info: Client number 13 is calling RPC method: ping (2) Parameters:
(String) c28e855a
06/16/18 23:31:55.197 RPC Server (Port 2001): Info: Client number 13 is calling RPC method: init (2) Parameters:
(String) binary://192.168.2.51:9126
06/16/18 23:31:55.197 Info: Client with IP ::ffff:192.168.2.51 is calling "init".
06/16/18 23:31:55.210 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.2.51:57092 accepted. Client number: 14
06/16/18 23:31:55.211 RPC Server (Port 2001): Info: RPC server client id for client number 14 is: 1
06/16/18 23:31:55.212 RPC Server (Port 2001): Info: Client number 14 is calling RPC method: init (2) Parameters:
(String) binary://192.168.2.51:9126
(String) RF-c28e855a
(Integer) 34
06/16/18 23:31:55.213 Info: Client with IP ::ffff:192.168.2.51 is calling "init".
06/16/18 23:31:55.214 Info: Adding server "binary://192.168.2.51".
06/16/18 23:31:55.215 Info: Calling init methods on server "binary://192.168.2.51".
06/16/18 23:31:55.219 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.2.51:57094 accepted. Client number: 15
06/16/18 23:31:55.219 RPC Server (Port 2001): Info: RPC server client id for client number 15 is: 2
06/16/18 23:31:55.221 RPC Server (Port 2001): Info: Client number 15 is calling RPC method: ping (2) Parameters:
(String) c28e855a
06/16/18 23:31:55.255 RPC Server (Port 2001): Info: Client number 15 is calling RPC method: getAllSystemVariables (2) Parameters:
06/16/18 23:31:55.259 RPC Server (Port 2001): Info: Client number 15 is calling RPC method: getAllScripts (2) Parameters:
06/16/18 23:31:55.346 RPC Server (Port 2001): Info: Client number 15 is calling RPC method: getParamset (2) Parameters:
(String) OEQ1301294:0
(String) MASTER
06/16/18 23:31:55.350 RPC Server (Port 2001): Info: Client number 15 is calling RPC method: getParamset (2) Parameters:
(String) OEQ1301294:0
(String) VALUES
06/16/18 23:31:55.356 RPC Server (Port 2001): Info: Client number 15 is calling RPC method: getParamset (2) Parameters:
(String) OEQ1301294:1
(String) MASTER
06/16/18 23:31:55.359 RPC Server (Port 2001): Info: Client number 15 is calling RPC method: getParamset (2) Parameters:
(String) OEQ1301294:1
(String) VALUES
06/16/18 23:31:55.450 RPC Server (Port 2001): Info: Client number 15 is calling RPC method: getParamset (2) Parameters:
(String) OEQ1300941:0
(String) MASTER
06/16/18 23:31:55.454 RPC Server (Port 2001): Info: Client number 15 is calling RPC method: getParamset (2) Parameters:
(String) OEQ1300941:0
(String) VALUES
06/16/18 23:31:55.459 RPC Server (Port 2001): Info: Client number 15 is calling RPC method: getParamset (2) Parameters:
(String) OEQ1300941:1
(String) MASTER
06/16/18 23:31:55.463 RPC Server (Port 2001): Info: Client number 15 is calling RPC method: getParamset (2) Parameters:
(String) OEQ1300941:1
(String) VALUES
06/16/18 23:31:55.529 RPC Server (Port 2001): Info: Client number 15 is calling RPC method: getParamset (2) Parameters:
(String) OEQ1713396:0
(String) MASTER
06/16/18 23:31:55.540 RPC Server (Port 2001): Info: Client number 15 is calling RPC method: getParamset (2) Parameters:
(String) OEQ1713396:0
(String) VALUES
06/16/18 23:31:55.561 RPC Server (Port 2001): Info: Client number 15 is calling RPC method: getParamset (2) Parameters:
(String) OEQ1713396:4
(String) MASTER
06/16/18 23:31:55.564 RPC Server (Port 2001): Info: Client number 15 is calling RPC method: getParamset (2) Parameters:
(String) OEQ1713396:4
(String) VALUES
06/16/18 23:31:55.585 RPC Server (Port 2001): Info: Client number 15 is calling RPC method: getParamset (2) Parameters:
(String) OEQ1713396:1
(String) MASTER
06/16/18 23:31:55.588 RPC Server (Port 2001): Info: Client number 15 is calling RPC method: getParamset (2) Parameters:
(String) OEQ1713396:1
(String) VALUES
06/16/18 23:31:55.592 RPC Server (Port 2001): Info: Client number 15 is calling RPC method: getParamset (2) Parameters:
(String) OEQ1713396:2
(String) MASTER
06/16/18 23:31:55.595 RPC Server (Port 2001): Info: Client number 15 is calling RPC method: getParamset (2) Parameters:
(String) OEQ1713396:2
(String) VALUES
06/16/18 23:31:55.598 RPC Server (Port 2001): Info: Client number 15 is calling RPC method: getParamset (2) Parameters:
(String) OEQ1713396:3
(String) MASTER
06/16/18 23:31:55.601 RPC Server (Port 2001): Info: Client number 15 is calling RPC method: getParamset (2) Parameters:
(String) OEQ1713396:3
(String) VALUES
06/16/18 23:31:55.604 RPC Server (Port 2001): Info: Client number 15 is calling RPC method: getParamset (2) Parameters:
(String) OEQ1713396:5
(String) MASTER
06/16/18 23:31:55.607 RPC Server (Port 2001): Info: Client number 15 is calling RPC method: getParamset (2) Parameters:
(String) OEQ1713396:5
(String) VALUES
06/16/18 23:31:55.610 RPC Server (Port 2001): Info: Client number 15 is calling RPC method: getParamset (2) Parameters:
(String) OEQ1713396:6
(String) MASTER
06/16/18 23:31:55.613 RPC Server (Port 2001): Info: Client number 15 is calling RPC method: getParamset (2) Parameters:
(String) OEQ1713396:6
(String) VALUES
06/16/18 23:32:10.227 RPC Server (Port 2001): Info: Client number 15 is calling RPC method: ping (2) Parameters:
(String) c28e855a
06/16/18 23:32:25.231 RPC Server (Port 2001): Info: Client number 15 is calling RPC method: ping (2) Parameters:
(String) c28e855a
06/16/18 23:32:29.138 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.2.9:47005 accepted. Client number: 20
06/16/18 23:32:29.139 RPC Server (Port 2001): Info: RPC server client id for client number 20 is: 3
06/16/18 23:32:40.235 RPC Server (Port 2001): Info: Client number 15 is calling RPC method: ping (2) Parameters:
(String) c28e855a
06/16/18 23:32:55.239 RPC Server (Port 2001): Info: Client number 15 is calling RPC method: ping (2) Parameters:
(String) c28e855a
06/16/18 23:33:10.244 RPC Server (Port 2001): Info: Client number 15 is calling RPC method: ping (2) Parameters:
^C
[23:33:19] openhabian@openHABianPi:~$

Irgendwie komisch. Manchmal geht’s jetzt, dann reagiert es wieder nicht.

sathya · June 16, 2018, 10:41pm

Hallo @TheBlueKL,

der HM-MOD-RPI-PCB funktioniert jetzt generell. Welcher Art sind die Probleme jetzt? Was sind die Fehlermeldungen im Log jetzt? Es ist ganz, ganz wichtig, dass auf dem UART keine serielle Konsole läuft. Auch sollte der Hardware-UART verwendet werden (siehe Anleitung auf https://doc.homegear.eu).

Viele Grüße

Sathya

TheBlueKL · June 17, 2018, 11:40am

Der Raspi ist exakt nach den Anleitungen hier aufgesetzt und eingestellt.
BT umleitung dtoverlay=pi3-miniuart-bt, usw.
Im Moment sind die Homematic Things erkannt. Items angelegt…
HomematicIP wollen noch nicht peeren. Da bin ich noch dran.
Die Kommunikation via openHAB will jetzt nicht wirklich. Ich habe die Rolladenschalter zwar im “Wohnzimmer” sichtbar aber wenn ich bei Control da drauf klicke passiert nix.

Unter Rapberrymatic auf dem gleichen Pi ging das sofort. (andere SD Karte)

Aber was kann das sein, was sich da ständig Connected?
192.168.2.9 ist mein Qnap-NAS und hat mal nix mit Homematic und openHAB zu tun. Was für ein Dienst könnte da sein?

06/17/18 13:33:03.182 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.2.9:47402 accepted. Client number: 4679
06/17/18 13:33:03.182 RPC Server (Port 2001): Info: RPC server client id for client number 4679 is: 1118
06/17/18 13:33:16.355 RPC Server (Port 2001): Info: Client number 4630 is calling RPC method: ping (2) Parameters:
(String) c28e855a
06/17/18 13:33:31.359 RPC Server (Port 2001): Info: Client number 4630 is calling RPC method: ping (2) Parameters:
(String) c28e855a
06/17/18 13:33:46.363 RPC Server (Port 2001): Info: Client number 4630 is calling RPC method: ping (2) Parameters:
(String) c28e855a
06/17/18 13:34:01.367 RPC Server (Port 2001): Info: Client number 4630 is calling RPC method: ping (2) Parameters:
(String) c28e855a
06/17/18 13:34:03.195 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.2.9:49020 accepted. Client number: 4684
06/17/18 13:34:03.195 RPC Server (Port 2001): Info: RPC server client id for client number 4684 is: 1119
06/17/18 13:34:16.371 RPC Server (Port 2001): Info: Client number 4630 is calling RPC method: ping (2) Parameters:
(String) c28e855a
06/17/18 13:34:31.375 RPC Server (Port 2001): Info: Client number 4630 is calling RPC method: ping (2) Parameters:
(String) c28e855a
06/17/18 13:34:46.380 RPC Server (Port 2001): Info: Client number 4630 is calling RPC method: ping (2) Parameters:
(String) c28e855a
06/17/18 13:35:01.384 RPC Server (Port 2001): Info: Client number 4630 is calling RPC method: ping (2) Parameters:
(String) c28e855a
06/17/18 13:35:03.295 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.2.9:49704 accepted. Client number: 4689
06/17/18 13:35:03.296 RPC Server (Port 2001): Info: RPC server client id for client number 4689 is: 1120
06/17/18 13:35:16.388 RPC Server (Port 2001): Info: Client number 4630 is calling RPC method: ping (2) Parameters:
(String) c28e855a
06/17/18 13:35:31.393 RPC Server (Port 2001): Info: Client number 4630 is calling RPC method: ping (2) Parameters:
(String) c28e855a
06/17/18 13:35:46.397 RPC Server (Port 2001): Info: Client number 4630 is calling RPC method: ping (2) Parameters:
(String) c28e855a
06/17/18 13:36:01.430 RPC Server (Port 2001): Info: Client number 4630 is calling RPC method: ping (2) Parameters:
(String) c28e855a
06/17/18 13:36:03.204 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.2.9:50372 accepted. Client number: 4694
06/17/18 13:36:03.205 RPC Server (Port 2001): Info: RPC server client id for client number 4694 is: 1121
06/17/18 13:36:16.434 RPC Server (Port 2001): Info: Client number 4630 is calling RPC method: ping (2) Parameters:
(String) c28e855a
06/17/18 13:36:31.438 RPC Server (Port 2001): Info: Client number 4630 is calling RPC method: ping (2) Parameters:
(String) c28e855a
06/17/18 13:36:46.442 RPC Server (Port 2001): Info: Client number 4630 is calling RPC method: ping (2) Parameters:
(String) c28e855a
06/17/18 13:37:01.448 RPC Server (Port 2001): Info: Client number 4630 is calling RPC method: ping (2) Parameters:
(String) c28e855a
06/17/18 13:37:03.158 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.2.9:51026 accepted. Client number: 4699
06/17/18 13:37:03.158 RPC Server (Port 2001): Info: RPC server client id for client number 4699 is: 1122
06/17/18 13:37:16.452 RPC Server (Port 2001): Info: Client number 4630 is calling RPC method: ping (2) Parameters:
(String) c28e855a
06/17/18 13:37:31.456 RPC Server (Port 2001): Info: Client number 4630 is calling RPC method: ping (2) Parameters:
(String) c28e855a
06/17/18 13:37:46.459 RPC Server (Port 2001): Info: Client number 4630 is calling RPC method: ping (2) Parameters:
(String) c28e855a
06/17/18 13:38:01.463 RPC Server (Port 2001): Info: Client number 4630 is calling RPC method: ping (2) Parameters:
(String) c28e855a
06/17/18 13:38:03.180 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.2.9:51690 accepted. Client number: 4704

job · June 17, 2018, 1:59pm

Dir ist klar, dass das direkt mit Homegear, d.h. ohne CCU, nicht geht?

TheBlueKL · June 17, 2018, 6:16pm

Das ist ja doof. Geht das denn mit dem HmIP Accesspoint aus dem Starterset?
Oder geht das nur via YAHM als Untersatz für openHAB?
Was ich gelesen hab läuft die RaspMatic CCU2 Software nicht auf Debian…
Mein Ziel ist eigentlich via openHAB als Oberfläche auf alles zugreifen zu können und das auf nem RPi3 laufen zu haben.

pmayer · June 17, 2018, 7:51pm

Du kannst über https://github.com/Homegear/Homegear-CCU2 eine CCU2 (oder entsprechende Open-Source-Lösungen) anbinden und darüber HomematicIP an Homegear anbinden.

Dass das natürlich ein bisschen doppelt gemoppelt ist, ist mir klar. Aber aus rechtlichen Gründen kann Homegear aktuell kein HomematicIP einbinden…