CC1101 Modul kein Pairing möglich

Deutsche Foren Hardware
#1

Hallo liebes Forum,

ich habe das fertige Modul von cod.m gekauft und am RPI angeschlossen. SPI aktiviert. Homegear 0.7 installiert und lt. Anleitung konfiguriert ( homematicbidcos.conf). Leider bekomme ich kein Pairing zum HM-Sec-Key-S. Wie kann ich feststellen ob das Modul soweit korrekt läuft?

Wesentlicher Teil des .conf:

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

## 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, homegeargateway
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 = 0

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

Debuglevel hat ich mal auf 5 gesetzt. Da kriege ich aber keine Meldungen bezüglich einer Pairinganfrage, nur jede Menge UPnP Meldungen. Was tun?

04/09/19 20:18:03.479 Starting Homegear...
04/09/19 20:18:03.479 Homegear version 0.7.39-2773
04/09/19 20:18:03.480 Git commit SHA of libhomegear-base: -
04/09/19 20:18:03.480 Git branch of libhomegear-base:     -
04/09/19 20:18:03.480 Git commit SHA of Homegear:         -
04/09/19 20:18:03.480 Git branch of Homegear:             -
04/09/19 20:18:03.483 Info: Setting allowed core file size to "4294967295" for user with id 0 and group with id 0.
04/09/19 20:18:03.483 Info: Core file size now is "4294967295".
04/09/19 20:18:03.483 Info: Setting maximum thread priority to "4294967295" for user with id 0 and group with id 0.
04/09/19 20:18:03.484 Info: Maximum thread priority now is "4294967295".
04/09/19 20:18:03.516 Info: Backing up database...
04/09/19 20:18:03.922 Initializing database...
04/09/19 20:18:03.953 Info: Loading family module (type 1) mod_homematicbidcos.so
04/09/19 20:18:04.046 Info: Loading settings from /etc/homegear/families/homematicbidcos.conf
04/09/19 20:18:04.054 Info: Loading family module (type 1) mod_ipcam.so
04/09/19 20:18:04.078 Info: Loading settings from /etc/homegear/families/ipcam.conf
04/09/19 20:18:04.082 Info: Loading family module (type 1) mod_mbus.so
04/09/19 20:18:04.118 Info: Loading settings from /etc/homegear/families/m-bus.conf
04/09/19 20:18:04.121 Info: Loading family module (type 1) mod_insteon.so
04/09/19 20:18:04.167 Info: Loading settings from /etc/homegear/families/insteon.conf
04/09/19 20:18:04.169 Info: Loading family module (type 1) mod_miscellaneous.so
04/09/19 20:18:04.187 Info: Loading settings from /etc/homegear/families/miscellaneous.conf
04/09/19 20:18:04.189 Info: Setting up physical interfaces and GPIOs...
04/09/19 20:18:04.201 Info: Dropping privileges to user homegear (109) and group homegear (113)
04/09/19 20:18:04.203 Info: Homegear is (now) running as user with id 109 and group with id 113.
04/09/19 20:18:04.783 Starting script engine server...
04/09/19 20:18:05.081 Initializing licensing controller...
04/09/19 20:18:05.081 Loading licensing controller data...
04/09/19 20:18:05.082 Loading devices...
04/09/19 20:18:05.082 Loading XML RPC devices...
04/09/19 20:18:09.955 Loading device 1
04/09/19 20:18:09.956 Module HomeMatic BidCoS: Info: Central address set to 0xFAB001.
04/09/19 20:18:09.960 Loading XML RPC devices...
04/09/19 20:18:10.018 Loading device 3
04/09/19 20:18:10.022 Loading XML RPC devices...
04/09/19 20:18:10.028 Loading device 7
04/09/19 20:18:10.030 Loading XML RPC devices...
04/09/19 20:18:10.032 Loading device 12
04/09/19 20:18:10.035 Loading XML RPC devices...
04/09/19 20:18:10.046 Loading device 13
04/09/19 20:18:10.047 Initializing RPC client...
04/09/19 20:18:10.048 Starting XML RPC server FamilyRPCServer listening on ::1:2000...
04/09/19 20:18:10.338 RPC Server (Port 2000): Info: Enabling basic authentication for WebSockets.
04/09/19 20:18:10.346 Starting XML RPC server RPCServer1 listening on :::2001...
04/09/19 20:18:10.356 RPC Server (Port 2000): Info: RPC Server started listening on address ::1 and port 2000
04/09/19 20:18:10.641 RPC Server (Port 2001): Warning: SSL is not enabled for this RPC server. It is strongly recommended to disable all unencrypted RPC servers when the connected clients support it.
04/09/19 20:18:10.642 RPC Server (Port 2001): Warning: RPC server has no authorization enabled. Everybody on your local network can login into this installation. It is strongly recommended to enable authorization on all RPC servers when the connected clients support it.
04/09/19 20:18:10.642 RPC Server (Port 2001): Info: Enabling session authentication for WebSockets.
04/09/19 20:18:10.644 Starting XML RPC server RPCServer2 listening on :::2002, SSL enabled...
04/09/19 20:18:10.649 RPC Server (Port 2001): Info: RPC Server started listening on address :: and port 2001
04/09/19 20:18:10.939 RPC Server (Port 2002): Warning: RPC server has no authorization enabled. Everybody on your local network can login into this installation. It is strongly recommended to enable authorization on all RPC servers when the connected clients support it.
04/09/19 20:18:10.940 RPC Server (Port 2002): Info: Enabling session authentication for WebSockets.
04/09/19 20:18:11.048 Starting XML RPC server RPCServer3 listening on :::2003, SSL enabled, authentication enabled...
04/09/19 20:18:11.056 RPC Server (Port 2002): Info: RPC Server started listening on address :: and port 2002
04/09/19 20:18:11.342 RPC Server (Port 2003): Info: Enabling basic authentication.
04/09/19 20:18:11.342 RPC Server (Port 2003): Info: Enabling client certificate authentication.
04/09/19 20:18:11.342 RPC Server (Port 2003): Info: Enabling session authentication for WebSockets.
04/09/19 20:18:11.431 Initializing event handler...
04/09/19 20:18:11.433 Loading events...
04/09/19 20:18:11.435 Start listening for packets...
04/09/19 20:18:11.446 Starting Node-BLUE server...
04/09/19 20:18:11.522 Starting IPC server...
04/09/19 20:18:11.539 Startup complete. Waiting for physical interfaces to connect.
04/09/19 20:18:11.539 Info: Waiting for physical interfaces to connect (0 of 180s).
04/09/19 20:18:11.540 All physical interfaces are connected now.
04/09/19 20:18:11.540 Starting UPnP server...
04/09/19 20:18:11.543 Info: UPnP server: Binding to address: 192.168.0.124
04/09/19 20:18:11.544 UPnP Server: Info: Started listening.
04/09/19 20:18:15.569 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.0.150:57794 accepted. Client number: 13
04/09/19 20:18:15.571 RPC Server (Port 2001): Info: RPC server client id for client number 13 is: 0
04/09/19 20:18:19.971 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.0.136:51488 accepted. Client number: 14
04/09/19 20:18:19.972 RPC Server (Port 2001): Info: RPC server client id for client number 14 is: 1
04/09/19 20:38:10.435 IPC Server: Info: Connection accepted. Client number: 15
04/09/19 20:38:10.442 IPC Server: Info: Client 0 successfully registered RPC method "cliOutput" (this method is registered by 1 client(s)).
04/09/19 20:38:10.449 IPC Server: Info: Client 0 successfully registered RPC method "cliOutput-0" (this method is registered by 1 client(s)).
04/09/19 20:39:59.697 IPC Server: Info: Client number 0 is calling RPC method: familyExists Parameters:
(Integer64) 0
04/09/19 20:41:14.084 IPC Server: Info: Connection to IPC server's client number 15 closed.
04/09/19 20:41:16.287 IPC Server: Info: Connection accepted. Client number: 16
04/09/19 20:41:16.294 IPC Server: Info: Client 1 successfully registered RPC method "cliOutput" (this method is registered by 1 client(s)).
04/09/19 20:41:16.308 IPC Server: Info: Client 1 successfully registered RPC method "cliOutput-1" (this method is registered by 1 client(s)).
04/09/19 20:42:12.230 IPC Server: Info: IPC client 0 removed.
04/09/19 20:42:26.522 IPC Server: Info: Client number 1 is calling RPC method: familyExists Parameters:
(Integer64) 0
04/09/19 20:45:00.070 IPC Server: Response:
(String) Debug level set to 5.

04/09/19 20:45:01.650 UPnP Server: Debug: Discovery packet received from 239.255.255.250:1900
04/09/19 20:45:01.672 Debug: Sleeping 38ms before sending response.
04/09/19 20:45:01.711 UPnP Server: Debug: Sending discovery response packets to 239.255.255.250 on port 1900
04/09/19 20:45:01.813 UPnP Server: Debug: Sending notify packets.
04/09/19 20:45:07.074 UPnP Server: Debug: Discovery packet received from 239.255.255.250:1900
04/09/19 20:45:07.096 Debug: Sleeping 995ms before sending response.
04/09/19 20:45:08.092 UPnP Server: Debug: Sending discovery response packets to 239.255.255.250 on port 1900
04/09/19 20:45:08.194 UPnP Server: Debug: Sending notify packets.
04/09/19 20:45:17.000 UPnP Server: Debug: Discovery packet received from 239.255.255.250:1900
04/09/19 20:45:17.022 Debug: Sleeping 33ms before sending response.
04/09/19 20:45:17.056 UPnP Server: Debug: Sending discovery response packets to 239.255.255.250 on port 1900
04/09/19 20:45:17.158 UPnP Server: Debug: Sending notify packets.
04/09/19 20:45:20.285 IPC Server: Info: Client number 1 is calling RPC method: familyExists Parameters:
(Integer64) 0
04/09/19 20:45:20.291 IPC Server: Response:
(Boolean) 1
04/09/19 20:45:21.707 UPnP Server: Debug: Discovery packet received from 239.255.255.250:1900
04/09/19 20:45:21.729 Debug: Sleeping 2988ms before sending response.
04/09/19 20:45:24.718 UPnP Server: Debug: Sending discovery response packets to 239.255.255.250 on port 1900
04/09/19 20:45:24.820 UPnP Server: Debug: Sending notify packets.
04/09/19 20:45:27.029 UPnP Server: Debug: Discovery packet received from 239.255.255.250:1900
04/09/19 20:45:27.051 Debug: Sleeping 2258ms before sending response.
04/09/19 20:45:29.310 UPnP Server: Debug: Sending discovery response packets to 239.255.255.250 on port 1900
04/09/19 20:45:29.412 UPnP Server: Debug: Sending notify packets.
04/09/19 20:45:31.633 UPnP Server: Debug: Discovery packet received from 239.255.255.250:1900
04/09/19 20:45:31.655 Debug: Sleeping 595ms before sending response.
04/09/19 20:45:32.252 UPnP Server: Debug: Sending discovery response packets to 239.255.255.250 on port 1900
04/09/19 20:45:32.353 UPnP Server: Debug: Sending notify packets.
04/09/19 20:45:37.057 UPnP Server: Debug: Discovery packet received from 239.255.255.250:1900
04/09/19 20:45:37.095 Debug: Sleeping 15ms before sending response.
04/09/19 20:45:37.112 UPnP Server: Debug: Sending discovery response packets to 239.255.255.250 on port 1900
04/09/19 20:45:37.214 UPnP Server: Debug: Sending notify packets.
04/09/19 20:45:41.662 UPnP Server: Debug: Discovery packet received from 239.255.255.250:1900
04/09/19 20:45:41.684 Debug: Sleeping 3296ms before sending response.
04/09/19 20:45:44.981 UPnP Server: Debug: Sending discovery response packets to 239.255.255.250 on port 1900
04/09/19 20:45:45.083 UPnP Server: Debug: Sending notify packets.
04/09/19 20:45:45.688 IPC Server: Info: Client number 1 is calling RPC method: cliFamilyCommand
(Integer64) 0
(String) pairing on
04/09/19 20:45:45.689 IPC Server: Debug: CLI client 1 is executing family command: pairing on
04/09/19 20:45:45.693 IPC Server: Response:
(String) Pairing mode enabled for 60 seconds.

04/09/19 20:45:46.983 UPnP Server: Debug: Discovery packet received from 239.255.255.250:1900
04/09/19 20:45:47.005 Debug: Sleeping 3125ms before sending response.
04/09/19 20:45:50.131 UPnP Server: Debug: Sending discovery response packets to 239.255.255.250 on port 1900
04/09/19 20:45:50.233 UPnP Server: Debug: Sending notify packets.
04/09/19 20:45:51.690 UPnP Server: Debug: Discovery packet received from 239.255.255.250:1900
04/09/19 20:45:51.712 Debug: Sleeping 4381ms before sending response.
04/09/19 20:45:56.095 UPnP Server: Debug: Sending discovery response packets to 239.255.255.250 on port 1900
04/09/19 20:45:56.206 UPnP Server: Debug: Sending notify packets.
04/09/19 20:45:57.012 UPnP Server: Debug: Discovery packet received from 239.255.255.250:1900
04/09/19 20:45:57.034 Debug: Sleeping 2639ms before sending response.
04/09/19 20:45:59.674 UPnP Server: Debug: Sending discovery response packets to 239.255.255.250 on port 1900
04/09/19 20:45:59.776 UPnP Server: Debug: Sending notify packets.
04/09/19 20:46:01.617 UPnP Server: Debug: Discovery packet received from 239.255.255.250:1900
04/09/19 20:46:01.639 Debug: Sleeping 937ms before sending response.
04/09/19 20:46:02.578 UPnP Server: Debug: Sending discovery response packets to 239.255.255.250 on port 1900
04/09/19 20:46:02.680 UPnP Server: Debug: Sending notify packets.
04/09/19 20:46:07.040 UPnP Server: Debug: Discovery packet received from 239.255.255.250:1900
04/09/19 20:46:07.062 Debug: Sleeping 1975ms before sending response.
04/09/19 20:46:09.039 UPnP Server: Debug: Sending discovery response packets to 239.255.255.250 on port 1900
04/09/19 20:46:09.141 UPnP Server: Debug: Sending notify packets.
04/09/19 20:46:11.645 UPnP Server: Debug: Discovery packet received from 239.255.255.250:1900
04/09/19 20:46:11.667 Debug: Sleeping 938ms before sending response.
04/09/19 20:46:12.606 UPnP Server: Debug: Sending discovery response packets to 239.255.255.250 on port 1900
04/09/19 20:46:12.716 UPnP Server: Debug: Sending notify packets.
04/09/19 20:46:16.973 UPnP Server: Debug: Discovery packet received from 239.255.255.250:1900
04/09/19 20:46:16.995 Debug: Sleeping 161ms before sending response.
04/09/19 20:46:17.158 UPnP Server: Debug: Sending discovery response packets to 239.255.255.250 on port 1900
04/09/19 20:46:17.260 UPnP Server: Debug: Sending notify packets.
04/09/19 20:46:21.674 UPnP Server: Debug: Discovery packet received from 239.255.255.250:1900
04/09/19 20:46:21.695 Debug: Sleeping 4009ms before sending response.
04/09/19 20:46:25.706 UPnP Server: Debug: Sending discovery response packets to 239.255.255.250 on port 1900
04/09/19 20:46:25.808 UPnP Server: Debug: Sending notify packets.
04/09/19 20:46:26.995 UPnP Server: Debug: Discovery packet received from 239.255.255.250:1900
04/09/19 20:46:27.022 Debug: Sleeping 15ms before sending response.
04/09/19 20:46:27.039 UPnP Server: Debug: Sending discovery response packets to 239.255.255.250 on port 1900
04/09/19 20:46:27.141 UPnP Server: Debug: Sending notify packets.
04/09/19 20:46:31.702 UPnP Server: Debug: Discovery packet received from 239.255.255.250:1900
04/09/19 20:46:31.724 Debug: Sleeping 4249ms before sending response.
04/09/19 20:46:35.975 UPnP Server: Debug: Sending discovery response packets to 239.255.255.250 on port 1900
04/09/19 20:46:36.076 UPnP Server: Debug: Sending notify packets.
04/09/19 20:46:37.023 UPnP Server: Debug: Discovery packet received from 239.255.255.250:1900
04/09/19 20:46:37.045 Debug: Sleeping 2760ms before sending response.
04/09/19 20:46:39.807 UPnP Server: Debug: Sending discovery response packets to 239.255.255.250 on port 1900
04/09/19 20:46:39.919 UPnP Server: Debug: Sending notify packets.
04/09/19 20:46:41.628 UPnP Server: Debug: Discovery packet received from 239.255.255.250:1900
04/09/19 20:46:41.649 Debug: Sleeping 2346ms before sending response.
04/09/19 20:46:43.996 UPnP Server: Debug: Sending discovery response packets to 239.255.255.250 on port 1900
04/09/19 20:46:44.096 UPnP Server: Debug: Sending notify packets.
04/09/19 20:46:47.052 UPnP Server: Debug: Discovery packet received from 239.255.255.250:1900
04/09/19 20:46:47.073 Debug: Sleeping 3227ms before sending response.
04/09/19 20:46:50.300 UPnP Server: Debug: Sending discovery response packets to 239.255.255.250 on port 1900
04/09/19 20:46:50.401 UPnP Server: Debug: Sending notify packets.
04/09/19 20:46:57.080 UPnP Server: Debug: Discovery packet received from 239.255.255.250:1900
04/09/19 20:46:57.101 Debug: Sleeping 2840ms before sending response.
04/09/19 20:46:59.942 UPnP Server: Debug: Sending discovery response packets to 239.255.255.250 on port 1900
04/09/19 20:47:00.048 UPnP Server: Debug: Sending notify packets.
04/09/19 20:47:01.685 UPnP Server: Debug: Discovery packet received from 239.255.255.250:1900
04/09/19 20:47:01.706 Debug: Sleeping 4265ms before sending response.
04/09/19 20:47:05.972 UPnP Server: Debug: Sending discovery response packets to 239.255.255.250 on port 1900
04/09/19 20:47:06.072 UPnP Server: Debug: Sending notify packets.
04/09/19 20:47:07.007 UPnP Server: Debug: Discovery packet received from 239.255.255.250:1900
04/09/19 20:47:07.027 Debug: Sleeping 219ms before sending response.
04/09/19 20:47:07.247 UPnP Server: Debug: Sending discovery response packets to 239.255.255.250 on port 1900
04/09/19 20:47:07.348 UPnP Server: Debug: Sending notify packets.
04/09/19 20:47:11.714 UPnP Server: Debug: Discovery packet received from 239.255.255.250:1900
04/09/19 20:47:11.735 Debug: Sleeping 3096ms before sending response.
04/09/19 20:47:14.831 UPnP Server: Debug: Sending discovery response packets to 239.255.255.250 on port 1900
04/09/19 20:47:14.932 UPnP Server: Debug: Sending notify packets.
04/09/19 20:47:17.035 UPnP Server: Debug: Discovery packet received from 239.255.255.250:1900
04/09/19 20:47:17.064 Debug: Sleeping 1238ms before sending response.
04/09/19 20:47:18.302 UPnP Server: Debug: Sending discovery response packets to 239.255.255.250 on port 1900
04/09/19 20:47:18.403 UPnP Server: Debug: Sending notify packets.
04/09/19 20:47:21.641 UPnP Server: Debug: Discovery packet received from 239.255.255.250:1900
04/09/19 20.....

Danke

#2

Hey @grasgruen.it,

ist schon mal ein gutes Zeichen… deine Config sieht auch richtig aus. centralAddress und rfKey hast du wahrscheinlich auch richtig konfiguriert, oder?

Gib mal bitte den Output von cat /etc/issue und mach mal ein Foto, wie das Modul auf dem Pi steckt.
Kannst du sicherstellen, dass dein HM-Sec-Key-S funktioniert? Hast du eventuell noch ein anderes Homematic-Gerät?
Den HM-Sec-Key hab ich ohne Problem mit homegear laufen: https://allgeek.de/2017/10/05/node-red-in-verbindung-mit-loxone/ (Loxone-Kontext)

Gruß,
p

#3

Hallo p,

danke für die rasche Antwort. Den Türschlossantrieb konnte ich zumindest mit dem inkludierten Funk-Handsender erfolgreich koppeln. Ansonsten habe ich bisher kein HM Gerät.

Beiliegend ein Bild vom installierten Modul.

pi@hso:~ $ cat /etc/issue
Raspbian GNU/Linux 9 \n \l

Die Keys habe ich nach folgendem Schema konfiguriert (aus Sicherheitsgründen hier abgeändert):
centralAddress = 0xFAB122
rfKey = AA12BB23CC45DD67EE89FF6677889900

IMG_20190410_082412
IMG_20190410_082412.jpg2862×2146 1.81 MB

Danke für die Unterstützung

#4

Ok, das sieht zumindest alles gut aus.

Hast du SPI per raspi-config aktiviert und danach rebootet?
pon zum pairen über die Homegear-Konsole hast du gemacht? Weil in deinem Log sind halt wirklich gar keine Pakete zu sehen.
Versuch doch mal deinen Handsender anzulernen. Bzw, mit dl 5 solltest du zumindest ein Paket sehen, wenn du auf einen Knopf drückst.

#5

Genau weiß ich nicht warum, aber nun konnte ich sowohl den Handsender, also auch den Türschlossantrieb anlernen. Ich glaube der Antrieb hatte erst ein Anlernpaket gesendet als ich am Sender eine Taste gedrückt habe.

Egal - danke für die Hilfe. Nun kann ich weiter vorgehen.

1 Like
#6