rfKey HM-LGW - "No init packet received" - Kein Pairing möglich

Hallo zusammen,

in meiner Log Datei taucht nach dem Start von Homegear folgende Meldung auf:

09/02/17 15:11:30.536 Starting Homegear...
09/02/17 15:11:30.536 Homegear version 0.7.8-1314
09/02/17 15:11:30.537 Git commit SHA of libhomegear-base: -
09/02/17 15:11:30.537 Git branch of libhomegear-base:     -
09/02/17 15:11:30.537 Git commit SHA of Homegear:         -
09/02/17 15:11:30.537 Git branch of Homegear:             -
09/02/17 15:11:30.539 Info: Setting allowed core file size to "4294967295" for user with id 0 and 
group with id 0.
09/02/17 15:11:30.540 Info: Core file size now is "4294967295".
09/02/17 15:11:30.540 Info: Setting maximum thread priority to "4294967295" for user with id 0 
and group with id 0.
09/02/17 15:11:30.540 Info: Maximum thread priority now is "4294967295".
09/02/17 15:11:30.551 Info: Backing up database...
09/02/17 15:11:31.003 Initializing database...
09/02/17 15:11:31.007 Info: Loading family module mod_homematicbidcos.so
09/02/17 15:11:31.019 /etc/homegear/families/homematicbidcos.conf
09/02/17 15:11:31.021 Info: Loading family module mod_intertechno.so
09/02/17 15:11:31.025 /etc/homegear/families/intertechno.conf
09/02/17 15:11:31.026 Info: Loading family module mod_miscellaneous.so
09/02/17 15:11:31.030 /etc/homegear/families/miscellaneous.conf
09/02/17 15:11:31.030 Info: Loading family module mod_enocean.so
09/02/17 15:11:31.035 /etc/homegear/families/enocean.conf
09/02/17 15:11:31.036 Info: Setting up physical interfaces and GPIOs...
09/02/17 15:11:31.037 Info: Dropping privileges to user homegear (112) and group homegear 
(118)
09/02/17 15:11:31.037 Info: Homegear is (now) running as user with id 112 and group with id 
118.
09/02/17 15:11:31.043 Starting script engine server...
09/02/17 15:11:31.047 Initializing licensing controller...
09/02/17 15:11:31.047 Loading licensing controller data...
09/02/17 15:11:31.047 Loading devices...
09/02/17 15:11:31.047 Loading XML RPC devices...
09/02/17 15:11:32.258 Loading device 2
09/02/17 15:11:32.259 Module HomeMatic BidCoS: Info: Central address set to 0xFD0001.
09/02/17 15:11:32.260 Info: Not initializing device family EnOcean, because no physical 
interface was found.
09/02/17 15:11:32.260 Info: Disposing family module mod_enocean.so
09/02/17 15:11:32.261 Info: Not initializing device family Intertechno, because no physical 
interface was found.
09/02/17 15:11:32.261 Info: Disposing family module mod_intertechno.so
09/02/17 15:11:32.261 Loading XML RPC devices...
09/02/17 15:11:32.264 Loading device 1
09/02/17 15:11:32.264 Initializing RPC client...
09/02/17 15:11:32.265 Starting XML RPC server RPCServer1 listening on :::2001...
09/02/17 15:11:32.267 Starting XML RPC server RPCServer2 listening on :::2002, SSL 
enabled...
09/02/17 15:11:32.268 RPC Server (Port 2001): Info: RPC Server started listening on address :: 
and port 2001
09/02/17 15:11:32.300 Starting XML RPC server RPCServer3 listening on :::2003, SSL enabled, 
authentication enabled...
09/02/17 15:11:32.300 RPC Server (Port 2002): Info: RPC Server started listening on address :: 
and port 2002
09/02/17 15:11:32.332 Starting CLI server...
09/02/17 15:11:32.332 RPC Server (Port 2003): Info: RPC Server started listening on address :: 
and port 2003
09/02/17 15:11:32.333 Initializing event handler...
09/02/17 15:11:32.333 Loading events...
09/02/17 15:11:32.334 Starting flows server...
09/02/17 15:11:32.341 Starting IPC server...
09/02/17 15:11:32.342 Start listening for packets...
09/02/17 15:11:32.343 Startup complete. Waiting for physical interfaces to connect.
09/02/17 15:11:32.343 All physical interfaces are connected now.
09/02/17 15:11:32.343 Starting UPnP server...
09/02/17 15:11:32.345 Info: UPnP server: Binding to address: 192.168.13.13
09/02/17 15:11:32.345 UPnP Server: Info: Started listening.
09/02/17 15:11:33.350 HM-LGW "HM-LGW": Warning: Too large packet received: 
356C2810261C03CDDCF484200D2EF40CA530E1BC17DB5BD444
09/02/17 15:11:33.351 HM-LGW "HM-LGW": Error: First packet does not start with "S" or has 
wrong structure. Please check your AES key in homematicbidcos.conf. Stopping listening.
09/02/17 15:12:02.343 HM-LGW "HM-LGW": Error: No init packet received.

Irgendwas scheint also mit meinem rfKey nicht zu stimmen. Ansonsten sieht der Start eigentlich gut aus. Ich kann mich mit Homegear verbinden und auch die Homematic Family auswählen.

sudo homegear -r
families select 0

Zum Test habe ich nun eins meiner HomeMatic Thermostate in den Werkzustand zurück versetzt. Nachdem ich mittels

pon

das HM-LGW und anschließend das Thermostat in den Anlernzustand versetzt habe, passiert gar nichts. Das Thermostat wird nicht erkannt. Ich habe auch noch mal die eq3 Konfigurationssoftware benutzt. Auch hier funktioniert das Anlernen nicht, wenn ich mich mit der Software per Homegear verbinde.

Hier ist meine homematicbidcos.conf

---------------------------- HomeMatic BidCoS  ----------------------------
___________________________________________________________________________

#######################################
########## General Settings  ##########
#######################################

[General]

## The BidCoS address of Homegear. It is recommended to change this to a random 3 byte hexadecimal
## value starting with 0xFD (e. g. 0xFD43AB). Only change this, when no HomeMatic BidCoS devices
## are paired to Homegear as existing pairings will not work anymore!
centralAddress = 0xFD0001

## Specify a 16 byte (32 characters) long AES key here to protect your wireless communication
## !!! IMPORTANT: It is highly recommended to change this key before pairing the first device.
## !!! IMPORTANT: Never ever lose this key. That would render your devices useless.
## To remove the key from your devices, you need to factory reset them using Homegear. The factory
## reset on the device is not possible!!!
rfKey = Hier steht ein 32stelliger Code
#rfKey = 00112233445566778899AABBCCDDEEFF

## With each key change currentRFKeyIndex needs to be
## incremented by 1
currentRfKeyIndex = 1

## When you change rfKey, put the old key here. To change the key Homegear needs to know the
## old and the new one.
## !!! Do not set oldRFKey when you set rfKey for the first time !!!
##oldRFKey = 00112233445566778899AABBCCDDEEFF

## When set to "true" unsigned broadcast packets are processed by Homegear. This could enable an
## attacker to make Homegear do things, you don't want. That means, this option is a security
## risk.
processBroadcastWithAesEnabled = false

#######################################
### HomeMatic Wireless LAN Gateway  ###
#######################################

## The device family this interface is for
[HomeMatic Wireless LAN Gateway]

## Specify an unique id here to identify this device in Homegear
id = HM-LGW

## 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 = hmlgw

## IP address of your HM-LGW
host = 192.168.13.12

## First Port number your HM-LGW listens on. Normally 2000.
port = 2000

## Keep alive port number your HM-LGW listens on. Normally 2001.
portKeepAlive = 2001

## Put the security key printed on your HM-LGW here
lanKey = Code, welcher auf dem LGW hinten aufgedruckt ist

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

## Default: sendFix = false
## Some LAN-Gateways do not send packets correctly. If sent packets are not received by the
## devices (you get error messages, that packets were not received after 3 retries), set
## sendFix to true.
## Note that the behavior of sendFix changed in version 0.6.13. If you had it set to true,
## set it to false now and the other way around.
sendFix = true

Wäre super, wenn mich jemand in die richtige Richtung schubsen könnte :wink:

Ich habe es jetzt mal mit meinem alten HM CFG LAN versucht. Da hat es auf Anhieb funktioniert und alle meine Devices ließen sich nach einem Reset mit Homegear pairen.