Homegear "no response received to packet" on Raspi2 mit HM-MOD-RPI-PCB

Hallo!
Ich habe auf den Raspi2 nach anleitung von Homegear alles installiert und konfiguriert.
wenn ich homegear -r starte bekomme ich im log folgendes:

tail -f /var/log/homegear/homegear.log
01/19/17 22:35:30.818 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
01/19/17 22:35:33.328 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "HM-MOD-RPI-PCB": Connected to HM-MOD-RPI-PCB.
01/19/17 22:35:44.470 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "HM-MOD-RPI-PCB": Error: No response received to packet: FD0003000003180A
01/19/17 22:35:44.471 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "HM-MOD-RPI-PCB": Error: Unknown packet received in response to init packet. Reconnecting...
01/19/17 22:35:46.038 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
01/19/17 22:35:48.548 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "HM-MOD-RPI-PCB": Connected to HM-MOD-RPI-PCB.
01/19/17 22:35:59.686 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "HM-MOD-RPI-PCB": Error: No response received to packet: FD0003000003180A
01/19/17 22:35:59.687 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "HM-MOD-RPI-PCB": Error: Unknown packet received in response to init packet. Reconnecting...
01/19/17 22:36:01.258 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
01/19/17 22:36:03.768 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "HM-MOD-RPI-PCB": Connected to HM-MOD-RPI-PCB.

ich habe auf einer 2.SD rapsberrymatics installiert dort funktionert alles.ich kann ein gerät anlernen und wieder ablernen.

meine homematicbidcos.conf schaut wie folgt aus:

\########### HM-MOD-RPI-PCB  ##########

\## The device family this interface is for
[HomeMatic Wireless Module for Raspberry Pi]

\## Specify an unique id here to identify this device in Homegear
id = HM-MOD-RPI-PCB

\## When default is set to "true" Homegear will assign this device
\## to new peers.
default = true

\## Options: cul, cc1100, coc, cunx, hmcfglan, hmlgw, hm-mod-rpi-pcb
deviceType = hm-mod-rpi-pcb

device = /dev/ttyAMA0

\## Default: responseDelay = 95
\## Should be "95" for CUL or COC, "100" for TI CC1101 and "60" for HM-CFG-LAN or HM-LGW
responseDelay = 95

\## Default: gpio1 = 0
\## "18" for HM-MOD-RPI-PCB
gpio1 = 18

ich weiß es leider nicht mehr weiter und kann keine Geräte pairen.

Danke für eure Hilfe im Vorraus!!

Hi @raspicc,

leider habe ich kein HM-MOD-RPI-PCB. Ich nutze auf meinem RPi2 das homegear-Image mit CC1101-SPI, CUL und EnOcean USB 300.
Hast du die Bootoptionen entsprechend angepasst? https://doc.homegear.eu/data/homegear-homematicbidcos/configuration.html#homematic-wireless-module-for-raspberry-pi-hm-mod-rpi-pcb

Wichtig wenn du ein eigenes Raspbian installiert hast:

If you’re using the official Raspbian, you need to delete the file /etc/udev/rules.d/99-com.rules for Homegear to be able to access the GPIOs.

Hast du hier schon mal geschaut? Kein Empfang nach "no answer to packet"-Meldung - glaube das bezieht sich aber auf RPi3 wegen dem verbauten Bluetooth.

Du könntest mal das Debug Level auf 5 stellen und mal den Log-Teil vom Start von homegear posten, da wo das Modul initialisiert wird.

so long,
p

Hallo pmayer,
habe es genauso mit der Anleitung gemacht.

Habe den Debug level auf 5 gesetzt und bekomme folgendes nach dem Start von homegear:

01/20/17 16:24:50.648 RPC Server (Port 2002): Info: RPC Server started listening on address 0.0.0.0 and port 2002
01/20/17 16:24:50.691 Debug: GPIO 18 set to 1.
01/20/17 16:24:50.698 RPC Server (Port 2003): Info: RPC Server started listening on address 0.0.0.0 and port 2003
01/20/17 16:24:50.698 Starting CLI server…
01/20/17 16:24:50.700 Debug: Waiting for CLI client threads to finish.
01/20/17 16:24:50.701 Initializing event handler…
01/20/17 16:24:50.701 Loading events…
01/20/17 16:24:50.703 Startup complete. Waiting for physical interfaces to connect.
01/20/17 16:24:50.703 All physical interfaces are connected now.
01/20/17 16:24:50.703 Starting UPnP server…
01/20/17 16:24:50.706 Info: UPnP server: Binding to address: 192.168.1.103
01/20/17 16:24:50.707 UPnP Server: Info: Started listening.
01/20/17 16:24:51.590 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received. Raw data: FD000C000000436F5F4350555F424C7251
01/20/17 16:24:51.591 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received from HM-MOD-RPI-PCB: FD000C000000436F5F4350555F424C7251
01/20/17 16:24:51.767 Debug: SSDP server: Binding to address: 192.168.1.103
01/20/17 16:24:51.767 Debug: Searching for SSDP devices …
01/20/17 16:24:52.591 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Sending: FD0003000003180A
01/20/17 16:24:53.123 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received. Raw data: FD00040000040199
01/20/17 16:24:53.123 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received. Raw data: 3D
01/20/17 16:24:53.123 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received from HM-MOD-RPI-PCB: FD000400000401993D
01/20/17 16:24:53.157 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received. Raw data: FD0010FE01004475
01/20/17 16:24:53.158 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received. Raw data: 616C436F50726F5F
01/20/17 16:24:53.159 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received. Raw data: 417070B736
01/20/17 16:24:53.159 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received from HM-MOD-RPI-PCB: FD0010FE01004475616C436F50726F5F417070B736
01/20/17 16:25:02.592 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Error: No response received to packet: FD0003000003180A
01/20/17 16:25:02.592 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Error: Unknown packet received in response to init packet. Reconnecting…
01/20/17 16:25:04.169 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Warning: Connection closed (1). Trying to reconnect…
01/20/17 16:25:04.672 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Connecting to HM-MOD-RPI-PCB…
01/20/17 16:25:06.673 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Connected to HM-MOD-RPI-PCB.
01/20/17 16:25:06.674 Debug: GPIO 18 set to 0.
01/20/17 16:25:06.774 Debug: GPIO 18 set to 1.
01/20/17 16:25:06.810 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received. Raw data: FD000C000000436F
01/20/17 16:25:06.811 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received. Raw data: 5F4350555F424C72
01/20/17 16:25:06.811 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received. Raw data: 51
01/20/17 16:25:06.811 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received from HM-MOD-RPI-PCB: FD000C000000436F5F4350555F424C7251
01/20/17 16:25:07.812 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Sending: FD0003000003180A
01/20/17 16:25:08.343 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received. Raw data: FD00040000040199
01/20/17 16:25:08.343 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received. Raw data: 3D
01/20/17 16:25:08.343 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received from HM-MOD-RPI-PCB: FD000400000401993D
01/20/17 16:25:08.377 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received. Raw data: FD0010FE01004475
01/20/17 16:25:08.378 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received. Raw data: 616C436F50726F5F
01/20/17 16:25:08.379 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received. Raw data: 417070B736
01/20/17 16:25:08.379 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received from HM-MOD-RPI-PCB: FD0010FE01004475616C436F50726F5F417070B736
01/20/17 16:25:17.488 Debug: SSDP server: Binding to address: 192.168.1.103
01/20/17 16:25:17.488 Debug: Searching for SSDP devices …
01/20/17 16:25:17.812 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Error: No response received to packet: FD0003000003180A
01/20/17 16:25:17.813 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Error: Unknown packet received in response to init packet. Reconnecting…
01/20/17 16:25:19.390 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Warning: Connection closed (1). Trying to reconnect…
01/20/17 16:25:19.892 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Connecting to HM-MOD-RPI-PCB…
01/20/17 16:25:21.893 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Connected to HM-MOD-RPI-PCB.
01/20/17 16:25:21.894 Debug: GPIO 18 set to 0.
01/20/17 16:25:21.994 Debug: GPIO 18 set to 1.
01/20/17 16:25:22.030 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received. Raw data: FD000C000000436F
01/20/17 16:25:22.030 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received. Raw data: 5F4350555F424C72
01/20/17 16:25:22.031 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received. Raw data: 51
01/20/17 16:25:22.031 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received from HM-MOD-RPI-PCB: FD000C000000436F5F4350555F424C7251
01/20/17 16:25:23.032 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Sending: FD0003000003180A
01/20/17 16:25:23.563 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received. Raw data: FD00040000040199
01/20/17 16:25:23.563 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received. Raw data: 3D
01/20/17 16:25:23.563 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received from HM-MOD-RPI-PCB: FD000400000401993D
01/20/17 16:25:23.597 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received. Raw data: FD0010FE01004475
01/20/17 16:25:23.599 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received. Raw data: 616C436F50726F5F
01/20/17 16:25:23.599 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received. Raw data: 417070B736
01/20/17 16:25:23.600 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received from HM-MOD-RPI-PCB: FD0010FE01004475616C436F50726F5F417070B736
01/20/17 16:25:33.032 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Error: No response received to packet: FD0003000003180A
01/20/17 16:25:33.033 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Error: Unknown packet received in response to init packet. Reconnecting…
01/20/17 16:25:34.605 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Warning: Connection closed (1). Trying to reconnect…
01/20/17 16:25:35.112 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Connecting to HM-MOD-RPI-PCB…
01/20/17 16:25:37.113 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Connected to HM-MOD-RPI-PCB.
01/20/17 16:25:37.114 Debug: GPIO 18 set to 0.
01/20/17 16:25:37.214 Debug: GPIO 18 set to 1.
01/20/17 16:25:37.250 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received. Raw data: FD000C000000436F
01/20/17 16:25:37.250 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received. Raw data: 5F4350555F424C72
01/20/17 16:25:37.251 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received. Raw data: 51
01/20/17 16:25:37.251 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received from HM-MOD-RPI-PCB: FD000C000000436F5F4350555F424C7251
01/20/17 16:25:38.251 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Sending: FD0003000003180A
01/20/17 16:25:38.783 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received. Raw data: FD00040000040199
01/20/17 16:25:38.783 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received. Raw data: 3D
01/20/17 16:25:38.784 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received from HM-MOD-RPI-PCB: FD000400000401993D
01/20/17 16:25:38.817 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received. Raw data: FD0010FE01004475
01/20/17 16:25:38.818 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received. Raw data: 616C436F50726F5F
01/20/17 16:25:38.819 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received. Raw data: 417070B736
01/20/17 16:25:38.819 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received from HM-MOD-RPI-PCB: FD0010FE01004475616C436F50726F5F417070B736
01/20/17 16:25:43.203 Debug: SSDP server: Binding to address: 192.168.1.103
01/20/17 16:25:44.547 Debug: Searching for SSDP devices …
01/20/17 16:25:48.252 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Error: No response received to packet: FD0003000003180A
01/20/17 16:25:48.252 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Error: Unknown packet received in response to init packet. Reconnecting…
01/20/17 16:25:49.830 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Warning: Connection closed (1). Trying to reconnect…
01/20/17 16:25:50.332 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Connecting to HM-MOD-RPI-PCB…
01/20/17 16:25:50.409 UPnP Server: Debug: Sending notify packets.
01/20/17 16:25:52.333 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Connected to HM-MOD-RPI-PCB.
01/20/17 16:25:52.334 Debug: GPIO 18 set to 0.
01/20/17 16:25:52.434 Debug: GPIO 18 set to 1.
01/20/17 16:25:52.470 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received. Raw data: FD000C000000436F
01/20/17 16:25:52.470 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received. Raw data: 5F4350555F424C72
01/20/17 16:25:52.471 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received. Raw data: 51
01/20/17 16:25:52.471 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received from HM-MOD-RPI-PCB: FD000C000000436F5F4350555F424C7251
01/20/17 16:25:53.471 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Sending: FD0003000003180A
01/20/17 16:25:54.010 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received. Raw data: FD00040000040199
01/20/17 16:25:54.010 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received. Raw data: 3D
01/20/17 16:25:54.010 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received from HM-MOD-RPI-PCB: FD000400000401993D
01/20/17 16:25:54.044 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received. Raw data: FD0010FE01004475
01/20/17 16:25:54.045 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received. Raw data: 616C436F50726F5F
01/20/17 16:25:54.046 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received. Raw data: 417070B736
01/20/17 16:25:54.046 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received from HM-MOD-RPI-PCB: FD0010FE01004475616C436F50726F5F417070B736
01/20/17 16:26:03.479 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Error: No response received to packet: FD0003000003180A
01/20/17 16:26:03.479 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Error: Unknown packet received in response to init packet. Reconnecting…
01/20/17 16:26:05.052 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Warning: Connection closed (1). Trying to reconnect…
01/20/17 16:26:05.562 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Connecting to HM-MOD-RPI-PCB…
01/20/17 16:26:07.563 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Connected to HM-MOD-RPI-PCB.
01/20/17 16:26:07.564 Debug: GPIO 18 set to 0.
01/20/17 16:26:07.664 Debug: GPIO 18 set to 1.
01/20/17 16:26:07.700 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received. Raw data: FD000C000000436F
01/20/17 16:26:07.700 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received. Raw data: 5F4350555F424C72
01/20/17 16:26:07.701 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received. Raw data: 51
01/20/17 16:26:07.701 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received from HM-MOD-RPI-PCB: FD000C000000436F5F4350555F424C7251
01/20/17 16:26:08.701 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Sending: FD0003000003180A
01/20/17 16:26:09.233 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received. Raw data: FD00040000040199
01/20/17 16:26:09.233 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received. Raw data: 3D
01/20/17 16:26:09.233 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received from HM-MOD-RPI-PCB: FD000400000401993D
01/20/17 16:26:09.267 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received. Raw data: FD0010FE01004475
01/20/17 16:26:09.268 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received. Raw data: 616C436F50726F5F
01/20/17 16:26:09.269 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received. Raw data: 417070B736
01/20/17 16:26:09.269 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received from HM-MOD-RPI-PCB: FD0010FE01004475616C436F50726F5F417070B736
01/20/17 16:26:10.542 Debug: SSDP server: Binding to address: 192.168.1.103
01/20/17 16:26:10.542 Debug: Searching for SSDP devices …
01/20/17 16:26:18.702 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Error: No response received to packet: FD0003000003180A
01/20/17 16:26:18.702 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Error: Unknown packet received in response to init packet. Reconnecting…
01/20/17 16:26:20.280 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Warning: Connection closed (1). Trying to reconnect…
01/20/17 16:26:20.782 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Connecting to HM-MOD-RPI-PCB…
01/20/17 16:26:22.783 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Connected to HM-MOD-RPI-PCB.
01/20/17 16:26:22.784 Debug: GPIO 18 set to 0.
01/20/17 16:26:22.884 Debug: GPIO 18 set to 1.
01/20/17 16:26:22.920 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received. Raw data: FD000C000000436F
01/20/17 16:26:22.921 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received. Raw data: 5F4350555F424C72
01/20/17 16:26:22.921 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received. Raw data: 51
01/20/17 16:26:22.921 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received from HM-MOD-RPI-PCB: FD000C000000436F5F4350555F424C7251
01/20/17 16:26:23.921 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Sending: FD0003000003180A
01/20/17 16:26:24.453 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received. Raw data: FD00040000040199
01/20/17 16:26:24.453 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received. Raw data: 3D
01/20/17 16:26:24.453 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received from HM-MOD-RPI-PCB: FD000400000401993D
01/20/17 16:26:24.487 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received. Raw data: FD0010FE01004475
01/20/17 16:26:24.488 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received. Raw data: 616C436F50726F5F
01/20/17 16:26:24.489 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received. Raw data: 417070B736
01/20/17 16:26:24.490 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “HM-MOD-RPI-PCB”: Debug: Packet received from HM-MOD-RPI-PCB: FD0010FE01004475616C436F50726F5F417070B736

Vielleicht kann jemand damit anfangen.
Danke!
Lg

Hmmm… das sieht zumindest so aus als ob Homegear mit dem Modul sprechen kann, sonst würden ja keine Packets received.

@sathya, hast du ne Idee?

Hallo @raspicc,

das sieht für mich so aus, als würde die serielle Konsole dazwischenfunken. Stell noch einmal sicher, dass Bluetooth auf dem Mini-UART liegt (dtoverlay=pi3-miniuart-bt in /boot/config.txt), in /boot/cmdline.txt kein /dev/ttyAMA0 steht und die Dienste der seriellen Konsole deaktiviert sind:

systemctl disable serial-getty@ttyAMA0.service
systemctl disable serial-getty@serial0.service
systemctl disable serial-getty@ttyS0.service

Dann sollte es eigentlich klappen.

Viele Grüße

Sathya

Hallo zusammen,
ich habe das gleiche Problem unter der aktuellen Version von openHABian (1.4.1) und homegear (7.30) wie @raspicc.
Meine Logs sehen sehr ähnlich aus. Im Error-Log steht immer wieder, dass ein Paket nicht ankam oder dass eine CRC von einem Paket nicht passte.

10/24/18 11:39:39.690 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No response received to packet: FD0003000003180A
10/24/18 11:39:39.690 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: Unknown packet received in response to init packet. Reconnecting...
10/24/18 11:39:42.131 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...

Mit debuglevel 5 sehe ich, dass zwischendurch auch sauber Pakete ausgetauscht werden.

10/24/18 11:41:39.987 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Sending: FD0003000003180A
10/24/18 11:41:40.516 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: FD00040000040199
10/24/18 11:41:40.516 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 3D
10/24/18 11:41:40.517 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received from HM-MOD-RPI-PCB: FD000400000401993D
10/24/18 11:41:40.553 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: FD0010FE01004475
10/24/18 11:41:40.555 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 616C436F50726F5F
10/24/18 11:41:40.555 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 417070B736
10/24/18 11:41:40.556 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received from HM-MOD-RPI-PCB: FD0010FE01004475616C436F50726F5F417070B736

Pairing klappt aber trotzdem nicht.
Die config.txt und cmdline.txt sind angepasst, die Services deaktiviert, die .rules-Datei entfernt.

Habt ihr noch eine andere Idee? Zwischendurch kam das Thema Firmware-Version auf. Laut RaspberryMatic bin ich mit HM-MOD-RPI-PCB aber auf der aktuellen version (2.8.5)

Hallo @surfa,

poste mal das gesamte Log vom Homegearstart auf Loglevel 5.

Viele Grüße

Sathya

Hallo @sathya,
danke für deine Hilfe!
Anbei die Logs nach einem service homegear restart + Debuglevel auf 5

11/01/18 10:53:58.477 Starting Homegear...
11/01/18 10:53:58.477 Homegear version 0.7.30-1900
11/01/18 10:53:58.477 Git commit SHA of libhomegear-base: -
11/01/18 10:53:58.477 Git branch of libhomegear-base:     -
11/01/18 10:53:58.477 Git commit SHA of Homegear:         -
11/01/18 10:53:58.477 Git branch of Homegear:             -
11/01/18 10:53:58.478 Info: Setting allowed core file size to "4294967295" for user with id 0 and group with id 0.
11/01/18 10:53:58.478 Info: Core file size now is "4294967295".
11/01/18 10:53:58.478 Info: Setting maximum thread priority to "4294967295" for user with id 0 and group with id 0.
11/01/18 10:53:58.478 Info: Maximum thread priority now is "4294967295".
11/01/18 10:53:58.487 Info: Backing up database...
11/01/18 10:53:58.566 Initializing database...
11/01/18 10:53:58.571 Info: Loading family module mod_homematicbidcos.so
11/01/18 10:53:58.584 /etc/homegear/families/homematicbidcos.conf
11/01/18 10:53:58.586 Info: Loading family module mod_miscellaneous.so
11/01/18 10:53:58.589 /etc/homegear/families/miscellaneous.conf
11/01/18 10:53:58.590 Info: Loading family module mod_homematicwired.so
11/01/18 10:53:58.596 /etc/homegear/families/homematicwired.conf
11/01/18 10:53:58.596 Info: Setting up physical interfaces and GPIOs...
11/01/18 10:53:58.598 Info: Dropping privileges to user homegear (111) and group homegear (116)
11/01/18 10:53:58.598 Info: Homegear is (now) running as user with id 111 and group with id 116.
11/01/18 10:53:58.606 Starting script engine server...
11/01/18 10:53:58.614 Initializing licensing controller...
11/01/18 10:53:58.615 Loading licensing controller data...
11/01/18 10:53:58.615 Loading devices...
11/01/18 10:53:58.615 Loading XML RPC devices...
11/01/18 10:53:59.509 Loading device 1
11/01/18 10:53:59.509 Module HomeMatic BidCoS: Info: Central address set to 0xFDAA22.
11/01/18 10:53:59.510 Loading XML RPC devices...
11/01/18 10:53:59.560 Loading device 2
11/01/18 10:53:59.561 Loading XML RPC devices...
11/01/18 10:53:59.563 Loading device 3
11/01/18 10:53:59.564 Initializing RPC client...
11/01/18 10:53:59.564 Starting XML RPC server RPCServer1 listening on :::2001...
11/01/18 10:53:59.567 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.
11/01/18 10:53:59.567 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.
11/01/18 10:53:59.567 RPC Server (Port 2001): Info: Enabling session authentication for WebSockets.
11/01/18 10:53:59.568 Starting XML RPC server RPCServer2 listening on :::2002, SSL enabled...
11/01/18 10:53:59.568 RPC Server (Port 2001): Info: RPC Server started listening on address :: and port 2001
11/01/18 10:53:59.571 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.
11/01/18 10:53:59.571 RPC Server (Port 2002): Info: Enabling session authentication for WebSockets.
11/01/18 10:53:59.607 Starting XML RPC server RPCServer3 listening on :::2003, SSL enabled, authentication enabled...
11/01/18 10:53:59.607 RPC Server (Port 2002): Info: RPC Server started listening on address :: and port 2002
11/01/18 10:53:59.611 RPC Server (Port 2003): Info: Enabling basic authentication.
11/01/18 10:53:59.611 RPC Server (Port 2003): Info: Enabling client certificate authentication.
11/01/18 10:53:59.611 RPC Server (Port 2003): Info: Enabling session authentication for WebSockets.
11/01/18 10:53:59.641 Initializing event handler...
11/01/18 10:53:59.641 Loading events...
11/01/18 10:53:59.642 Start listening for packets...
11/01/18 10:54:01.643 Starting Node-BLUE server...
11/01/18 10:54:01.652 Starting IPC server...
11/01/18 10:54:01.660 Startup complete. Waiting for physical interfaces to connect.
11/01/18 10:54:01.660 Info: Waiting for physical interfaces to connect (0 of 180s).
11/01/18 10:54:01.660 All physical interfaces are connected now.
11/01/18 10:54:01.660 Starting UPnP server...
11/01/18 10:54:01.662 Info: UPnP server: Binding to address: 192.168.178.42
11/01/18 10:54:01.663 UPnP Server: Info: Started listening.
11/01/18 10:54:01.926 IPC Server: Info: Connection accepted. Client number: 11
11/01/18 10:54:01.926 IPC Server: Info: Client 0 successfully registered RPC method "cliOutput" (this method is registered by 1 client(s)).
11/01/18 10:54:01.927 IPC Server: Info: Client 0 successfully registered RPC method "cliOutput-0" (this method is registered by 1 client(s)).
11/01/18 10:54:04.933 IPC Server: Response: 
(String) Debug level set to 5.

11/01/18 10:54:06.851 IPC Server: Info: Connection to IPC server's client number 11 closed.
11/01/18 10:54:08.643 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No response received to packet: FD0003000003180A
11/01/18 10:54:08.650 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: Unknown packet received in response to init packet. Reconnecting...
11/01/18 10:54:10.213 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
11/01/18 10:54:10.214 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Connecting to HM-MOD-RPI-PCB...
11/01/18 10:54:12.215 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Connected to HM-MOD-RPI-PCB.
11/01/18 10:54:12.215 Debug: GPIO 18 set to 0.
11/01/18 10:54:12.315 Debug: GPIO 18 set to 1.
11/01/18 10:54:12.351 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: FD000C000000436F
11/01/18 10:54:12.352 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 5F4350555F424C72
11/01/18 10:54:12.352 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 51
11/01/18 10:54:12.352 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received from HM-MOD-RPI-PCB: FD000C000000436F5F4350555F424C7251
11/01/18 10:54:13.352 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Sending: FD0003000003180A
11/01/18 10:54:13.483 RPC Server (Port 2001): Info: Connection from ::ffff:127.0.0.1:33650 accepted. Client number: 14
11/01/18 10:54:13.483 RPC Server (Port 2001): Info: RPC server client id for client number 14 is: 0
11/01/18 10:54:13.485 RPC Server (Port 2001): Listening for incoming packets from client number 14.
11/01/18 10:54:13.485 RPC Server (Port 2001): Debug: Packet received: 42696E000000001C0000000470696E670000000100000003000000083865393265626262
11/01/18 10:54:13.485 RPC Server (Port 2001): Info: Client number 14 is calling RPC method: ping (2) Parameters:
(String) 8e92ebbb
11/01/18 10:54:13.485 RPC Server (Port 2001): Response: 
(Boolean) 1
11/01/18 10:54:13.485 RPC Server (Port 2001): Response binary:
42696E01000000050000000201
11/01/18 10:54:13.882 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: FD00040000040199
11/01/18 10:54:13.883 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 3D
11/01/18 10:54:13.887 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received from HM-MOD-RPI-PCB: FD000400000401993D
11/01/18 10:54:13.916 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: FD0010FE01004475
11/01/18 10:54:13.917 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 616C436F50726F5F
11/01/18 10:54:13.918 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 417070B736
11/01/18 10:54:13.918 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received from HM-MOD-RPI-PCB: FD0010FE01004475616C436F50726F5F417070B736
11/01/18 10:54:15.335 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: FD001003000505A0
11/01/18 10:54:15.336 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 003050A03F64CDA5
11/01/18 10:54:15.337 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 59E2C15D5D
11/01/18 10:54:15.337 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received from HM-MOD-RPI-PCB: FD001003000505A0003050A03F64CDA559E2C15D5D
11/01/18 10:54:18.353 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No response received to packet: FD0003000003180A
11/01/18 10:54:18.353 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: Unknown packet received in response to init packet. Reconnecting...
11/01/18 10:54:21.339 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
11/01/18 10:54:21.340 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Connecting to HM-MOD-RPI-PCB...
11/01/18 10:54:23.340 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Connected to HM-MOD-RPI-PCB.
11/01/18 10:54:23.341 Debug: GPIO 18 set to 0.
11/01/18 10:54:23.441 Debug: GPIO 18 set to 1.
11/01/18 10:54:23.477 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: FD000C000000436F
11/01/18 10:54:23.477 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 5F4350555F424C72
11/01/18 10:54:23.478 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 51
11/01/18 10:54:23.478 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received from HM-MOD-RPI-PCB: FD000C000000436F5F4350555F424C7251
11/01/18 10:54:24.478 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Sending: FD0003000003180A
11/01/18 10:54:25.008 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: FD00040000040199
11/01/18 10:54:25.008 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 3D
11/01/18 10:54:25.008 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received from HM-MOD-RPI-PCB: FD000400000401993D
11/01/18 10:54:25.041 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: FD0010FE01004475
11/01/18 10:54:25.042 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 616C436F50726F5F
11/01/18 10:54:25.043 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 417070B736
11/01/18 10:54:25.043 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received from HM-MOD-RPI-PCB: FD0010FE01004475616C436F50726F5F417070B736
11/01/18 10:54:28.489 RPC Server (Port 2001): Debug: Packet received: 42696E000000002B00000004696E697400000001000000030000001762696E6172793A2F2F6C6F63616C686F73743A39313236
11/01/18 10:54:28.489 RPC Server (Port 2001): Info: Client number 14 is calling RPC method: init (2) Parameters:
(String) binary://localhost:9126
11/01/18 10:54:28.490 Info: Client with IP ::ffff:127.0.0.1 is calling "init".
11/01/18 10:54:28.490 RPC Server (Port 2001): Response: 
(void)
11/01/18 10:54:28.490 RPC Server (Port 2001): Response binary:
42696E01000000080000000300000000
11/01/18 10:54:28.493 RPC Server (Port 2001): Debug: Connection to client number 14 closed (3).
11/01/18 10:54:28.496 RPC Server (Port 2001): Info: Connection from ::ffff:127.0.0.1:33652 accepted. Client number: 17
11/01/18 10:54:28.497 RPC Server (Port 2001): Info: RPC server client id for client number 17 is: 1
11/01/18 10:54:28.498 RPC Server (Port 2001): Listening for incoming packets from client number 17.
11/01/18 10:54:28.498 RPC Server (Port 2001): Debug: Packet received: 42696E000000004600000004696E697400000003000000030000001762696E6172793A2F2F6C6F63616C686F73743A39313236000000030000000B52462D38653932656262620000000100000022
11/01/18 10:54:28.498 RPC Server (Port 2001): Info: Client number 17 is calling RPC method: init (2) Parameters:
(String) binary://localhost:9126
(String) RF-8e92ebbb
(Integer) 34
11/01/18 10:54:28.499 Info: Client with IP ::ffff:127.0.0.1 is calling "init".
11/01/18 10:54:28.499 Info: Adding server "binary://localhost".
11/01/18 10:54:28.500 RPC Server (Port 2001): Response: 
(void)
11/01/18 10:54:28.500 Info: Calling init methods on server "binary://localhost".
11/01/18 10:54:28.500 RPC Server (Port 2001): Response binary:
42696E01000000080000000300000000
11/01/18 10:54:28.503 RPC Server (Port 2001): Debug: Connection to client number 17 closed (3).
11/01/18 10:54:28.504 RPC Server (Port 2001): Info: Connection from ::ffff:127.0.0.1:33654 accepted. Client number: 18
11/01/18 10:54:28.505 RPC Server (Port 2001): Info: RPC server client id for client number 18 is: 2
11/01/18 10:54:28.506 RPC Server (Port 2001): Listening for incoming packets from client number 18.
11/01/18 10:54:28.506 RPC Server (Port 2001): Debug: Packet received: 42696E000000001C0000000470696E670000000100000003000000083865393265626262
11/01/18 10:54:28.506 RPC Server (Port 2001): Info: Client number 18 is calling RPC method: ping (2) Parameters:
(String) 8e92ebbb
11/01/18 10:54:28.507 RPC client: Debug: Calling RPC method "system.multicall" on server localhost.
11/01/18 10:54:28.507 RPC client: Parameters:
11/01/18 10:54:28.507 RPC Server (Port 2001): Response: 
(Boolean) 1
11/01/18 10:54:28.507 RPC Server (Port 2001): Response binary:
42696E01000000050000000201
(Array length=1)
{
  (Struct length=2)
  {
    [methodName]
    {
      (String) event
    }
    [params]
    {
      (Array length=4)
      {
        (String) RF-8e92ebbb
        (String) CENTRAL
        (String) PONG
        (String) 8e92ebbb
      }
    }
  }
}
11/01/18 10:54:28.507 Debug: Calling getFileDescriptor...
11/01/18 10:54:28.507 Debug: Connecting to host localhost on port 9126...
11/01/18 10:54:28.510 Debug: Connected to host localhost on port 9126. Client number is: 19
11/01/18 10:54:28.510 RPC client: Debug: Sending packet: 42696E00000000930000001073797374656D2E6D756C746963616C6C00000001000001000000000100000101000000020000000A6D6574686F644E616D6500000003000000056576656E7400000006706172616D730000010000000004000000030000000B52462D3865393265626262000000030000000743454E5452414C0000000300000004504F4E4700000003000000083865393265626262
11/01/18 10:54:28.558 RPC client: Debug: Packet received: 42696E0100000015000001000000000100000003000000056576656E74
11/01/18 10:54:28.558 RPC client: Debug: Received packet from server localhost: 42696E0100000015000001000000000100000003000000056576656E74
11/01/18 10:54:28.558 RPC client: Response was:
(Array length=1)
{
  (String) event
}
11/01/18 10:54:29.000 RPC client: Debug: Calling RPC method "system.listMethods" on server localhost.
11/01/18 10:54:29.000 RPC client: Parameters:
11/01/18 10:54:29.000 Debug: Calling getFileDescriptor...
11/01/18 10:54:29.000 Debug: Connecting to host localhost on port 9126...
11/01/18 10:54:29.001 Debug: Connected to host localhost on port 9126. Client number is: 20
11/01/18 10:54:29.001 RPC client: Debug: Sending packet: 42696E000000001A0000001273797374656D2E6C6973744D6574686F647300000000
11/01/18 10:54:29.003 RPC client: Debug: Packet received: 42696E01000000540000010000000004000000030000001073797374656D2E6D756C746963616C6C00000003000000056576656E74000000030000000D64656C65746544657669636573000000030000000A6E657744657669636573
11/01/18 10:54:29.003 RPC client: Debug: Received packet from server localhost: 42696E01000000540000010000000004000000030000001073797374656D2E6D756C746963616C6C00000003000000056576656E74000000030000000D64656C65746544657669636573000000030000000A6E657744657669636573
11/01/18 10:54:29.003 RPC client: Response was:
(Array length=4)
{
  (String) system.multicall
  (String) event
  (String) deleteDevices
  (String) newDevices
}
11/01/18 10:54:29.004 Debug: Adding method system.multicall
11/01/18 10:54:29.004 Debug: Adding method event
11/01/18 10:54:29.004 Debug: Adding method deleteDevices
11/01/18 10:54:29.004 Debug: Adding method newDevices
11/01/18 10:54:29.478 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No response received to packet: FD0003000003180A
11/01/18 10:54:29.479 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: Unknown packet received in response to init packet. Reconnecting...
11/01/18 10:54:31.048 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
11/01/18 10:54:31.049 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Connecting to HM-MOD-RPI-PCB...
11/01/18 10:54:33.049 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Connected to HM-MOD-RPI-PCB.
11/01/18 10:54:33.050 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: FD00160301051E4F0038C186105F9C210000000A88C40C00008B6A
11/01/18 10:54:33.050 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received from HM-MOD-RPI-PCB: FD00160301051E4F0038C186105F9C210000000A88C40C00008B6A
11/01/18 10:54:33.050 Debug: GPIO 18 set to 0.
11/01/18 10:54:33.150 Debug: GPIO 18 set to 1.
11/01/18 10:54:33.186 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: FD000C000000436F
11/01/18 10:54:33.186 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 5F4350555F424C72
11/01/18 10:54:33.187 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 51
11/01/18 10:54:33.187 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received from HM-MOD-RPI-PCB: FD000C000000436F5F4350555F424C7251
11/01/18 10:54:34.187 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Sending: FD0003000003180A
11/01/18 10:54:34.717 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: FD00040000040199
11/01/18 10:54:34.717 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 3D
11/01/18 10:54:34.717 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received from HM-MOD-RPI-PCB: FD000400000401993D
11/01/18 10:54:34.750 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: FD0010FE01004475
11/01/18 10:54:34.751 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 616C436F50726F5F
11/01/18 10:54:34.752 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 417070B736
11/01/18 10:54:34.753 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received from HM-MOD-RPI-PCB: FD0010FE01004475616C436F50726F5F417070B736
11/01/18 10:54:39.188 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No response received to packet: FD0003000003180A
11/01/18 10:54:39.188 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: Unknown packet received in response to init packet. Reconnecting...
11/01/18 10:54:40.758 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
11/01/18 10:54:40.758 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Connecting to HM-MOD-RPI-PCB...
11/01/18 10:54:42.759 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Connected to HM-MOD-RPI-PCB.
11/01/18 10:54:42.759 Debug: GPIO 18 set to 0.
11/01/18 10:54:42.859 Debug: GPIO 18 set to 1.
11/01/18 10:54:42.895 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: FD000C000000436F
11/01/18 10:54:42.896 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 5F4350555F424C72
11/01/18 10:54:42.896 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 51
11/01/18 10:54:42.896 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received from HM-MOD-RPI-PCB: FD000C000000436F5F4350555F424C7251
11/01/18 10:54:43.516 RPC Server (Port 2001): Debug: Packet received: 42696E000000001C0000000470696E670000000100000003000000083865393265626262
11/01/18 10:54:43.517 RPC Server (Port 2001): Info: Client number 18 is calling RPC method: ping (2) Parameters:
(String) 8e92ebbb
11/01/18 10:54:43.517 RPC Server (Port 2001): Response: 
(Boolean) 1
11/01/18 10:54:43.517 RPC client: Debug: Calling RPC method "system.multicall" on server localhost.
11/01/18 10:54:43.517 RPC client: Parameters:
11/01/18 10:54:43.517 RPC Server (Port 2001): Response binary:
42696E01000000050000000201
(Array length=1)
{
  (Struct length=2)
  {
    [methodName]
    {
      (String) event
    }
    [params]
    {
      (Array length=4)
      {
        (String) RF-8e92ebbb
        (String) CENTRAL
        (String) PONG
        (String) 8e92ebbb
      }
    }
  }
}
11/01/18 10:54:43.517 Debug: Calling getFileDescriptor...
11/01/18 10:54:43.517 Debug: Connecting to host localhost on port 9126...
11/01/18 10:54:43.518 Debug: Connected to host localhost on port 9126. Client number is: 25
11/01/18 10:54:43.519 RPC client: Debug: Sending packet: 42696E00000000930000001073797374656D2E6D756C746963616C6C00000001000001000000000100000101000000020000000A6D6574686F644E616D6500000003000000056576656E7400000006706172616D730000010000000004000000030000000B52462D3865393265626262000000030000000743454E5452414C0000000300000004504F4E4700000003000000083865393265626262
11/01/18 10:54:43.523 RPC client: Debug: Packet received: 42696E0100000015000001000000000100000003000000056576656E74
11/01/18 10:54:43.523 RPC client: Debug: Received packet from server localhost: 42696E0100000015000001000000000100000003000000056576656E74
11/01/18 10:54:43.523 RPC client: Response was:
(Array length=1)
{
  (String) event
}
11/01/18 10:54:43.896 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Sending: FD0003000003180A
11/01/18 10:54:44.426 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: FD00040000040199
11/01/18 10:54:44.427 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 3D
11/01/18 10:54:44.427 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received from HM-MOD-RPI-PCB: FD000400000401993D
11/01/18 10:54:44.459 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: FD0010FE01004475
11/01/18 10:54:44.461 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 616C436F50726F5F
11/01/18 10:54:44.461 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 417070B736
11/01/18 10:54:44.462 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received from HM-MOD-RPI-PCB: FD0010FE01004475616C436F50726F5F417070B736
11/01/18 10:54:45.047 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: FD0013030005025A
11/01/18 10:54:45.048 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 000067865A6336F5
11/01/18 10:54:45.049 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 00000088C431BEC9
11/01/18 10:54:45.049 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received from HM-MOD-RPI-PCB: FD0013030005025A000067865A6336F500000088C431BEC9
11/01/18 10:54:45.335 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: FD0010030105037C
11/01/18 10:54:45.336 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 002E52A03F64CDA5
11/01/18 10:54:45.337 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 59E2C135C7
11/01/18 10:54:45.337 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received from HM-MOD-RPI-PCB: FD0010030105037C002E52A03F64CDA559E2C135C7
11/01/18 10:54:48.897 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No response received to packet: FD0003000003180A
11/01/18 10:54:48.897 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: Unknown packet received in response to init packet. Reconnecting...
11/01/18 10:54:51.342 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
11/01/18 10:54:51.343 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Connecting to HM-MOD-RPI-PCB...
11/01/18 10:54:53.343 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Connected to HM-MOD-RPI-PCB.
11/01/18 10:54:53.344 Debug: GPIO 18 set to 0.
11/01/18 10:54:53.444 Debug: GPIO 18 set to 1.
11/01/18 10:54:53.479 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: FD000C000000436F
11/01/18 10:54:53.480 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 5F4350555F424C72
11/01/18 10:54:53.480 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 51
11/01/18 10:54:53.480 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received from HM-MOD-RPI-PCB: FD000C000000436F5F4350555F424C7251
11/01/18 10:54:54.481 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Sending: FD0003000003180A
11/01/18 10:54:55.011 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: FD00040000040199
11/01/18 10:54:55.011 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 3D
11/01/18 10:54:55.011 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received from HM-MOD-RPI-PCB: FD000400000401993D
11/01/18 10:54:55.044 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: FD0010FE01004475
11/01/18 10:54:55.045 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 616C436F50726F5F
11/01/18 10:54:55.046 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 417070B736
11/01/18 10:54:55.046 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received from HM-MOD-RPI-PCB: FD0010FE01004475616C436F50726F5F417070B736
11/01/18 10:54:58.521 RPC Server (Port 2001): Debug: Packet received: 42696E000000001C0000000470696E670000000100000003000000083865393265626262
11/01/18 10:54:58.521 RPC Server (Port 2001): Info: Client number 18 is calling RPC method: ping (2) Parameters:
(String) 8e92ebbb
11/01/18 10:54:58.521 RPC Server (Port 2001): Response: 
(Boolean) 1
11/01/18 10:54:58.521 RPC client: Debug: Calling RPC method "system.multicall" on server localhost.
11/01/18 10:54:58.521 RPC client: Parameters:
11/01/18 10:54:58.521 RPC Server (Port 2001): Response binary:
42696E01000000050000000201
(Array length=1)
{
  (Struct length=2)
  {
    [methodName]
    {
      (String) event
    }
    [params]
    {
      (Array length=4)
      {
        (String) RF-8e92ebbb
        (String) CENTRAL
        (String) PONG
        (String) 8e92ebbb
      }
    }
  }
}
11/01/18 10:54:58.522 Debug: Calling getFileDescriptor...
11/01/18 10:54:58.522 Debug: Connecting to host localhost on port 9126...
11/01/18 10:54:58.523 Debug: Connected to host localhost on port 9126. Client number is: 28
11/01/18 10:54:58.523 RPC client: Debug: Sending packet: 42696E00000000930000001073797374656D2E6D756C746963616C6C00000001000001000000000100000101000000020000000A6D6574686F644E616D6500000003000000056576656E7400000006706172616D730000010000000004000000030000000B52462D3865393265626262000000030000000743454E5452414C0000000300000004504F4E4700000003000000083865393265626262
11/01/18 10:54:58.525 RPC client: Debug: Packet received: 42696E0100000015000001000000000100000003000000056576656E74
11/01/18 10:54:58.526 RPC client: Debug: Received packet from server localhost: 42696E0100000015000001000000000100000003000000056576656E74
11/01/18 10:54:58.526 RPC client: Response was:
(Array length=1)
{
  (String) event
}
11/01/18 10:54:59.481 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No response received to packet: FD0003000003180A
11/01/18 10:54:59.481 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: Unknown packet received in response to init packet. Reconnecting...
11/01/18 10:54:59.746 RPC Server (Port 2001): Debug: Joining read thread of client 0
11/01/18 10:54:59.747 RPC Server (Port 2001): Debug: Client 0 removed.
11/01/18 10:54:59.747 RPC Server (Port 2001): Debug: Joining read thread of client 1
11/01/18 10:54:59.747 RPC Server (Port 2001): Debug: Client 1 removed.
11/01/18 10:55:01.051 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
11/01/18 10:55:01.052 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Connecting to HM-MOD-RPI-PCB...
11/01/18 10:55:01.061 UPnP Server: Debug: Sending notify packets.
11/01/18 10:55:01.827 IPC Server: Info: IPC client 0 removed.
11/01/18 10:55:03.052 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Connected to HM-MOD-RPI-PCB.
11/01/18 10:55:03.053 Debug: GPIO 18 set to 0.
11/01/18 10:55:03.153 Debug: GPIO 18 set to 1.
11/01/18 10:55:03.188 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: FD000C000000436F
11/01/18 10:55:03.189 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 5F4350555F424C72
11/01/18 10:55:03.189 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 51
11/01/18 10:55:03.190 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received from HM-MOD-RPI-PCB: FD000C000000436F5F4350555F424C7251
11/01/18 10:55:04.190 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Sending: FD0003000003180A

Mir kam heute morgen noch ein Gedanke: Es wird immer davon gesprochen, dass Firmware 1.4 funktioniert. Vielleicht wurde in einer späteren Firmware etwas verändert, was Probleme erzeugt (mein Modul ist auf 2.8.5)

Viele Grüße
surfa

Bei dir ist die Dual-Firmware drauf (HomeMatic IP plus HomeMatic BidCoS). Die geht nicht ohne Weiteres in normalen Linux-Installationen (es sind Kernel-Patches erforderlich). Installier eine Single-Firmware, dann wird es funktionieren.

Viele Grüße

Sathya

1 Like

Hi @sathya,
danke für den Hinweis. Ich habe Geräte von Homematic und von Homematic IP im Einsatz. Laut https://homegear.eu/ wird beides unterstützt. Kann ich beide Komponenten-Arten mit der 1.4er Firmware nutzen oder geht dann nur noch Homematic BidCos?
Viele Grüße
surfa

Homegear unterstützt aktuell HomematicIP NUR über die CCU2…

Hi, das Thema ist ja schon ein paar Tage älter. Gibt es dazu vielleicht Neuigkeiten oder ist es immernoch nur möglich Homematic IP mit Homegear über die CCU2 zu steuern? Wie sieht es mit Raspberrymatic, kann ich damit und dem HM-MOD-* die IP Geräte steuern?
Lg

Hey @Chrasonier,

Immer noch nur über homegear-ccu.

Womit du die CCU realisierst ist egal. Du kannst durchaus eine vCCU/oCCU/Raspberrymatic parallel zu homegear auf dem selben Pi betreiben.
Für HomematicIP benötigt das HM-MOD-RPI-PCB allerdings die aktuellste Firmware womit es dann micht mehr mit homegear-homematicbidcos funktioniert. Ist ja dann aber nicht schlimm, weil das ja die vCCU übernehmen kann.