HM-CFG-LAN kein pairing

Hallo zusammen

Ich bin soweit, das ich um euren Rat bitte, da ich es nicht schaffe einen gebrauchten HM-CFG-LAN Adapter homegear bekannt zu machen.

Ich habe auf einem raspi (IP=192.168.1.8) openhab und homegear installiert und versuche einen “gebraucht” gekauften HM-CFG-LAN (IP=192.168.1.174) zu pairen.

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

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

#######################################
############# 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 = 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.1.174

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

## Put the AES key printed on your HM-CFG-LAN here
#lanKey = 18D37F11C12D9C2446E870824D70A14E

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

Mittels homegear -r

fs 0
paring on

und anschliessend gedrückten “Reset-Knopf” in der Mitte vom HM-CFG-LAN bekomme ich kein pairing zustande

homegear.log:

03/08/16 19:04:45.685 Starting Homegear...
03/08/16 19:04:45.686 Homegear version 0.6.0-1244
03/08/16 19:04:45.686 Git commit SHA of libhomegear-base: 953dea2f53a78e28b5e6e65d5e564e7ba92592e1
03/08/16 19:04:45.687 Git commit SHA of Homegear:         1cef456dae99d0c591dd6f62b3b5f0f34b1628e4
03/08/16 19:04:45.666 Starting Homegear...
03/08/16 19:04:45.688 Homegear version 0.6.0-1244
03/08/16 19:04:45.688 Git commit SHA of libhomegear-base: 953dea2f53a78e28b5e6e65d5e564e7ba92592e1
03/08/16 19:04:45.688 Git commit SHA of Homegear:         1cef456dae99d0c591dd6f62b3b5f0f34b1628e4
03/08/16 19:04:45.690 Info: Setting allowed core file size on monitor process to "4294967295" for user with id 0 and gr
oup with id 0.
03/08/16 19:04:45.690 Info: Core file size on monitor process now is "4294967295".
03/08/16 19:04:45.691 Info: Setting maximum thread priority on monitor process to "100" for user with id 0 and group wi
th id 0.
03/08/16 19:04:45.691 Info: Maximum thread priority on monitor process now is "100".
03/08/16 19:04:45.702 Info: Loading family module mod_philipshue.so
03/08/16 19:04:45.744 /etc/homegear/families/philipshue.conf
03/08/16 19:04:45.745 Info: Loading family module mod_max.so
03/08/16 19:04:45.844 /etc/homegear/families/max.conf
03/08/16 19:04:45.845 Info: Loading family module mod_homematicbidcos.so
03/08/16 19:04:45.955 /etc/homegear/families/homematicbidcos.conf
03/08/16 19:04:45.970 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN": Info: Disabling AES encryption f
or communication with HM-CFG-LAN.
03/08/16 19:04:45.970 Info: Loading family module mod_miscellaneous.so
03/08/16 19:04:46.000 /etc/homegear/families/miscellaneous.conf
03/08/16 19:04:46.001 Info: Loading family module mod_insteon.so
03/08/16 19:04:46.057 /etc/homegear/families/insteon.conf
03/08/16 19:04:46.068 Info: Loading family module mod_sonos.so
03/08/16 19:04:46.097 /etc/homegear/families/sonos.conf
03/08/16 19:04:46.106 Info: Loading family module mod_homematicwired.so
03/08/16 19:04:46.156 /etc/homegear/families/homematicwired.conf
03/08/16 19:04:46.174 Info: Settings up physical interfaces and GPIOs...
03/08/16 19:04:46.175 Info: Dropping privileges to user homegear (106) and group homegear (111)
03/08/16 19:04:46.183 Info: Homegear is (now) running as user with id 106 and group with id 111.
03/08/16 19:04:46.183 Info: Setting allowed core file size to "4294967295" for user with id 106 and group with id 111.
03/08/16 19:04:46.184 Info: Core file size now is "4294967295".
03/08/16 19:04:46.184 Info: Setting maximum thread priority to "100" for user with id 106 and group with id 111.
03/08/16 19:04:46.184 Info: Maximum thread priority now is "100".
03/08/16 19:04:46.242 Info: Backing up database...
03/08/16 19:04:46.616 Initializing database...
03/08/16 19:04:46.630 Starting script engine server...
03/08/16 19:04:46.757 Initializing licensing controller...
03/08/16 19:04:46.757 Loading licensing controller data...
03/08/16 19:04:46.757 Loading devices...
03/08/16 19:04:46.758 Loading XML RPC devices...
03/08/16 19:04:51.079 Loading device 3
03/08/16 19:04:51.081 Module HomeMatic BidCoS: Info: Central address set to 0xFDFFFF.
03/08/16 19:04:51.084 Info: Not initializing device family HomeMatic Wired, because no physical interface was found.
03/08/16 19:04:51.085 Info: Disposing family module mod_homematicwired.so
03/08/16 19:04:51.086 Info: Not initializing device family Insteon, because no physical interface was found.
03/08/16 19:04:51.086 Info: Disposing family module mod_insteon.so
03/08/16 19:04:51.087 Info: Not initializing device family MAX!, because no physical interface was found.
03/08/16 19:04:51.088 Info: Disposing family module mod_max.so
03/08/16 19:04:51.089 Info: Not initializing device family Philips hue, because no physical interface was found.
03/08/16 19:04:51.089 Info: Disposing family module mod_philipshue.so
03/08/16 19:04:51.090 Info: Not initializing device family Sonos, because no physical interface was found.
03/08/16 19:04:51.090 Info: Disposing family module mod_sonos.so
03/08/16 19:04:51.091 Loading XML RPC devices...
03/08/16 19:04:51.101 Loading device 1
03/08/16 19:04:51.102 Start listening for packets...
03/08/16 19:04:51.104 Initializing RPC client...
03/08/16 19:04:51.104 Starting XML RPC server RPCServer1 listening on 0.0.0.0:2001...
03/08/16 19:04:51.118 Info: Connecting to host 192.168.1.174 on port 1000...
03/08/16 19:04:51.129 Starting XML RPC server RPCServer2 listening on 0.0.0.0:2002, SSL enabled...
03/08/16 19:04:51.132 Info: Connected to host 192.168.1.174 on port 1000. Client number is: 1
03/08/16 19:04:51.137 RPC Server (Port 2001): Info: RPC Server started listening on address 0.0.0.0 and port 2001
03/08/16 19:04:51.143 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "HM-CFG-LAN": Info: Initialization completed.
03/08/16 19:04:51.245 Starting XML RPC server RPCServer3 listening on 0.0.0.0:2003, SSL enabled, authentication enabled
...
03/08/16 19:04:51.248 RPC Server (Port 2002): Info: RPC Server started listening on address 0.0.0.0 and port 2002
03/08/16 19:04:51.338 Starting CLI server...
03/08/16 19:04:51.339 Initializing event handler...
03/08/16 19:04:51.341 Loading events...
03/08/16 19:04:51.343 Startup complete. Waiting for physical interfaces to connect.
03/08/16 19:04:51.343 All physical interfaces are connected now.
03/08/16 19:04:51.343 Starting UPnP server...
03/08/16 19:04:51.348 RPC Server (Port 2003): Info: RPC Server started listening on address 0.0.0.0 and port 2003
03/08/16 19:04:51.350 Info: UPnP server: Binding to address: 192.168.1.8
03/08/16 19:04:51.351 UPnP Server: Info: Started listening.
03/08/16 19:04:52.168 RPC Server (Port 2001): Info: Connection from 127.0.0.1:45667 accepted. Client number: 7
03/08/16 19:04:52.169 RPC Server (Port 2001): Info: RPC server client id for client number 7 is: 0
03/08/16 19:04:52.172 RPC Server (Port 2001): Info: Client number 7 is calling RPC method: init Parameters:
(String) binary://192.168.1.8:9123
03/08/16 19:04:52.180 RPC Server (Port 2001): Info: Connection to client number 7 closed (3).
03/08/16 19:04:52.191 RPC Server (Port 2001): Info: Connection from 127.0.0.1:45668 accepted. Client number: 8
03/08/16 19:04:52.193 RPC Server (Port 2001): Info: RPC server client id for client number 8 is: 1
03/08/16 19:04:52.196 RPC Server (Port 2001): Info: Client number 8 is calling RPC method: getDeviceDescription Paramet
ers:
(String) BidCoS-RF
03/08/16 19:04:52.204 RPC Server (Port 2001): Info: Connection to client number 8 closed (3).
03/08/16 19:04:52.228 RPC Server (Port 2001): Info: Connection from 127.0.0.1:45669 accepted. Client number: 9
03/08/16 19:04:52.229 RPC Server (Port 2001): Info: RPC server client id for client number 9 is: 2
03/08/16 19:04:52.232 RPC Server (Port 2001): Info: Client number 9 is calling RPC method: getAllValues Parameters:
(Boolean) 1
03/08/16 19:04:52.249 RPC Server (Port 2001): Info: Connection to client number 9 closed (3).
03/08/16 19:04:52.260 RPC Server (Port 2001): Info: Connection from 127.0.0.1:45670 accepted. Client number: 10
03/08/16 19:04:52.261 RPC Server (Port 2001): Info: RPC server client id for client number 10 is: 3
03/08/16 19:04:52.264 RPC Server (Port 2001): Info: Client number 10 is calling RPC method: getAllSystemVariables Param
eters:
03/08/16 19:04:52.276 RPC Server (Port 2001): Info: Connection to client number 10 closed (3).
03/08/16 19:04:52.288 RPC Server (Port 2001): Info: Connection from 127.0.0.1:45671 accepted. Client number: 11
03/08/16 19:04:52.289 RPC Server (Port 2001): Info: RPC server client id for client number 11 is: 4
03/08/16 19:04:52.292 RPC Server (Port 2001): Info: Client number 11 is calling RPC method: init Parameters:
(String) binary://192.168.1.8:9123
(String) Homegear
03/08/16 19:04:52.294 Info: Adding server "binary://192.168.1.8".
03/08/16 19:04:52.296 Info: Calling init methods on server "binary://192.168.1.8".
03/08/16 19:04:52.305 RPC Server (Port 2001): Info: Connection to client number 11 closed (3).
03/08/16 19:04:52.797 RPC client: Info: Calling RPC method "system.listMethods" on server binary://192.168.1.8.
03/08/16 19:04:52.797 Info: Connecting to host 192.168.1.8 on port 9123...
03/08/16 19:04:52.801 Info: Connected to host 192.168.1.8 on port 9123. Client number is: 12
03/08/16 19:05:52.335 RPC Server (Port 2001): Info: Connection from 127.0.0.1:45674 accepted. Client number: 13
03/08/16 19:05:52.336 RPC Server (Port 2001): Info: RPC server client id for client number 13 is: 5
03/08/16 19:05:52.342 RPC Server (Port 2001): Info: Client number 13 is calling RPC method: init Parameters:
(String) binary://192.168.1.8:9123
03/08/16 19:05:52.342 Info: Removing server "binary://192.168.1.8".
03/08/16 19:05:52.348 RPC Server (Port 2001): Info: Connection to client number 13 closed (3).
03/08/16 19:05:52.364 RPC Server (Port 2001): Info: Connection from 127.0.0.1:45675 accepted. Client number: 14
03/08/16 19:05:52.365 RPC Server (Port 2001): Info: RPC server client id for client number 14 is: 6
03/08/16 19:05:52.368 RPC Server (Port 2001): Info: Client number 14 is calling RPC method: getDeviceDescription Parame
ters:
(String) BidCoS-RF
03/08/16 19:05:52.372 RPC Server (Port 2001): Info: Connection to client number 14 closed (3).
03/08/16 19:05:52.397 RPC Server (Port 2001): Info: Connection from 127.0.0.1:45676 accepted. Client number: 15
03/08/16 19:05:52.399 RPC Server (Port 2001): Info: RPC server client id for client number 15 is: 7
03/08/16 19:05:52.402 RPC Server (Port 2001): Info: Client number 15 is calling RPC method: getAllValues Parameters:
(Boolean) 1
03/08/16 19:05:52.419 RPC Server (Port 2001): Info: Connection to client number 15 closed (3).
03/08/16 19:05:52.430 RPC Server (Port 2001): Info: Connection from 127.0.0.1:45677 accepted. Client number: 16
03/08/16 19:05:52.431 RPC Server (Port 2001): Info: RPC server client id for client number 16 is: 8
03/08/16 19:05:52.434 RPC Server (Port 2001): Info: Client number 16 is calling RPC method: getAllSystemVariables Param
eters:
03/08/16 19:05:52.446 RPC Server (Port 2001): Info: Connection to client number 16 closed (3).
03/08/16 19:05:52.458 RPC Server (Port 2001): Info: Connection from 127.0.0.1:45678 accepted. Client number: 17
03/08/16 19:05:52.459 RPC Server (Port 2001): Info: RPC server client id for client number 17 is: 9
03/08/16 19:05:52.462 RPC Server (Port 2001): Info: Client number 17 is calling RPC method: init Parameters:
(String) binary://192.168.1.8:9123
(String) Homegear
03/08/16 19:05:52.464 Info: Adding server "binary://192.168.1.8".
03/08/16 19:05:52.466 Info: Calling init methods on server "binary://192.168.1.8".
03/08/16 19:05:52.475 RPC Server (Port 2001): Info: Connection to client number 17 closed (3).
03/08/16 19:05:52.967 RPC client: Info: Calling RPC method "system.listMethods" on server binary://192.168.1.8.
03/08/16 19:05:52.967 Info: Connecting to host 192.168.1.8 on port 9123...
03/08/16 19:05:52.969 Info: Connected to host 192.168.1.8 on port 9123. Client number is: 18
03/08/16 19:06:52.510 RPC Server (Port 2001): Info: Connection from 127.0.0.1:45681 accepted. Client number: 19
03/08/16 19:06:52.511 RPC Server (Port 2001): Info: RPC server client id for client number 19 is: 10
03/08/16 19:06:52.514 RPC Server (Port 2001): Info: Client number 19 is calling RPC method: init Parameters:
(String) binary://192.168.1.8:9123
03/08/16 19:06:52.515 Info: Removing server "binary://192.168.1.8".
03/08/16 19:06:52.521 RPC Server (Port 2001): Info: Connection to client number 19 closed (3).
03/08/16 19:06:52.533 RPC Server (Port 2001): Info: Connection from 127.0.0.1:45682 accepted. Client number: 20
03/08/16 19:06:52.535 RPC Server (Port 2001): Info: RPC server client id for client number 20 is: 11
03/08/16 19:06:52.538 RPC Server (Port 2001): Info: Client number 20 is calling RPC method: getDeviceDescription Parame
ters:
(String) BidCoS-RF
03/08/16 19:06:52.542 RPC Server (Port 2001): Info: Connection to client number 20 closed (3).
03/08/16 19:06:52.580 RPC Server (Port 2001): Info: Connection from 127.0.0.1:45683 accepted. Client number: 21
03/08/16 19:06:52.581 RPC Server (Port 2001): Info: RPC server client id for client number 21 is: 12
03/08/16 19:06:52.584 RPC Server (Port 2001): Info: Client number 21 is calling RPC method: getAllValues Parameters:
(Boolean) 1
03/08/16 19:06:52.601 RPC Server (Port 2001): Info: Connection to client number 21 closed (3).
03/08/16 19:06:52.612 RPC Server (Port 2001): Info: Connection from 127.0.0.1:45684 accepted. Client number: 22
03/08/16 19:06:52.613 RPC Server (Port 2001): Info: RPC server client id for client number 22 is: 13
03/08/16 19:06:52.616 RPC Server (Port 2001): Info: Client number 22 is calling RPC method: getAllSystemVariables Param
eters:
03/08/16 19:06:52.623 RPC Server (Port 2001): Info: Connection to client number 22 closed (3).
03/08/16 19:06:52.644 RPC Server (Port 2001): Info: Connection from 127.0.0.1:45685 accepted. Client number: 23
03/08/16 19:06:52.645 RPC Server (Port 2001): Info: RPC server client id for client number 23 is: 14
03/08/16 19:06:52.648 RPC Server (Port 2001): Info: Client number 23 is calling RPC method: init Parameters:
(String) binary://192.168.1.8:9123
(String) Homegear
03/08/16 19:06:52.650 Info: Adding server "binary://192.168.1.8".
03/08/16 19:06:52.651 Info: Calling init methods on server "binary://192.168.1.8".
03/08/16 19:06:52.656 RPC Server (Port 2001): Info: Connection to client number 23 closed (3).
03/08/16 19:06:53.152 RPC client: Info: Calling RPC method "system.listMethods" on server binary://192.168.1.8.
03/08/16 19:06:53.152 Info: Connecting to host 192.168.1.8 on port 9123...
03/08/16 19:06:53.156 Info: Connected to host 192.168.1.8 on port 9123. Client number is: 24
03/08/16 19:07:21.745 Info: CLI connection accepted. Client number: 25
03/08/16 19:07:52.687 RPC Server (Port 2001): Info: Connection from 127.0.0.1:45688 accepted. Client number: 26
03/08/16 19:07:52.688 RPC Server (Port 2001): Info: RPC server client id for client number 26 is: 15
03/08/16 19:07:52.691 RPC Server (Port 2001): Info: Client number 26 is calling RPC method: init Parameters:
(String) binary://192.168.1.8:9123
03/08/16 19:07:52.691 Info: Removing server "binary://192.168.1.8".
03/08/16 19:07:52.698 RPC Server (Port 2001): Info: Connection to client number 26 closed (3).
03/08/16 19:07:52.710 RPC Server (Port 2001): Info: Connection from 127.0.0.1:45689 accepted. Client number: 27
03/08/16 19:07:52.711 RPC Server (Port 2001): Info: RPC server client id for client number 27 is: 16
03/08/16 19:07:52.714 RPC Server (Port 2001): Info: Client number 27 is calling RPC method: getDeviceDescription Parame
ters:
(String) BidCoS-RF
03/08/16 19:07:52.718 RPC Server (Port 2001): Info: Connection to client number 27 closed (3).
03/08/16 19:07:52.735 RPC Server (Port 2001): Info: Connection from 127.0.0.1:45690 accepted. Client number: 28
03/08/16 19:07:52.736 RPC Server (Port 2001): Info: RPC server client id for client number 28 is: 17
03/08/16 19:07:52.747 RPC Server (Port 2001): Info: Client number 28 is calling RPC method: getAllValues Parameters:
(Boolean) 1
03/08/16 19:07:52.758 RPC Server (Port 2001): Info: Connection to client number 28 closed (3).
03/08/16 19:07:52.775 RPC Server (Port 2001): Info: Connection from 127.0.0.1:45691 accepted. Client number: 29
03/08/16 19:07:52.776 RPC Server (Port 2001): Info: RPC server client id for client number 29 is: 18
03/08/16 19:07:52.779 RPC Server (Port 2001): Info: Client number 29 is calling RPC method: getAllSystemVariables Param
eters:
03/08/16 19:07:52.791 RPC Server (Port 2001): Info: Connection to client number 29 closed (3).
03/08/16 19:07:52.803 RPC Server (Port 2001): Info: Connection from 127.0.0.1:45692 accepted. Client number: 30
03/08/16 19:07:52.804 RPC Server (Port 2001): Info: RPC server client id for client number 30 is: 19
03/08/16 19:07:52.808 RPC Server (Port 2001): Info: Client number 30 is calling RPC method: init Parameters:
(String) binary://192.168.1.8:9123
(String) Homegear
03/08/16 19:07:52.810 Info: Adding server "binary://192.168.1.8".
03/08/16 19:07:52.811 Info: Calling init methods on server "binary://192.168.1.8".
03/08/16 19:07:52.821 RPC Server (Port 2001): Info: Connection to client number 30 closed (3).
03/08/16 19:07:53.312 RPC client: Info: Calling RPC method "system.listMethods" on server binary://192.168.1.8.
03/08/16 19:07:53.312 Info: Connecting to host 192.168.1.8 on port 9123...
03/08/16 19:07:53.314 Info: Connected to host 192.168.1.8 on port 9123. Client number is: 31

Leider habe ich keinen Windows Rechner und kann das Windows-Konfigurations Programm des Adapters nicht ausführen. Gibt es eine Möglichkeit die über DHCP bezogene IP-Adresse in eine feste IP-Adresse zu ändern (ohne Windows-Prgramm)?

An der Stelle schon mal, vielen Dank für diese Software und für dieses informative Forum.

Hat jemand einen Tip für mich ?

Hallo

Ich bin einen Schritt weiter :bulb: .

In meiner Hilflosigkeit, habe ich einfach nochmal versucht einen HomeMatic Funk-Schaltaktor 1fach mit Leistungsmessung, Zwischenstecker anzulernen und überraschenderweise hat es geklappt. Das heißt für mich, die Konfiguration ist nicht so falsch. :smiley:

Ich hatte erwartet, das der HM-CFG-LAN in der Liste der homegear Geräte auftaucht, weshalb ich hier um Unterstützung gebeten hatte.

Hat jemand eine Idee, wie ich bei dem HM-CFG-LAN Adapter die IP-Adresse von DHCP auf eine feste IP-Adresse setzen kann ? (Ich habe keinen Windows Rechner)

Danke für dieses Forum und eure Unterstützung

Jürgen

Hallo Jürgen,

mir ist leider kein Weg bekannt, wie du den HM-CFG-LAN ohne Windows-Rechner auf eine fest IP bekommst (das geht bestimmt auch ohne, aber die entsprechenden Netzwerk-Pakete habe ich mir noch nicht angeschaut). Kannst du vielleicht irgendwo Windows in einer Virtuellen Maschine starten oder einen Freund bitten, mal mit Windows-Notebook vorbeizuschauen? Dann kannst du mit der Windows-Software zum HM-CFG-LAN die IP ändern.

Kannst du alternativ im DHCP-Server die IP-Adresse fest dem HM-CFG-LAN zuweisen (so habe ich es bei mir gemacht)?

Viele Grüße

Sathya