Hallo,
ich habe leider auch diesen Fehler:
root@raspberrypi:/var/lib/homegear# homegear -r
04/04/16 20:23:42.415 Could not connect to socket. Error: No such file or directory
04/04/16 20:23:42.416 Could not connect to socket. Error: No such file or directory
Ich habe homegear frisch auf raspbian installiert und habe folgende Dateien von meinem alten raspberry pi über den laptop auf den neuen geschoben:
[ul]
db.sql
db.sql.bak
ordner scripts
main.conf
physicalinterfaces.conf
[/ul]
Ich hatte schonmal bei einer anderen Sache Probleme mit den Rechten als ich Dateien vom Mac auf den Raspberry geschoben habe, daher vermute ich auch hier das Problem.
Hier die Rechte:
pi@raspberrypi:~/homegear $ ls -al /etc/homegear/
insgesamt 56
drwxr-xr-x 3 root root 4096 Apr 4 19:32 .
drwxr-xr-x 111 root root 4096 Apr 4 19:32 ..
drwxr-xr-x 8 root root 4096 Apr 4 19:27 devices
-r-------- 1 homegear homegear 827 Apr 4 19:32 dh1024.pem
-rw-r--r-- 1 root root 1111 Apr 4 19:27 homegear.crt
-r-------- 1 homegear homegear 1675 Apr 4 19:27 homegear.key
-rw-r--r-- 1 homegear homegear 5432 Apr 4 19:59 main.conf
-rw-r--r-- 1 homegear homegear 11492 Apr 4 20:09 physicalinterfaces.conf
-r--r----- 1 homegear homegear 1458 Jun 13 2015 rpcclients.conf
-rw-r--r-- 1 root root 4880 Jun 13 2015 rpcservers.conf
pi@raspberrypi:~/homegear $ ls -al /etc/homegear/
insgesamt 56
drwxr-xr-x 3 root root 4096 Apr 4 19:32 .
drwxr-xr-x 111 root root 4096 Apr 4 19:32 ..
drwxr-xr-x 8 root root 4096 Apr 4 19:27 devices
-r-------- 1 homegear homegear 827 Apr 4 19:32 dh1024.pem
-rw-r--r-- 1 root root 1111 Apr 4 19:27 homegear.crt
-r-------- 1 homegear homegear 1675 Apr 4 19:27 homegear.key
-rw-r--r-- 1 homegear homegear 5432 Apr 4 19:59 main.conf
-rw-r--r-- 1 homegear homegear 11492 Apr 4 20:09 physicalinterfaces.conf
-r--r----- 1 homegear homegear 1458 Jun 13 2015 rpcclients.conf
-rw-r--r-- 1 root root 4880 Jun 13 2015 rpcservers.conf
Liegt da irgendwo ein Fehler vor?
Ansonsten hier nochmal die physicalinterfaces.conf:
[code]___________________________________________________________________________
---------------------------- HomeMatic BidCoS ----------------------------
#######################################
################# CUL #################
#######################################
The device family this interface is for
#[HomeMaticBidCoS]
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
#[HomeMaticBidCoS]
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
Specify a 16 byte (32 characters) long AES key here to protect your wireless communication
!!! 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
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
#######################################
############# HM-CFG-LAN #############
#######################################
The device family this interface is for
#[HomeMaticBidCoS]
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
Specify a 16 byte (32 characters) long AES key here to protect your wireless communication
!!! 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. Default value is 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
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
#[HomeMaticBidCoS]
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
#[HomeMaticBidCoS]
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
#[HomeMaticBidCoS]
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 = 2
The GPIO GDO0 or GDO2 is connected to. Specify which GDO to use above.
#gpio1 = 23
----------------------------- HomeMatic Wired -----------------------------
#######################################
######### RS485 - USB Module #########
#######################################
The device family this interface is for
#[HomeMaticWired]
Specify an unique id here to identify this device in Homegear
#id = My-COC
Options: rs485, hmwlgw
#deviceType = rs485
Mostly /dev/ttyACM0 or /dev/ttyUSB0
#device = /dev/ttyUSB0
Should be “13” for serial modules, “20” for USB modules and “8” for HMW-LGW.
#responseDelay = 20
Set to “true” for USB modules
#oneWay = true
#######################################
######## RS485 - Serial Module ########
#######################################
The device family this interface is for
#[HomeMaticWired]
Specify an unique id here to identify this device in Homegear
#id = My-RS485
Options: rs485, hmwlgw
#deviceType = rs485
#device = /dev/ttyAMA0
Should be “13” for serial modules, “20” for USB modules and “8” for HMW-LGW.
#responseDelay = 13
Set to “true” for USB modules
#oneWay = false
GPIO to enable RX
#gpio1 = 22
Set GPIO to this value to enable RX
#enableRXValue = 0
GPIO to enable TX
#gpio2 = 17
Set GPIO to this value to enable TX
#enableTXValue = 1
!!!EXPERIMENTAL!!!
Reduces the time for the bus to become free from about 200 ms
to about 100 ms.
#fastSending = true
#######################################
HomeMatic Wired RS485 LAN Gateway
#######################################
The device family this interface is for
#[HomeMaticWired]
Specify an unique id here to identify this device in Homegear
#id = My-HMW-LGW
Options: rs485, hmwlgw
#deviceType = hmwlgw
IP address of your HMW-LGW
#host = 192.168.178.100
First Port number your HMW-LGW listens on. Normally 1000.
#port = 1000
Put the security key printed on your HMW-LGW here
#lanKey = SecurityKey
Should be “13” for serial modules, “20” for USB modules and “8” for HMW-LGW.
#responseDelay = 8
--------------------------------- INSTEON ---------------------------------
#######################################
########### Insteon Hub X10 ###########
#######################################
The device family this interface is for
#[INSTEON]
Specify an unique id here to identify this device in Homegear
#id = My-Hub
Options: insteonhubx10
#deviceType = insteonhubx10
IP address of your hub
#host = 192.168.178.100
Port number your hub listens on. Normally 9761.
#port = 9761
Should be “100”
#responseDelay = 100
---------------------------------- MAX! ----------------------------------
#######################################
################# CUL #################
#######################################
The device family this interface is for
[MAX]
Specify an unique id here to identify this device in Homegear
id = My-MAX-CUL
When default is set to “true” Homegear will assign this device
to new peers.
default = true
Options: cul, coc, cc1100
deviceType = cul
device = /dev/ttyACM0
Should be “40” for MAX!
responseDelay = 40
#######################################
########## TI CC1101 Module ##########
#######################################
The device family this interface is for
#[MAX]
Specify an unique id here to identify this device in Homegear
#id = My-MAX-CC1101
When default is set to “true” Homegear will assign this device
to new peers.
#default = true
Options: cul, coc, cc1100
#deviceType = cc1100
#device = /dev/spidev0.0
Default: responseDelay = 95
Should be “40” for CUL or COC and “45” for TI CC1101.
#responseDelay = 45
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 = 23
------------------------------- Philips hue -------------------------------
#######################################
############# Hue Bridge #############
#######################################
The device family this interface is for
#[PhilipsHue]
Specify an unique id here to identify this device in Homegear
This identifier is also used as the bridge user name and “password”.
#id = My-Bridge-1234
Options: huebridge
#deviceType = huebridge
IP address of your bridge
#host = 192.168.178.100
Port number your bridge listens on. Normally 80.
#port = 80
Should be “100” for Philips hue
#responseDelay = 100
[/code]
und die main.cfg
[code]# Homegear configuration file
Default: debugLevel = 3
debugLevel = 4
Prints log information helping in fixing errors
Default: devLog = false
devLog = false
If databasePath is empty, the executable path is used
Default: databasePath =
databasePath = /var/lib/homegear/db.sql
If databaseMemoryJournal is set to true database write operations are faster but if your system
suffers a power loss the database might get corrupted.
Default: databaseMemoryJournal = true
databaseMemoryJournal = true;
If databaseSynchronous is set to false database write operations are faster but if your system
suffers a power loss the database might get corrupted.
Default: databaseSynchronous = false
databaseSynchronous = false;
Default: logfilePath = /var/log/homegear
logfilePath = /var/log/homegear
SSL options
You can create a new certificate pair with:
openssl genrsa -out /etc/homegear/homegear.key 2048
openssl req -new -key /etc/homegear/homegear.key -out /etc/homegear/homegear.csr
openssl x509 -req -in /etc/homegear/homegear.csr -signkey /etc/homegear/homegear.key -out /etc/homegear/homegear.crt
Default: certPath = /etc/homegear/homegear.crt
certPath = /etc/homegear/homegear.crt
Default: keyPath = /etc/homegear/homegear.key
keyPath = /etc/homegear/homegear.key
When “loadDHParamsFromFile” is set to “false”, Diffie-Hellman parameters will be generated when Homegear starts.
That actually is more secure, but the generation takes a long time on slow computers.
Default: loadDHParamsFromFile = true
loadDHParamsFromFile = true
Default: dhParamPath = /etc/homegear/dh1024.pem
dhParamPath = /etc/homegear/dh1024.pem
Path to device description files
Default: /etc/homegear/devices
deviceDescriptionPath = /etc/homegear/devices
Path to the RPC clients event server settings file.
Default: clientSettingsPath = /etc/homegear/rpcclients.conf
clientSettingsPath = /etc/homegear/rpcclients.conf
Path to the RPC server settings file.
Default: serverSettingsPath = /etc/homegear/rpcservers.conf
serverSettingsPath = /etc/homegear/rpcservers.conf
Path to the physical interface settings file.
Default: physicalInterfaceSettingsPath = /etc/homegear/physicalinterfaces.conf
physicalInterfaceSettingsPath = /etc/homegear/physicalinterfaces.conf
Path to the GPIO root directory. Only relevant if one of the physical devices needs GPIO access.
Default: gpioPath = /sys/class/gpio
gpioPath = /sys/class/gpio
Path to scripts which can be executed by calling “runScript”
Default: scriptPath = /var/lib/homegear/scripts
scriptPath = /var/lib/homegear/scripts
Path to the family modules.
Default: modulePath = /var/lib/homegear/modules
modulePath = /var/lib/homegear/modules
Path to the directory with firmware updates
Default: firmwarePath = /var/lib/homegear/firmware
firmwarePath = /var/lib/homegear/firmware
Some clients don’t provide the option to set their hostname to
“localhost” or “127.0.0.1” so a SSH tunnel normally wouldn’t work.
To redirect communication to a client’s XML RPC event server through a
SSH tunnel in this case, specify the client’s XML RPC server address
here. Homegear replaces the provided address (or hostname) with
127.0.0.1 (or ::1 when IPv6 is used). Multiple entries are allowed.
redirectToSSHTunnel = 192.168.0.1
redirectToSSHTunnel = fdef:abcd:bcda::1234
redirectToSSHTunnel = 192.168.0.10
redirectToSSHTunnel = MyHostname
!!!Don’t change settings below unless you know exactly what you’re doing!!!
!!!Don’t change settings below unless you know exactly what you’re doing!!!
!!!Don’t change settings below unless you know exactly what you’re doing!!!
Default: prioritizeThreads = true
prioritizeThreads = true
Default: workerThreadWindow = 3000
workerThreadWindow = 3000
Default: rpcServerMaxConnections = 50
rpcServerMaxConnections = 50
Default: rpcServerThreadPriority = 0
rpcServerThreadPriority = 0
Default: rpcServerThreadPolicy = SCHED_OTHER
Valid policies: SCHED_OTHER, SCHED_BATCH, SCHED_IDLE, SCHED_FIFO, SCHED_RR
rpcServerThreadPolicy = SCHED_OTHER
Default: rpcClientMaxThreads = 50
rpcClientMaxThreads = 50
Default: rpcClientThreadPriority = 0
rpcClientThreadPriority = 0
Default: rpcClientThreadPolicy = SCHED_OTHER
Valid policies: SCHED_OTHER, SCHED_BATCH, SCHED_IDLE, SCHED_FIFO, SCHED_RR
rpcClientThreadPolicy = SCHED_OTHER
Default: workerThreadPriority = 0
workerThreadPriority = 0
Default: workerThreadPolicy = SCHED_OTHER
Valid policies: SCHED_OTHER, SCHED_BATCH, SCHED_IDLE, SCHED_FIFO, SCHED_RR
workerThreadPolicy = SCHED_OTHER
Default: packetQueueThreadPriority = 45
packetQueueThreadPriority = 45
Default: packetQueueThreadPolicy = SCHED_FIFO
Valid policies: SCHED_OTHER, SCHED_BATCH, SCHED_IDLE, SCHED_FIFO, SCHED_RR
packetQueueThreadPolicy = SCHED_FIFO
Default: packetReceivedThreadPriority = 0
packetReceivedThreadPriority = 0
Default: packetReceivedThreadPolicy = SCHED_OTHER
Valid policies: SCHED_OTHER, SCHED_BATCH, SCHED_IDLE, SCHED_FIFO, SCHED_RR
packetReceivedThreadPolicy = SCHED_OTHER
Default: eventMaxThreads = 20
eventMaxThreads = 20
Default: eventTriggerThreadPriority = 0
eventTriggerThreadPriority = 0
Default: eventTriggerThreadPolicy = SCHED_OTHER
Valid policies: SCHED_OTHER, SCHED_BATCH, SCHED_IDLE, SCHED_FIFO, SCHED_RR
eventTriggerThreadPolicy = SCHED_OTHER[/code]
logs scheint es noch nicht zu geben.
Vielen Dank schonmal!
.