Hallo zusammen
Nach einem Update von 0.6.7-1480 auf 0.6.20-987 kann ich meine Rolladenaktoren (HM-LC-BI1PBU-FM) nicht mehr ansteuern (RasPi 3 mit Jessie).
Des weiteren ist kein Anlernen von irgendwelchen neuen HomeMatic Geräten mehr möglich (habe es mit Fenstersensor HM-Sec-SCo, Taster HM-PB-2-WM55-2 und Rolladenaktor HM-LC-BI1PBU-FM probiert).
Wenn ich wieder auf das alte System (Backup vor Update) zurückgehe, ist An- und Ablernen problemlos möglich.
Nachdem ich die “centralAddress” kurzfristig gesetzt hatte (um zu testen, ob es vielleicht damit zu tun hat), habe ich jetzt zusätzlich das Problem, dass jeder Tastendruck eines Tasters 3 Mal im log auftaucht und auch 3 Mal in OpenHAB ankommt. Sehr häßlich 
Weiß da jemand, wie ich das wieder zum Laufen bekomme?
Besten Dank schonmal,
Dirk
Die homematicbidcos.conf ist identisch in beiden Versionen:
#######################################
########## 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
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 = My-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.178.22
## 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 = xxxxxxx [hier steht der Key des LGW]
## 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.
sendFix = false
Ach ja, das log-file während des Anlernvorgangs sieht folgendermaßen aus:
05/06/17 00:56:11.607 RPC Server (Port 2001): Info: Client number 369 is calling RPC method: getInstallMode (2) Parameters:
05/06/17 00:56:12.122 RPC Server (Port 2001): Info: Client number 369 is calling RPC method: getInstallMode (2) Parameters:
05/06/17 00:56:12.621 RPC Server (Port 2001): Info: Client number 369 is calling RPC method: getInstallMode (2) Parameters:
05/06/17 00:56:13.138 RPC Server (Port 2001): Info: Client number 369 is calling RPC method: getInstallMode (2) Parameters:
05/06/17 00:56:13.652 RPC Server (Port 2001): Info: Client number 369 is calling RPC method: getInstallMode (2) Parameters:
05/06/17 00:56:14.133 HomeMatic BidCoS packet received (My-HM-LGW, RSSI: -44 dBm): 1A04840043488E0000001000C74D45513137323631363280810101
05/06/17 00:56:14.134 Module HomeMatic BidCoS: Info: Pushing pending queues.
05/06/17 00:56:14.170 RPC Server (Port 2001): Info: Client number 369 is calling RPC method: getInstallMode (2) Parameters:
05/06/17 00:56:14.192 HM-LGW "My-HM-LGW": Info: Sending (My-HM-LGW): 1030A001FD000143488E00050000000000
05/06/17 00:56:14.685 RPC Server (Port 2001): Info: Client number 369 is calling RPC method: getInstallMode (2) Parameters:
05/06/17 00:56:14.781 HM-LGW "My-HM-LGW": Info: No answer to packet 1030A001FD000143488E00050000000000
05/06/17 00:56:15.199 RPC Server (Port 2001): Info: Client number 369 is calling RPC method: getInstallMode (2) Parameters:
05/06/17 00:56:15.714 RPC Server (Port 2001): Info: Client number 369 is calling RPC method: getInstallMode (2) Parameters:
05/06/17 00:56:16.214 RPC Server (Port 2001): Info: Client number 369 is calling RPC method: getInstallMode (2) Parameters:
05/06/17 00:56:16.728 RPC Server (Port 2001): Info: Client number 369 is calling RPC method: getInstallMode (2) Parameters:
05/06/17 00:56:17.227 RPC Server (Port 2001): Info: Client number 369 is calling RPC method: getInstallMode (2) Parameters:
05/06/17 00:56:17.735 RPC Server (Port 2001): Info: Client number 369 is calling RPC method: getInstallMode (2) Parameters:
05/06/17 00:56:18.018 RPC Server (Port 2001): Info: Client number 369 is calling RPC method: clientServerInitialized (2) Parameters:
(String) HomegearLib.192.168.178.27:9876
05/06/17 00:56:18.252 RPC Server (Port 2001): Info: Client number 369 is calling RPC method: getInstallMode (2) Parameters:
05/06/17 00:56:18.767 RPC Server (Port 2001): Info: Client number 369 is calling RPC method: getInstallMode (2) Parameters:
Habe gerade zu allem Überfluss noch bemerkt, dass auch die Fensterkontakte nicht mehr funktionieren:
05/06/17 01:06:39.201 HomeMatic BidCoS packet received (My-HM-LGW, RSSI: -56 dBm): 0DE4A6103D0DB9FD00F006010000
05/06/17 01:06:39.201 RPC client: Info: Calling RPC method "system.multicall" on server 192.168.178.30.
05/06/17 01:06:39.203 Info: Ignoring broadcast packet from peer 18 to other peer, because AES handshakes are enabled for this peer.
05/06/17 01:06:39.203 RPC client: Info: Calling RPC method "system.multicall" on server 192.168.178.27.
05/06/17 01:06:39.473 HomeMatic BidCoS packet received (My-HM-LGW, RSSI: -56 dBm): 0DE5A6103D0DB9FD00F006010000
05/06/17 01:06:39.473 Info: Ignoring broadcast packet from peer 18 to other peer, because AES handshakes are enabled for this peer.
05/06/17 01:06:40.031 HomeMatic BidCoS packet received (My-HM-LGW, RSSI: -58 dBm): 0DE6A6103D0DB9FD00F006010000
05/06/17 01:06:40.032 Info: Ignoring broadcast packet from peer 18 to other peer, because AES handshakes are enabled for this peer.
05/06/17 01:06:40.347 HomeMatic BidCoS packet received (My-HM-LGW, RSSI: -74 dBm): 0C65B6413D0D4336BFF30180C8
05/06/17 01:06:40.348 RPC client: Info: Calling RPC method "system.multicall" on server 192.168.178.27.
05/06/17 01:06:40.348 Info: Ignoring broadcast packet from peer 30 to other peer, because AES handshakes are enabled for this peer.
05/06/17 01:06:40.349 RPC client: Info: Calling RPC method "system.multicall" on server 192.168.178.30.