Moin,
als erste Gehversuche mit Homegear versuche ich zu Anfang einmal nur einen Homematic Thermostat per Funk zu erreichen. Ich habe folgendes Setup:
Rechner: Raspberry Pi 2 mit Raspbian 8 (vorgefertigtes Image mit Homegear und openHab)
Funkmodul: Pollin CC1101
Pinning:
Raspberry Pi Pin Header <-> Funkmodul
1 <-> +Vb
6 <-> GND
19 <-> SI
21 <-> SO
22 <-> GDO0
23 <-> CLK
24 <-> CS
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 = 0xFD0001
## 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
#######################################
################# 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, cuno, hmcfglan, hmlgw
#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, cuno, hmcfglan, hmlgw
#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.
#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, cuno, hmcfglan, hmlgw
#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, cuno, hmcfglan, hmlgw
## 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
#######################################
################ CUNO ################
#######################################
## The device family this interface is for
#[CUNO]
## Specify an unique id here to identify this device in Homegear
#id = My-CUNO
## When default is set to "true" Homegear will assign this device
## to new peers.
#default = true
## Options: cul, cc1100, coc, cuno, hmcfglan, hmlgw
#deviceType = cuno
## IP address of your CUNO
#host = 192.168.178.100
## Port number your CUNO listens on. Normally 2323.
#port = 2323
## Default: responseDelay = 95
## Should be "95" for CUNO
#responseDelay = 95
#######################################
########## 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, cuno, hmcfglan, hmlgw
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
### 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)Es gibt unter /dev die Devices spidev0.0 und spidev0.1. Ich bekomme aber beim besten Willen die SPI Kommunikation nicht zum Laufen.
Auszug aus homegear.log (interessant ist der Hinweis, dass kein Device gefunden wird):
01/01/70 01:00:06.611 /etc/homegear/families/homematicbidcos.conf
01/01/70 01:00:06.614 Debug: Loading section "General"
01/01/70 01:00:06.614 Debug: Family setting rfkey set to 00112233445566778899AABBCCDDEEFF
01/01/70 01:00:06.614 Debug: Family setting currentrfkeyindex set to 1
01/01/70 01:00:06.615 Debug: Family setting id set to My-CC1101
01/01/70 01:00:06.615 Debug: Family setting default set to true
01/01/70 01:00:06.615 Debug: Family setting devicetype set to cc1100
01/01/70 01:00:06.615 Debug: Family setting device set to /dev/spidev0.0
01/01/70 01:00:06.615 Debug: Family setting responsedelay set to 100
01/01/70 01:00:06.616 Debug: Family setting interruptpin set to 0
01/01/70 01:00:06.616 Debug: Family setting gpio1 set to 25
01/01/70 01:00:06.616 Module HomeMatic BidCoS: Debug: Loading module...
01/01/70 01:00:06.622 Info: Loading family module mod_max.so
01/01/70 01:00:06.668 /etc/homegear/families/max.conf
01/01/70 01:00:06.669 Module MAX: Debug: Loading module...
01/01/70 01:00:06.670 Info: Loading family module mod_miscellaneous.so
01/01/70 01:00:06.690 /etc/homegear/families/miscellaneous.conf
01/01/70 01:00:06.691 Module Miscellaneous: Debug: Loading module...
01/01/70 01:00:06.695 Info: Settings up physical interfaces and GPIOs...
01/01/70 01:00:06.695 Debug: Setting up physical device.
01/01/70 01:00:06.699 Info: Dropping privileges to user homegear (107) and group homegear (112)
01/01/70 01:00:06.700 Info: Homegear is (now) running as user with id 107 and group with id 112.
01/01/70 01:00:06.700 Info: Setting allowed core file size to "4294967295" for user with id 107 and group with id 112.
01/01/70 01:00:06.700 Info: Core file size now is "4294967295".
01/01/70 01:00:06.700 Info: Setting maximum thread priority to "100" for user with id 107 and group with id 112.
01/01/70 01:00:06.700 Info: Maximum thread priority now is "100".
01/01/70 01:00:07.029 Starting script engine server...
01/01/70 01:00:07.029 Script Engine Server: Debug: Waiting for script engine server's client threads to finish.
01/01/70 01:00:07.030 Warning: Time is in the past. Waiting for ntp to set the time...
01/23/16 19:36:13.499 Debug: checkHealth returned ok.
01/23/16 19:36:14.174 Info: Backing up database...
01/23/16 19:36:14.609 Initializing database...
01/23/16 19:36:14.617 Initializing licensing controller...
01/23/16 19:36:14.617 Loading licensing controller data...
01/23/16 19:36:14.617 Loading devices...
01/23/16 19:36:14.617 Info: Not initializing device family HomeMatic BidCoS, because no physical interface was found.
01/23/16 19:36:14.618 Debug: Disposing central...
01/23/16 19:36:14.618 Info: Disposing family module mod_homematicbidcos.so
01/23/16 19:36:14.618 Debug: Deleting factory pointer of module mod_homematicbidcos.so
01/23/16 19:36:14.618 Debug: Closing dynamic library module mod_homematicbidcos.so
01/23/16 19:36:14.619 Debug: Dynamic library mod_homematicbidcos.so disposed
Mir ist aufgefallen, dass es unter /sys/class/gpio keinen Link auf den GPIO25 gibt. Muss ich das händisch machen? Falls ja, mit welchen Parametern? Außerdem kann ich auf dem Pin 23 des Raspberry keinen Clock mit meinem Multimeter messen. Der müsste doch eigentlich dauerhaft aus dem RPi kommen, wenn SPI aktiviert ist, oder nicht? Fehlt da auch noch etwas?
Hat irgendjemand eine Idee, wonach ich suchen muss? Fehlt evtl. noch eine Information von mir, die zur Identifizierung des Problems nützlich oder notwendig ist?
Vielen Dank schon einmal für die Hilfe!
Timo