HM-MOD-RPI-PCB und Homegear und openHAB2 auf Raspberry PI3

Deutsche Foren Installation
#1

Hallo,

ich versuche nun schon seit einigen Tagen HM-MOD-RPI-PCB an meinen Raspberry PI 3 mit Homegear und openHAB2 zum laufen zu bringen.
Bei der Installation habe ich mich an die Homegear Dokumentation gehalten. Alles mehrfach ĂŒberprĂŒft und alle BeitrĂ€ge egelesen die ich finden kann.
Meine HM-MOD-RPI-PCB ist mit der Firmware ./flash-hmmoduart -U /dev/ttyAMA0 coprocessor_update.eq3 geupdated.
Das Modul ist ĂŒbrigens funktionsfĂ€hig (Ich hatte es zwischenzeitlich mit einem RaspberryMatic Image getestet).
Wenn ich den pairing mode (pon) an beiden GerÀten aktiviere, laufen die 60/30 Sekunden ab, aber in meiner Liste (ls) ist nichts zu finden (No peers are paired to this central) .

Als Ausgangspunkt ist ein openHabian Image installiert mit dem ich HomeGear installiert habe.

Serielle Consolen sind deaktiviert. Die homematicbidcos.conf sieht genau so aus wie in der Anleitung beschrieben

id = My-HM-MOD-RPI-PCB
default = true
deviceType = hm-mod-rpi-pcb
device = /dev/ttys0
gpio1 = 18

Ein “sudo chown homegear:homegear /dev/ttyAMA0” ĂŒberlebt aber einen neustart nicht.
Es steht wieder auf root:dialout anschließend.

Hat da evtl. jmd eine Idee? WĂ€re fĂŒr jede Hilfe dankbar.
mfg
Klaus

#######
[21:53:55] openhabian@openHABianPi:~$ cat /etc/issue
Raspbian GNU/Linux 9 \n \l
#######
[21:55:17] openhabian@openHABianPi:~$ homegear -v
Homegear version 0.7.19-1846
Copyright © 2013-2018 Homegear GmbH

Git commit SHA of libhomegear-base: -
Git branch of libhomegear-base:     -
Git commit SHA of Homegear:         -
Git branch of Homegear:             -

PHP (License: PHP License):
This product includes PHP software, freely available from <http://www.php.net/software/>
Copyright (c) 1999-2018 The PHP Group. All rights reserved.

#######

meine config.txt

[21:15:15] openhabian@openHABianPi:~$ cat /boot/config.txt
# For more options and information see
# http://rpf.io/configtxt
# Some settings may impact device functionality. See link above for details

# uncomment if you get no picture on HDMI for a default "safe" mode
#hdmi_safe=1

# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
#disable_overscan=1

# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16

# uncomment to force a console size. By default it will be display's size minus
# overscan.
#framebuffer_width=1280
#framebuffer_height=720

# uncomment if hdmi display is not detected and composite is being output
#hdmi_force_hotplug=1

# uncomment to force a specific HDMI mode (this will force VGA)
#hdmi_group=1
#hdmi_mode=1

# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
#hdmi_drive=2

# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
#config_hdmi_boost=4

# uncomment for composite PAL
#sdtv_mode=2

#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800

# Uncomment some or all of these to enable the optional hardware interfaces
enable_uart=1
dtparam=i2c_arm=on
#dtparam=i2s=on
dtparam=spi=on

# Uncomment this to enable the lirc-rpi module
#dtoverlay=lirc-rpi

# Additional overlays and parameters are documented /boot/overlays/README

# Enable audio (loads snd_bcm2835)
dtparam=audio=on
gpu_mem=16

dtoverlay=pi3-miniuart-bt

########
meine cmdline.txt

[21:19:51] openhabian@openHABianPi:~$ cat /boot/cmdline.txt
dwc_otg.lpm_enable=0 console=tty1 root=PARTUUID=895091fd-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait

########

homegear.log

06/13/18 21:47:28.052 Starting Homegear...
06/13/18 21:47:28.052 Homegear version 0.7.19-1846
06/13/18 21:47:28.052 Git commit SHA of libhomegear-base: -
06/13/18 21:47:28.052 Git branch of libhomegear-base:     -
06/13/18 21:47:28.052 Git commit SHA of Homegear:         -
06/13/18 21:47:28.052 Git branch of Homegear:             -
06/13/18 21:47:28.053 Info: Setting allowed core file size to "4294967295" for user with id 0 and group with id 0.
06/13/18 21:47:28.053 Info: Core file size now is "4294967295".
06/13/18 21:47:28.053 Info: Setting maximum thread priority to "4294967295" for user with id 0 and group with id 0.
06/13/18 21:47:28.053 Info: Maximum thread priority now is "4294967295".
06/13/18 21:47:28.160 Info: Backing up database...
06/13/18 21:47:29.441 Initializing database...
06/13/18 21:47:29.487 Info: Loading family module mod_homematicbidcos.so
06/13/18 21:47:29.545 /etc/homegear/families/homematicbidcos.conf
06/13/18 21:47:29.612 Info: Loading family module mod_miscellaneous.so
06/13/18 21:47:29.635 /etc/homegear/families/miscellaneous.conf
06/13/18 21:47:29.635 Info: Loading family module mod_homematicwired.so
06/13/18 21:47:29.679 /etc/homegear/families/homematicwired.conf
06/13/18 21:47:29.689 Info: Setting up physical interfaces and GPIOs...
06/13/18 21:47:29.695 Info: Dropping privileges to user homegear (110) and group homegear (115)
06/13/18 21:47:29.695 Info: Homegear is (now) running as user with id 110 and group with id 115.
06/13/18 21:47:29.719 Starting script engine server...
06/13/18 21:47:29.733 Initializing licensing controller...
06/13/18 21:47:29.734 Loading licensing controller data...
06/13/18 21:47:29.734 Loading devices...
06/13/18 21:47:29.734 Loading XML RPC devices...
06/13/18 21:47:31.292 Loading device 1
06/13/18 21:47:31.293 Module HomeMatic BidCoS: Info: Central address set to 0xFD073E.
06/13/18 21:47:31.315 Loading XML RPC devices...
06/13/18 21:47:31.418 Loading device 2
06/13/18 21:47:31.424 Loading XML RPC devices...
06/13/18 21:47:31.432 Loading device 3
06/13/18 21:47:31.433 Initializing RPC client...
06/13/18 21:47:31.433 Starting XML RPC server RPCServer1 listening on :::2001...
06/13/18 21:47:31.436 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.
06/13/18 21:47:31.437 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.
06/13/18 21:47:31.437 Starting XML RPC server RPCServer2 listening on :::2002, SSL enabled...
06/13/18 21:47:31.438 RPC Server (Port 2001): Info: RPC Server started listening on address :: and port 2001
06/13/18 21:47:31.441 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.
06/13/18 21:47:31.516 Starting XML RPC server RPCServer3 listening on :::2003, SSL enabled, authentication enabled...
06/13/18 21:47:31.518 RPC Server (Port 2002): Info: RPC Server started listening on address :: and port 2002
06/13/18 21:47:31.550 Starting CLI server...
06/13/18 21:47:31.550 RPC Server (Port 2003): Info: RPC Server started listening on address :: and port 2003
06/13/18 21:47:31.550 Initializing event handler...
06/13/18 21:47:31.550 Loading events...
06/13/18 21:47:31.551 Start listening for packets...
06/13/18 21:47:31.551 Starting Node-BLUE server...
06/13/18 21:47:31.561 Starting IPC server...
06/13/18 21:47:31.565 Startup complete. Waiting for physical interfaces to connect.
06/13/18 21:47:31.566 Info: Waiting for physical interfaces to connect (0 of 180s).
06/13/18 21:47:31.566 All physical interfaces are connected now.
06/13/18 21:47:31.566 Starting UPnP server...
06/13/18 21:47:31.567 Info: UPnP server: Binding to address: 192.168.2.51
06/13/18 21:47:31.567 UPnP Server: Info: Started listening.
06/13/18 21:48:31.138 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.2.9:41799 accepted. Client number: 8
06/13/18 21:48:31.138 RPC Server (Port 2001): Info: RPC server client id for client number 8 is: 0
06/13/18 21:48:35.701 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.2.9:41809 accepted. Client number: 9
06/13/18 21:48:35.702 RPC Server (Port 2001): Info: RPC server client id for client number 9 is: 1
06/13/18 21:48:36.014 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.2.9:41810 accepted. Client number: 10
06/13/18 21:48:36.014 RPC Server (Port 2001): Info: RPC server client id for client number 10 is: 2
06/13/18 21:48:38.084 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.2.51:42374 accepted. Client number: 11
06/13/18 21:48:38.084 RPC Server (Port 2001): Info: RPC server client id for client number 11 is: 3
06/13/18 21:48:38.091 RPC Server (Port 2001): Info: Client number 11 is calling RPC method: getDeviceDescription (1) Parameters:
(String) BidCoS-RF
06/13/18 21:48:38.164 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.2.51:42378 accepted. Client number: 12
06/13/18 21:48:38.164 RPC Server (Port 2001): Info: RPC server client id for client number 12 is: 4
06/13/18 21:48:38.167 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: listBidcosInterfaces (1) Parameters:
06/13/18 21:48:38.429 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.2.51:42390 accepted. Client number: 13
06/13/18 21:48:38.429 RPC Server (Port 2001): Info: RPC server client id for client number 13 is: 5
06/13/18 21:48:38.433 RPC Server (Port 2001): Info: Client number 13 is calling RPC method: init (2) Parameters:
(String) binary://192.168.2.51:9126
(String) RF-c28e855a
(Integer) 34
06/13/18 21:48:38.433 Info: Client with IP ::ffff:192.168.2.51 is calling "init".
06/13/18 21:48:38.434 Info: Adding server "binary://192.168.2.51".
06/13/18 21:48:38.435 Info: Calling init methods on server "binary://192.168.2.51".
06/13/18 21:48:38.482 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.2.51:42392 accepted. Client number: 14
06/13/18 21:48:38.483 RPC Server (Port 2001): Info: RPC server client id for client number 14 is: 6
06/13/18 21:48:38.484 RPC Server (Port 2001): Info: Client number 14 is calling RPC method: listDevices (2) Parameters:
06/13/18 21:48:38.498 RPC Server (Port 2001): Info: Client number 14 is calling RPC method: getDeviceInfo (2) Parameters:
06/13/18 21:48:38.503 RPC Server (Port 2001): Info: Client number 14 is calling RPC method: getAllSystemVariables (2) Parameters:
06/13/18 21:48:38.518 RPC Server (Port 2001): Info: Client number 14 is calling RPC method: getAllScripts (2) Parameters:
06/13/18 21:48:38.589 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.2.9:41815 accepted. Client number: 15
06/13/18 21:48:38.589 RPC Server (Port 2001): Info: RPC server client id for client number 15 is: 7
06/13/18 21:48:40.828 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.2.9:41818 accepted. Client number: 17
06/13/18 21:48:40.828 RPC Server (Port 2001): Info: RPC server client id for client number 17 is: 8
06/13/18 21:48:43.135 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.2.9:41821 accepted. Client number: 18
06/13/18 21:48:43.136 RPC Server (Port 2001): Info: RPC server client id for client number 18 is: 9
06/13/18 21:48:44.977 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.2.9:41824 accepted. Client number: 19
06/13/18 21:48:44.978 RPC Server (Port 2001): Info: RPC server client id for client number 19 is: 10
06/13/18 21:48:45.249 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.2.9:41825 accepted. Client number: 20
06/13/18 21:48:45.249 RPC Server (Port 2001): Info: RPC server client id for client number 20 is: 11
06/13/18 21:48:45.588 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.2.9:41827 accepted. Client number: 21
06/13/18 21:48:45.588 RPC Server (Port 2001): Info: RPC server client id for client number 21 is: 12
06/13/18 21:48:47.946 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.2.9:41834 accepted. Client number: 22
06/13/18 21:48:47.947 RPC Server (Port 2001): Info: RPC server client id for client number 22 is: 13
06/13/18 21:48:50.083 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.2.9:41837 accepted. Client number: 23
06/13/18 21:48:50.084 RPC Server (Port 2001): Info: RPC server client id for client number 23 is: 14
06/13/18 21:49:08.638 RPC Server (Port 2001): Info: Client number 14 is calling RPC method: ping (2) Parameters:
(String) c28e855a
06/13/18 21:49:23.646 RPC Server (Port 2001): Info: Client number 14 is calling RPC method: ping (2) Parameters:
(String) c28e855a
06/13/18 21:49:38.651 RPC Server (Port 2001): Info: Client number 14 is calling RPC method: ping (2) Parameters:
(String) c28e855a
06/13/18 21:49:49.457 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.2.9:41910 accepted. Client number: 27
06/13/18 21:49:49.458 RPC Server (Port 2001): Info: RPC server client id for client number 27 is: 15
06/13/18 21:49:53.654 RPC Server (Port 2001): Info: Client number 14 is calling RPC method: ping (2) Parameters:
(String) c28e855a
06/13/18 21:50:08.658 RPC Server (Port 2001): Info: Client number 14 is calling RPC method: ping (2) Parameters:
(String) c28e855a
06/13/18 21:50:23.662 RPC Server (Port 2001): Info: Client number 14 is calling RPC method: ping (2) Parameters:
(String) c28e855a
06/13/18 21:50:38.666 RPC Server (Port 2001): Info: Client number 14 is calling RPC method: ping (2) Parameters:
(String) c28e855a
06/13/18 21:50:49.143 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.2.9:41999 accepted. Client number: 32
06/13/18 21:50:49.143 RPC Server (Port 2001): Info: RPC server client id for client number 32 is: 16
06/13/18 21:50:53.670 RPC Server (Port 2001): Info: Client number 14 is calling RPC method: ping (2) Parameters:
(String) c28e855a
06/13/18 21:51:08.674 RPC Server (Port 2001): Info: Client number 14 is calling RPC method: ping (2) Parameters:
(String) c28e855a
06/13/18 21:51:23.678 RPC Server (Port 2001): Info: Client number 14 is calling RPC method: ping (2) Parameters:
(String) c28e855a
06/13/18 21:51:38.682 RPC Server (Port 2001): Info: Client number 14 is calling RPC method: ping (2) Parameters:
(String) c28e855a
06/13/18 21:51:49.319 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.2.9:42075 accepted. Client number: 37
06/13/18 21:51:49.319 RPC Server (Port 2001): Info: RPC server client id for client number 37 is: 17
06/13/18 21:51:53.686 RPC Server (Port 2001): Info: Client number 14 is calling RPC method: ping (2) Parameters:
(String) c28e855a
06/13/18 21:52:08.690 RPC Server (Port 2001): Info: Client number 14 is calling RPC method: ping (2) Parameters:
(String) c28e855a
06/13/18 21:52:23.694 RPC Server (Port 2001): Info: Client number 14 is calling RPC method: ping (2) Parameters:
[21:52:28] openhabian@openHABianPi:~$

########

homegear.err

06/13/18 21:47:31.436 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.
06/13/18 21:47:31.437 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.
06/13/18 21:47:31.441 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.

#########

#2

Gib mal bitte den Teil deiner homematicbidcos.conf komplett
 vor allem den mi []


Das Log sagt All physical interfaces are connected now. von daher ist das alles Ordnung. Ich vermute, dass du [HomeMatic Wireless Module for Raspberry Pi] nicht einkommentiert hast :slight_smile:

#3

Hallo pmayer
danke fĂŒr die Antwort. Es beruhigt ein wenig, das es soweit gut aussieht, und ich dann doch was gelernt habe bei der ganzen Leserei.

hier meine kpl. HomeMatic BidCoS. Bekam ich nicht via Potty kpl. zu fassen und habe sie daher per FTP auf meinen PC erst runtergeladen. Bin schon lÀnger nicht mehr in Linux unterwegs gewesen und habe die Consolenbefehle nicht so parat.

___________________________________________________________________________

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

## 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 = 0123A3B2C6455678899A4B7BAC1D7EF5

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

#######################################
########## Homegear Gateway  ##########
#######################################

## The device family this interface is for
#[Homegear Gateway]

## Specify an unique id here to identify this device in Homegear
#id = My-HG-GW

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

## The host name or IP address of the gateway
#host = 

## The port of the gateway
#port = 2017

## The CA certificate
#caFile = /etc/homegear/ca/cacert.pem

## The client certificate
#certFile = /etc/homegear/ca/certs/gateway-client.crt

## The client key file
#keyFile = /etc/homegear/ca/private/gateway-client.key

## Use the ID defined above to verify the common name of the certificate
## Default: false
#useIdForHostnameVerification = true

## Default: responseDelay = 95
## Should be "95" for CUL or COC, "100" for TI CC1101, "98" for Homegear Gateway and "60" for HM-CFG-LAN or HM-LGW
#responseDelay = 98

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

Und da ist dein Problem :wink:
Das # am Anfang muss weg, damit die Sektion einkommentiert ist. Homegear weiß gerade nichts von irgend einer Hardware fĂŒr Homematic, da keine Sektion einkommentiert ist.

Außerdem “musst” du eine centralAddress definieren und du solltest außerdem nicht den Beispiel-rfKey nehmen.
Leß am besten mal hier worum es da geht: Grundlagen Homegear / Starter-Guide - vor allem ab “Konfiguration”.

#5

Hallo pmayer
Jetzt wo ich es lese, zu erkennen am einfachen #. Da werde ich dann die Anleitungen nochmal ddurchforsten, ob die Zeile bei den Beispielen auch ohne # vorkommen. Die hatte ich gedanklich als Teil der ErklÀrungen (## markiert) angesehen.
Ich werde berichten.
Aber das ist weder die Standard centralAddress in meiner .conf, noch ist das der rfKey aus den Beispielen.

#6

Ooops. 0123... suggerierte das. Trotzdem muss du aber die Zeile mit der centralAddress einkommentieren, also ohne # davor.
Deine “echten” rfKey solltest du ĂŒbrigens nicht öffentlich posten


Hier mal als Beispiel wie die config ausreichend wÀre:

[General]
centralAddress = 0xFD5D95
rfKey = 0123A3B2C6455678899A4B7BAC1D7EF5
currentRfKeyIndex = 1
processBroadcastWithAesEnabled = false

[HomeMatic Wireless Module for Raspberry Pi]
id = My-HM-MOD-RPI-PCB
default = true
deviceType = hm-mod-rpi-pcb
device = /dev/ttyAMA0
responseDelay = 95
gpio1 = 18
1 Like
#7

Ja wenn schon nicht einkommentiert dann richtig :grinning:
Was soll ich sagen. Kaum macht man’s richtig, funktioniert es.
Es ist schon komisch, wie man trotz mehrfachen durchlesen sowas nicht sieht


DANKE fĂŒr die Hilfe, werde dann bis zum nĂ€chsten Problem weiter machen.
Jetz ist dann wohl openHAB dran.

1 Like
#8