Kein Pairing möglich zwischen HM-LGW und HM-CC-RT Heizkörperthermostat

Hallo zusammen,

ich interessiere mich schon längere Zeit für eine Smarthome-Steuerung und bin gerade dabei mich durch die einzelnen Großbaustellen zu kämpfen… :blush: Die Einstiegshürden sind (zumindest für mich) doch beträchtlich…

Kurz zu meiner Ausgangslage:

Raspberry2 mit Raspian-Image inkl. Homegear und Openhab sowie einem HM-LGW als Gateway.

Das Thermostat ist nagelneu aus der Verpackung und das Gateway (gebraucht gekauft) hab ich resetet.

Konfig-File 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 = 0xFDABAB

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

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

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

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

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

Meine Versuche per sudo homegear -r

fs 0 pon ls und gleichzeitigen pairen des Thermostats schlagen leider alle fehl.

Hier ein Auszug aus dem homegear.log:

03/25/16 20:24:35.415 Starting Homegear... 03/25/16 20:24:35.417 Homegear version 0.6.0-1274 03/25/16 20:24:35.418 Git commit SHA of libhomegear-base: e9eab5319a6e80438a1022c46ce0d89d9a95e7b4 03/25/16 20:24:35.418 Git commit SHA of Homegear: 44bbf379b9ce30a2001fbbc8b5a6339b756513a7 03/25/16 20:24:35.420 Info: Setting allowed core file size to "4294967295" for user with id 0 and group with id 0. 03/25/16 20:24:35.421 Info: Core file size now is "4294967295". 03/25/16 20:24:35.421 Info: Setting maximum thread priority to "100" for user with id 0 and group with id 0. 03/25/16 20:24:35.422 Info: Maximum thread priority now is "100". 03/25/16 20:24:35.427 Starting Homegear... 03/25/16 20:24:35.429 Homegear version 0.6.0-1274 03/25/16 20:24:35.430 Git commit SHA of libhomegear-base: e9eab5319a6e80438a1022c46ce0d89d9a95e7b4 03/25/16 20:24:35.430 Git commit SHA of Homegear: 44bbf379b9ce30a2001fbbc8b5a6339b756513a7 03/25/16 20:24:35.435 Info: Loading family module mod_philipshue.so 03/25/16 20:24:35.447 /etc/homegear/families/philipshue.conf 03/25/16 20:24:35.449 Info: Loading family module mod_max.so 03/25/16 20:24:35.464 /etc/homegear/families/max.conf 03/25/16 20:24:35.465 Info: Loading family module mod_homematicbidcos.so 03/25/16 20:24:35.490 /etc/homegear/families/homematicbidcos.conf 03/25/16 20:24:35.493 Info: Loading family module mod_miscellaneous.so 03/25/16 20:24:35.500 /etc/homegear/families/miscellaneous.conf 03/25/16 20:24:35.502 Info: Loading family module mod_insteon.so 03/25/16 20:24:35.514 /etc/homegear/families/insteon.conf 03/25/16 20:24:35.515 Info: Loading family module mod_sonos.so 03/25/16 20:24:35.524 /etc/homegear/families/sonos.conf 03/25/16 20:24:35.526 Info: Loading family module mod_homematicwired.so 03/25/16 20:24:35.537 /etc/homegear/families/homematicwired.conf 03/25/16 20:24:35.541 Info: Settings up physical interfaces and GPIOs... 03/25/16 20:24:35.543 Info: Dropping privileges to user homegear (106) and group homegear (111) 03/25/16 20:24:35.544 Info: Homegear is (now) running as user with id 106 and group with id 111. 03/25/16 20:24:35.544 Info: Setting allowed core file size to "4294967295" for user with id 106 and group with id 111. 03/25/16 20:24:35.545 Info: Core file size now is "4294967295". 03/25/16 20:24:35.545 Info: Setting maximum thread priority to "100" for user with id 106 and group with id 111. 03/25/16 20:24:35.546 Info: Maximum thread priority now is "100". 03/25/16 20:24:35.558 Info: Backing up database... 03/25/16 20:24:35.699 Initializing database... 03/25/16 20:24:35.706 Starting script engine server... 03/25/16 20:24:35.775 Initializing licensing controller... 03/25/16 20:24:35.776 Loading licensing controller data... 03/25/16 20:24:35.776 Loading devices... 03/25/16 20:24:35.776 Loading XML RPC devices... 03/25/16 20:24:37.965 Loading device 3 03/25/16 20:24:37.966 Module HomeMatic BidCoS: Info: Central address set to 0xFDABAB. 03/25/16 20:24:37.968 Info: Not initializing device family HomeMatic Wired, because no physical interface was found. 03/25/16 20:24:37.968 Info: Disposing family module mod_homematicwired.so 03/25/16 20:24:37.969 Info: Not initializing device family Insteon, because no physical interface was found. 03/25/16 20:24:37.969 Info: Disposing family module mod_insteon.so 03/25/16 20:24:37.970 Info: Not initializing device family MAX!, because no physical interface was found. 03/25/16 20:24:37.970 Info: Disposing family module mod_max.so 03/25/16 20:24:37.970 Info: Not initializing device family Philips hue, because no physical interface was found. 03/25/16 20:24:37.971 Info: Disposing family module mod_philipshue.so 03/25/16 20:24:37.971 Loading XML RPC devices... 03/25/16 20:24:37.998 Loading device 2 03/25/16 20:24:38.001 Loading XML RPC devices... 03/25/16 20:24:38.006 Loading device 1 03/25/16 20:24:38.007 Start listening for packets... 03/25/16 20:24:38.010 Initializing RPC client... 03/25/16 20:24:38.011 Starting XML RPC server RPCServer1 listening on 0.0.0.0:2001... 03/25/16 20:24:38.017 Starting XML RPC server RPCServer2 listening on 0.0.0.0:2002, SSL enabled... 03/25/16 20:24:38.023 Module Sonos: Event server "My-Sonos-1234": Info: Started listening on address 192.168.178.3 and port 7373 03/25/16 20:24:38.023 Info: Connecting to host 192.168.178.27 on port 2001... 03/25/16 20:24:38.026 Info: Connecting to host 192.168.178.27 on port 2000... 03/25/16 20:24:38.027 RPC Server (Port 2001): Info: RPC Server started listening on address 0.0.0.0 and port 2001 03/25/16 20:24:38.031 Info: Connected to host 192.168.178.27 on port 2001. Client number is: 2 03/25/16 20:24:38.036 Info: Connected to host 192.168.178.27 on port 2000. Client number is: 3 03/25/16 20:24:38.110 Starting XML RPC server RPCServer3 listening on 0.0.0.0:2003, SSL enabled, authentication enabled... 03/25/16 20:24:38.123 RPC Server (Port 2002): Info: RPC Server started listening on address 0.0.0.0 and port 2002 03/25/16 20:24:38.179 Starting CLI server... 03/25/16 20:24:38.179 Initializing event handler... 03/25/16 20:24:38.180 Loading events... 03/25/16 20:24:38.181 Startup complete. Waiting for physical interfaces to connect. 03/25/16 20:24:38.182 All physical interfaces are connected now. 03/25/16 20:24:38.182 Starting UPnP server... 03/25/16 20:24:38.184 Info: UPnP server: Binding to address: 192.168.178.3 03/25/16 20:24:38.185 UPnP Server: Info: Started listening. 03/25/16 20:24:38.186 RPC Server (Port 2003): Info: RPC Server started listening on address 0.0.0.0 and port 2003 03/25/16 20:24:45.069 Module HomeMatic BidCoS: HM-LGW "My-HM-LGW": Info: Init queue completed. Sending peers... 03/25/16 20:24:45.069 Module HomeMatic BidCoS: HM-LGW "My-HM-LGW": Info: Peer sending completed. 03/25/16 20:24:53.983 HomeMatic BidCoS packet received (My-HM-LGW, RSSI: -86 dBm): 0F1286103F65350000000AA8F00E0000 03/25/16 20:25:29.712 HomeMatic BidCoS packet received (My-HM-LGW, RSSI: -54 dBm): 0D5C861041198900000006010000 03/25/16 20:25:34.832 RPC Server (Port 2001): Info: Connection from 127.0.0.1:40291 accepted. Client number: 12 03/25/16 20:25:34.833 RPC Server (Port 2001): Info: RPC server client id for client number 12 is: 0 03/25/16 20:25:34.834 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getDeviceDescription Parameters: (String) BidCoS-RF 03/25/16 20:25:34.838 RPC Server (Port 2001): Info: Connection to client number 12 closed (3). 03/25/16 20:25:34.843 RPC Server (Port 2001): Info: Connection from 127.0.0.1:40292 accepted. Client number: 13 03/25/16 20:25:34.844 RPC Server (Port 2001): Info: RPC server client id for client number 13 is: 1 03/25/16 20:25:34.845 RPC Server (Port 2001): Info: Client number 13 is calling RPC method: getAllValues Parameters: (Boolean) 1 03/25/16 20:25:34.858 RPC Server (Port 2001): Info: Connection to client number 13 closed (3). 03/25/16 20:25:34.862 RPC Server (Port 2001): Info: Connection from 127.0.0.1:40293 accepted. Client number: 14 03/25/16 20:25:34.863 RPC Server (Port 2001): Info: RPC server client id for client number 14 is: 2 03/25/16 20:25:34.864 RPC Server (Port 2001): Info: Client number 14 is calling RPC method: getAllSystemVariables Parameters: 03/25/16 20:25:34.868 RPC Server (Port 2001): Info: Connection to client number 14 closed (3). 03/25/16 20:25:34.872 RPC Server (Port 2001): Info: Connection from 127.0.0.1:40294 accepted. Client number: 15 03/25/16 20:25:34.873 RPC Server (Port 2001): Info: RPC server client id for client number 15 is: 3 03/25/16 20:25:34.874 RPC Server (Port 2001): Info: Client number 15 is calling RPC method: init Parameters: (String) binary://127.0.0.1:9123 (String) Homegear 03/25/16 20:25:34.875 Info: Adding server "binary://127.0.0.1". 03/25/16 20:25:34.876 Info: Calling init methods on server "binary://127.0.0.1". 03/25/16 20:25:34.879 RPC Server (Port 2001): Info: Connection to client number 15 closed (3). 03/25/16 20:25:35.376 RPC client: Info: Calling RPC method "system.listMethods" on server binary://127.0.0.1. 03/25/16 20:25:35.377 Info: Connecting to host 127.0.0.1 on port 9123... 03/25/16 20:25:35.378 Info: Connected to host 127.0.0.1 on port 9123. Client number is: 16 03/25/16 20:25:47.878 Info: CLI connection accepted. Client number: 17 03/25/16 20:26:00.265 HomeMatic BidCoS packet received (My-HM-LGW, RSSI: -31 dBm): 1A0184003CE1BD0000001400954D4551303830373830355900FFFF 03/25/16 20:26:00.268 Module HomeMatic BidCoS: Info: Pushing pending queues. 03/25/16 20:26:00.324 Module HomeMatic BidCoS: HM-LGW "My-HM-LGW": Info: Sending (My-HM-LGW): 1078A001FDABAB3CE1BD00050000000000 03/25/16 20:26:34.891 RPC Server (Port 2001): Info: Connection from 127.0.0.1:40296 accepted. Client number: 20 03/25/16 20:26:34.891 RPC Server (Port 2001): Info: RPC server client id for client number 20 is: 4 03/25/16 20:26:34.892 RPC Server (Port 2001): Info: Client number 20 is calling RPC method: init Parameters: (String) binary://127.0.0.1:9123 03/25/16 20:26:34.893 Info: Removing server "binary://127.0.0.1". 03/25/16 20:26:34.897 RPC Server (Port 2001): Info: Connection to client number 20 closed (3). 03/25/16 20:26:34.907 RPC Server (Port 2001): Info: Connection from 127.0.0.1:40297 accepted. Client number: 21 03/25/16 20:26:34.908 RPC Server (Port 2001): Info: RPC server client id for client number 21 is: 5 03/25/16 20:26:34.909 RPC Server (Port 2001): Info: Client number 21 is calling RPC method: getDeviceDescription Parameters: (String) BidCoS-RF 03/25/16 20:26:34.912 RPC Server (Port 2001): Info: Connection to client number 21 closed (3). 03/25/16 20:26:34.917 RPC Server (Port 2001): Info: Connection from 127.0.0.1:40298 accepted. Client number: 22 03/25/16 20:26:34.918 RPC Server (Port 2001): Info: RPC server client id for client number 22 is: 6 03/25/16 20:26:34.919 RPC Server (Port 2001): Info: Client number 22 is calling RPC method: getAllValues Parameters: (Boolean) 1 03/25/16 20:26:34.932 RPC Server (Port 2001): Info: Connection to client number 22 closed (3). 03/25/16 20:26:34.935 RPC Server (Port 2001): Info: Connection from 127.0.0.1:40299 accepted. Client number: 23 03/25/16 20:26:34.936 RPC Server (Port 2001): Info: RPC server client id for client number 23 is: 7 03/25/16 20:26:34.937 RPC Server (Port 2001): Info: Client number 23 is calling RPC method: getAllSystemVariables Parameters: 03/25/16 20:26:34.941 RPC Server (Port 2001): Info: Connection to client number 23 closed (3). 03/25/16 20:26:34.946 RPC Server (Port 2001): Info: Connection from 127.0.0.1:40300 accepted. Client number: 24 03/25/16 20:26:34.947 RPC Server (Port 2001): Info: RPC server client id for client number 24 is: 8 03/25/16 20:26:34.948 RPC Server (Port 2001): Info: Client number 24 is calling RPC method: init Parameters: (String) binary://127.0.0.1:9123 (String) Homegear 03/25/16 20:26:34.949 Info: Adding server "binary://127.0.0.1". 03/25/16 20:26:34.949 Info: Calling init methods on server "binary://127.0.0.1". 03/25/16 20:26:34.952 RPC Server (Port 2001): Info: Connection to client number 24 closed (3). 03/25/16 20:26:35.245 HomeMatic BidCoS packet received (My-HM-LGW, RSSI: -88 dBm): 0FAB86103D92C40000000AB0EF100600 03/25/16 20:26:35.450 RPC client: Info: Calling RPC method "system.listMethods" on server binary://127.0.0.1. 03/25/16 20:26:35.450 Info: Connecting to host 127.0.0.1 on port 9123... 03/25/16 20:26:35.451 Info: Connected to host 127.0.0.1 on port 9123. Client number is: 25 03/25/16 20:27:05.728 HomeMatic BidCoS packet received (My-HM-LGW, RSSI: -86 dBm): 0F1386103F65350000000AA8F10E0000 03/25/16 20:27:34.967 RPC Server (Port 2001): Info: Connection from 127.0.0.1:40302 accepted. Client number: 28 03/25/16 20:27:34.968 RPC Server (Port 2001): Info: RPC server client id for client number 28 is: 9 03/25/16 20:27:34.973 RPC Server (Port 2001): Info: Client number 28 is calling RPC method: init Parameters: (String) binary://127.0.0.1:9123 03/25/16 20:27:34.974 Info: Removing server "binary://127.0.0.1". 03/25/16 20:27:34.978 RPC Server (Port 2001): Info: Connection to client number 28 closed (3). 03/25/16 20:27:34.983 RPC Server (Port 2001): Info: Connection from 127.0.0.1:40303 accepted. Client number: 29 03/25/16 20:27:34.984 RPC Server (Port 2001): Info: RPC server client id for client number 29 is: 10 03/25/16 20:27:34.985 RPC Server (Port 2001): Info: Client number 29 is calling RPC method: getDeviceDescription Parameters: (String) BidCoS-RF 03/25/16 20:27:34.988 RPC Server (Port 2001): Info: Connection to client number 29 closed (3). 03/25/16 20:27:34.994 RPC Server (Port 2001): Info: Connection from 127.0.0.1:40304 accepted. Client number: 30 03/25/16 20:27:34.994 RPC Server (Port 2001): Info: RPC server client id for client number 30 is: 11 03/25/16 20:27:34.995 RPC Server (Port 2001): Info: Client number 30 is calling RPC method: getAllValues Parameters: (Boolean) 1 03/25/16 20:27:35.008 RPC Server (Port 2001): Info: Connection to client number 30 closed (3). 03/25/16 20:27:35.011 RPC Server (Port 2001): Info: Connection from 127.0.0.1:40305 accepted. Client number: 31 03/25/16 20:27:35.012 RPC Server (Port 2001): Info: RPC server client id for client number 31 is: 12 03/25/16 20:27:35.013 RPC Server (Port 2001): Info: Client number 31 is calling RPC method: getAllSystemVariables Parameters: 03/25/16 20:27:35.017 RPC Server (Port 2001): Info: Connection to client number 31 closed (3). 03/25/16 20:27:35.022 RPC Server (Port 2001): Info: Connection from 127.0.0.1:40306 accepted. Client number: 32 03/25/16 20:27:35.023 RPC Server (Port 2001): Info: RPC server client id for client number 32 is: 13 03/25/16 20:27:35.024 RPC Server (Port 2001): Info: Client number 32 is calling RPC method: init Parameters: (String) binary://127.0.0.1:9123 (String) Homegear 03/25/16 20:27:35.025 Info: Adding server "binary://127.0.0.1". 03/25/16 20:27:35.025 Info: Calling init methods on server "binary://127.0.0.1". 03/25/16 20:27:35.034 RPC Server (Port 2001): Info: Connection to client number 32 closed (3). 03/25/16 20:27:35.526 RPC client: Info: Calling RPC method "system.listMethods" on server binary://127.0.0.1. 03/25/16 20:27:35.526 Info: Connecting to host 127.0.0.1 on port 9123... 03/25/16 20:27:35.527 Info: Connected to host 127.0.0.1 on port 9123. Client number is: 33

Was mache ich falsch?

Nebenschauplatz: Wieso zählt der RPC-Client pro Minute irgendwelche Clients hoch?

Danke für eure Hilfe!

Grüße

Matthias

Hallo Matthias,

setz mal “sendfix = true” in der Konfiguration. Klappt es jetzt? Die Clientnummer sind die IDs der Verbindungen zu OpenHAB. Mit jedem CLI-Paket wird eine TCP-Verbindung aufgebaut und diese bekommt eine neue ID.

Viele Grüße

Sathya

Hallo Sathya,

vielen Dank für den Tipp, ich werd es am Wochenende wenn ich wieder zu Hause bin gleich testen und das Ergebnis posten.

Danke auch für den Hinweis bezüglich der CLI-Pakete. Die Verbindung zu openHAB wird die nächste Baustelle sein die ich angehe. Ich versuche mich langsam voran zu tasten, aber die SmartHome-Thematik erschlägt mich eher und anstatt Antworten stoße ich eher immer auf neue Fragen.

Viele Grüße

Matthias

Hallo Sathya,

mit “sendfix = true” und nem Neustart des homegear-Dienstes hat das Pairing funktioniert, danke!

D.h. für mich auf zur nächsten Baustelle, Verbindung zu openHAB herstellen…

Liebe Grüße

Matthias