Hi wie der Titel schon aussagt möchte ich Homegear mit Openhab2 betreiben.
Ich bekomme aber das HM-MOD-RPI-PCB nicht ans laufen.
Hab mit an die Offizelle Anleitung gehalten aber irgendwas scheint nicht richtig zu Arbeiten.
Wenn ich das Modul unter Raspberrymatic betreibe gibt es keine Probelme.
hier der Log
08/27/17 11:36:11.656 Starting CLI server...
08/27/17 11:36:11.656 RPC Server (Port 2003): Info: RPC Server started listening on address :: and port 2003
08/27/17 11:36:11.656 Initializing event handler...
08/27/17 11:36:11.660 Loading events...
08/27/17 11:36:11.661 Starting flows server...
08/27/17 11:36:11.667 Starting IPC server...
08/27/17 11:36:11.669 Start listening for packets...
08/27/17 11:36:13.672 Startup complete. Waiting for physical interfaces to connect.
08/27/17 11:36:13.672 All physical interfaces are connected now.
08/27/17 11:36:13.672 Starting UPnP server...
08/27/17 11:36:13.675 Info: UPnP server: Binding to address: 192.168.10.124
08/27/17 11:36:13.675 UPnP Server: Info: Started listening.
08/27/17 11:36:13.679 Error: A core file exists in Homegear's working directory ("/var/lib/homegear/core"). Please send this file to the Homegear team including information about your system (Linux distribution, CPU architecture), the Homegear version, the current log files and information what might've caused the error.
08/27/17 11:36:16.680 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.10.119:60981 accepted. Client number: 12
08/27/17 11:36:16.680 RPC Server (Port 2001): Info: RPC server client id for client number 12 is: 0
08/27/17 11:36:16.684 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.10.120:38468 accepted. Client number: 13
08/27/17 11:36:16.685 RPC Server (Port 2001): Info: RPC server client id for client number 13 is: 1
08/27/17 11:36:18.623 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.10.122:54769 accepted. Client number: 14
08/27/17 11:36:18.624 RPC Server (Port 2001): Info: RPC server client id for client number 14 is: 2
08/27/17 11:36:20.672 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No response received to packet: FD0003000003180A
08/27/17 11:36:20.673 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: Unknown packet received in response to init packet. Reconnecting...
08/27/17 11:36:22.247 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
08/27/17 11:36:24.248 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Connected to HM-MOD-RPI-PCB.
08/27/17 11:36:30.387 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No response received to packet: FD0003000003180A
08/27/17 11:36:30.387 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: Unknown packet received in response to init packet. Reconnecting...
08/27/17 11:36:31.961 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
08/27/17 11:36:33.963 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Connected to HM-MOD-RPI-PCB.
08/27/17 11:36:40.101 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No response received to packet: FD0003000003180A
08/27/17 11:36:40.101 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: Unknown packet received in response to init packet. Reconnecting...
08/27/17 11:36:41.676 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
08/27/17 11:36:43.677 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Connected to HM-MOD-RPI-PCB.
08/27/17 11:36:49.815 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No response received to packet: FD0003000003180A
08/27/17 11:36:49.816 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: Unknown packet received in response to init packet. Reconnecting...
08/27/17 11:36:51.385 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
08/27/17 11:36:53.386 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Connected to HM-MOD-RPI-PCB.
08/27/17 11:36:59.524 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No response received to packet: FD0003000003180A
08/27/17 11:36:59.525 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: Unknown packet received in response to init packet. Reconnecting...
08/27/17 11:37:00.054 RPC Server (Port 2001): Info: Connection from ::ffff:127.0.0.1:39404 accepted. Client number: 23
08/27/17 11:37:00.055 RPC Server (Port 2001): Info: RPC server client id for client number 23 is: 3
08/27/17 11:37:00.767 RPC Server (Port 2001): Info: Client number 23 is calling RPC method: getDeviceDescription (1) Parameters:
(String) BidCoS-RF
08/27/17 11:37:00.907 RPC Server (Port 2001): Info: Connection from ::ffff:127.0.0.1:39410 accepted. Client number: 24
08/27/17 11:37:00.908 RPC Server (Port 2001): Info: RPC server client id for client number 24 is: 4
08/27/17 11:37:00.913 RPC Server (Port 2001): Info: Client number 24 is calling RPC method: listBidcosInterfaces (1) Parameters:
08/27/17 11:37:01.098 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
08/27/17 11:37:01.300 RPC Server (Port 2001): Info: Connection from ::ffff:127.0.0.1:39426 accepted. Client number: 26
08/27/17 11:37:01.301 RPC Server (Port 2001): Info: RPC server client id for client number 26 is: 5
08/27/17 11:37:01.303 RPC Server (Port 2001): Info: Client number 26 is calling RPC method: init (2) Parameters:
(String) binary://192.168.10.124:9126
(String) RF-a7f9461a