Config Pending

Deutsche Foren Allgemein
#1

Guten Abend,

ich habe das Problem, dass mein einer Fenstersensor im Config Pending hängen bleibt.
Ich wollte ihn nun auf factory resetten… auch da passiert nichts und er bleibt hängen. Hier der Log. Ich weiß nicht so ganz was ich nun noch machen kann.

10/31/19 09:56:35.454 RPC Server (Port 2002): Warning: TLS handshake has failed: A TLS fatal alert has been received.

10/31/19 09:56:36.076 RPC Server (Port 2002): Warning: TLS handshake has failed: A TLS fatal alert has been received.

10/31/19 09:56:37.207 RPC Server (Port 2002): Error: Broken pipe

10/31/19 09:56:38.892 RPC Server (Port 2002): Warning: TLS handshake has failed: A TLS fatal alert has been received.

10/31/19 09:56:42.791 RPC Server (Port 2002): Warning: TLS handshake has failed: A TLS fatal alert has been received.

10/31/19 09:56:42.822 RPC Server (Port 2002): Warning: TLS handshake has failed: A TLS fatal alert has been received.

10/31/19 09:56:53.952 Error: No AES key is defined for the key index to set. You probably changed rfKey before the last key was sent to the device or you forgot to set oldRfKey. Please set oldRfKey in homematicbidcos.conf to the current AES key of the peer or reset the peer and pair it again.

10/31/19 09:56:54.140 RPC Server (Port 2002): Warning: TLS handshake has failed: A TLS fatal alert has been received.

10/31/19 09:56:54.173 RPC Server (Port 2002): Warning: TLS handshake has failed: A TLS fatal alert has been received.

10/31/19 09:56:54.206 RPC Server (Port 2002): Warning: TLS handshake has failed: A TLS fatal alert has been received.

10/31/19 09:56:54.261 RPC Server (Port 2002): Warning: TLS handshake has failed: A TLS fatal alert has been received.

10/31/19 10:50:56.260 Error: No AES key is defined for the key index to set. You probably changed rfKey before the last key was sent to the device or you forgot to set oldRfKey. Please set oldRfKey in homematicbidcos.conf to the current AES key of the peer or reset the peer and pair it again.

10/31/19 11:51:54.868 Error: No AES key is defined for the key index to set. You probably changed rfKey before the last key was sent to the device or you forgot to set oldRfKey. Please set oldRfKey in homematicbidcos.conf to the current AES key of the peer or reset the peer and pair it again.

10/31/19 12:51:22.173 Error: No AES key is defined for the key index to set. You probably changed rfKey before the last key was sent to the device or you forgot to set oldRfKey. Please set oldRfKey in homematicbidcos.conf to the current AES key of the peer or reset the peer and pair it again.

10/31/19 13:50:03.732 Error: No AES key is defined for the key index to set. You probably changed rfKey before the last key was sent to the device or you forgot to set oldRfKey. Please set oldRfKey in homematicbidcos.conf to the current AES key of the peer or reset the peer and pair it again.

10/31/19 14:49:33.184 Error: No AES key is defined for the key index to set. You probably changed rfKey before the last key was sent to the device or you forgot to set oldRfKey. Please set oldRfKey in homematicbidcos.conf to the current AES key of the peer or reset the peer and pair it again.

10/31/19 15:50:46.094 Error: No AES key is defined for the key index to set. You probably changed rfKey before the last key was sent to the device or you forgot to set oldRfKey. Please set oldRfKey in homematicbidcos.conf to the current AES key of the peer or reset the peer and pair it again.

10/31/19 16:43:08.835 Error: No AES key is defined for the key index to set. You probably changed rfKey before the last key was sent to the device or you forgot to set oldRfKey. Please set oldRfKey in homematicbidcos.conf to the current AES key of the peer or reset the peer and pair it again.

10/31/19 16:56:36.369 Module HomeMatic BidCoS: Error: Peer deletion took too long.

10/31/19 16:56:36.401 Module HomeMatic BidCoS: Error: Packet was processed more than 5 seconds after reception. If your CPU and network load is low, please report this to the Homegear developers.

10/31/19 16:56:36.403 Module HomeMatic BidCoS: Error: Packet was processed more than 5 seconds after reception. If your CPU and network load is low, please report this to the Homegear developers.

10/31/19 16:56:36.415 Module HomeMatic BidCoS: Error: Packet was processed more than 5 seconds after reception. If your CPU and network load is low, please report this to the Homegear developers.

10/31/19 16:56:36.424 Module HomeMatic BidCoS: Error: Packet was processed more than 5 seconds after reception. If your CPU and network load is low, please report this to the Homegear developers.

10/31/19 16:56:36.424 Module HomeMatic BidCoS: Error: Packet was processed more than 5 seconds after reception. If your CPU and network load is low, please report this to the Homegear developers.
#2

Zeig mal deine homematicbidcos.conf… natürlich mit entfremdeten AES-Key.

#3

Ich habe an den ganzen AES Settings nichts geändert. Ich habe lediglich den nightly installiert und den stable per apt removed und gepurged.

---------------------------- 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 = 0xFD23BA

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

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

#######################################

################# CUL #################

#######################################

## The device family this interface is for

[CUL]

## Specify an unique id here to identify this device in Homegear

id = My-CUL

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

device = /dev/ttyACM0

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

#######################################

### 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.100

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

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

#######################################

############# HM-CFG-LAN #############

#######################################

## The device family this interface is for

#[HM-CFG-LAN]

## Specify an unique id here to identify this device in Homegear

#id = My-HM-CFG-LAN

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

## IP address of your HM-CFG-LAN

#host = 192.168.178.100

## Port number your HM-CFG-LAN listens on. Normally 1000.

#port = 1000

## Put the AES key printed on your HM-CFG-LAN here

#lanKey = 00112233445566778899AABBCCDDEEFF

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

#######################################

######### COC, SCC, CSM, CCD #########

#######################################

## The device family this interface is for

#[COC, SCC, CSM, CCD]

## Specify an unique id here to identify this device in Homegear

#id = My-COC

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

## Also use "coc" for SCC, CCD and CSM

#deviceType = coc

#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

## "17" for COC, SCC and CCD. Empty for CSM.

#gpio1 = 17

## Default: gpio2 = 0

## "18" for COC and SCC. "22" for CCD. Empty for CSM.

#gpio2 = 18

## Default: stackPosition = 0 (= no stacking)

## Set stackPosition if you use the SCC and stacked multiple devices.

## Set stackPosition to "1" for the lowest device, to "2" for the device

## above that and so on.

# stackPosition = 0

#######################################

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

#######################################

################ CUNX ################

#######################################

## The device family this interface is for

#[CUNX]

## Specify an unique id here to identify this device in Homegear

#id = My-CUNX

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

## IP address of your CUNO

#host = 192.168.178.100

## Port number your CUNX listens on. Normally 2323.

#port = 2323

## Default: responseDelay = 95

## Should be "93" for CUNX

#responseDelay = 93

#######################################

########## TI CC1101 Module ##########

#######################################

## The device family this interface is for

#[TI CC1101 Module]

## Specify an unique id here to identify this device in Homegear

#id = My-CC1101

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

#device = /dev/spidev0.0

## Default: responseDelay = 95

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

#responseDelay = 100

## The interrupt pin to use. "0" for GDO0 or "2" for GDO2.

## You only need to connect one of them. Specify the GPIO

## you connected the interrupt pin to below.

#interruptPin = 2

## The GPIO GDO0 or GDO2 is connected to. Specify which GDO to use above.

#gpio1 = 24

### Additional TI CC1190 Config ###

## The GPIO high gain mode of the CC1190 is connected to.

## Default: -1 (disabled)

#gpio2 = 5

## The hexadecimal value for the PATABLE of the TI CC1101.

## Default:

## - Without high gain mode: 0xC2

## - With high gain mode: 0x27 (maximum legally allowed setting)

#txPowerSetting = 0x27

# vim: filetype=cfg
#4

Besteht dein AES key evtl nicht nur aus 0-9 und A-F?

Ansonsten sieht das für mich gut aus…

#5

Leider ist der AES Key korrekt.
Wie kann ich denn die Homematic Geräte factory-resetten? Ohne Homegear?

#6

Das steht in der Anleitung des Gerätes… bei gleichem AES Key kannst du sie in jedem Fall neu anlernen.

#7

Hallo @MaxBec,

der AES-Schlüssel in Homegear ist nicht der, welcher im Gerät eingespeichert ist bzw. der Index stimmt nicht. Wenn nur letzteres der Fall ist, kannst du currentRfKeyIndex so lange inkrementieren, bis die Fehlermeldung im Log verschwindet. Falls der Schlüssel falsch sit, wüsste keinen Weg, das Gerät in den Werkszustand zu versetzen.

Viele Grüße

Sathya