So, ich habe mich die Tage wieder längere Zeit damit beschäftigt und komme zu keiner Lösung. Ich hoffe die folgenden Informationen helfen Euch, damit wir gemeinsam eine Lösung finden können:
Reboot: ca. 09/29/15 08:04
pi@raspberrypi ~ $ sudo tail -n 10 /var/log/homegear/homegear.err
09/27/15 12:43:57.667 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "My-HM-CFG-LAN": Error: First packet from HM-CFG-LAN does not start with "HHM-LAN-IF" or has wrong structure. Please check your AES key in physicalinterfaces.conf. Stopping listening. Packet was: HHM-USB-IF,03C7,MEQ0231261,37333A,000000,0018B441,0000,00
09/27/15 12:43:57.667 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "My-HM-CFG-LAN": Error: First packet from HM-CFG-LAN does not start with "HHM-LAN-IF" or has wrong structure. Please check your AES key in physicalinterfaces.conf. Stopping listening. Packet was: E2E5BCF,0000,0005ABA1,FF,FFE7,0184002E5BCF0000001300954C4551303835363236375900FFFF
09/27/15 12:55:00.801 Error: At least one physical interface is not connected.
09/27/15 12:59:24.973 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "My-HM-CFG-LAN": Error: First packet from HM-CFG-LAN does not start with "HHM-LAN-IF" or has wrong structure. Please check your AES key in physicalinterfaces.conf. Stopping listening. Packet was: HHM-USB-IF,03C7,MEQ0231261,37333A,000000,0008C6FC,0000,00
09/27/15 13:05:52.043 Error: At least one physical interface is not connected.
09/27/15 13:16:27.306 Error: At least one physical interface is not connected.
09/27/15 14:13:13.122 Error: At least one physical interface is not connected.
09/27/15 14:57:41.184 Error: At least one physical interface is not connected.
09/27/15 17:45:38.595 Error: At least one physical interface is not connected.
09/28/15 20:35:45.512 Error: At least one physical interface is not connected.
pi@raspberrypi ~ $ sudo tail -n 10 /var/log/homegear/homegear.log
09/29/15 08:04:46.287 Info: Connecting to host localhost on port 1000...
09/29/15 08:05:01.340 Info: Connecting to host localhost on port 1000...
09/29/15 08:05:16.390 Info: Connecting to host localhost on port 1000...
09/29/15 08:05:31.440 Info: Connecting to host localhost on port 1000...
09/29/15 08:05:46.493 Info: Connecting to host localhost on port 1000...
09/29/15 08:06:01.547 Info: Connecting to host localhost on port 1000...
09/29/15 08:06:16.606 Info: Connecting to host localhost on port 1000...
09/29/15 08:06:31.664 Info: Connecting to host localhost on port 1000...
09/29/15 08:06:46.723 Info: Connecting to host localhost on port 1000...
09/29/15 08:07:01.783 Info: Connecting to host localhost on port 1000...
physicalinterfaces.conf
[code]#######################################
############# 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 = localhost
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[/code]
Frage: Macht es Sinn, rfKey zu verändern, um die Sicherheit zu erhöhen?
/etc/init.d/hmland
[code]#!/bin/sh
BEGIN INIT INFO
Provides: hmland
Required-Start: $localfs $syslog $remote_fs
Required-Stop:
Default-Start: 2 3 4 5
Default-Stop: 0 1 6
Short-Description: hmland daemon
Description: hmland daemon, Homematic USB Adapter on port 1234
END INIT INFO
simple init for hmland
pidfile=/var/run/hmland.pid
port=1234
case “$1” in
start|"")
chrt 50 /opt/hmcfgusb/hmland -I -d -P -l 127.0.0.1 -p $port 2>&1 | perl -ne ‘$|=1; print localtime . “: [hmland] $_”’ >> /var/log/hmland.log &
;;
restart|reload|force-reload)
echo “Error: argument ‘$1’ not supported” >&2
exit 3
;;
stop)
killall hmland
;;
status)
if [ ! -e $pidfile ]; then
echo "No pid"
exit 1
fi
pid=cat $pidfile
if kill -0 $pid &>1 > /dev/null; then
echo "Running"
exit 0
else
rm $pidfile
echo "Not running"
exit 1
fi
;;
*)
echo “Usage: hmland [start|stop|status]” >&2
exit 3
;;
esac
[/code]
Ich hatte hmland -I mal ergänzt. Er funktioniert jedoch weder mit noch ohne.
pi@raspberrypi /etc/homegear $ homegear -r
09/29/15 08:18:53.664 Could not connect to socket. Error: Permission denied
09/29/15 08:18:53.665 Could not connect to socket. Error: Permission denied
pi@raspberrypi /etc/homegear $ ^C
pi@raspberrypi /etc/homegear $ sudo homegear -r
> families select 0
Device family "HomeMatic BidCoS" selected.
For information about the family's commands type: "help"
(Family)> devices select central
Device selected.
For information about the device's commands type: "help"
(Device)> pairing on
Pairing mode enabled.
(Device)> peers list
No peers are paired to this central.
(Device)>
.
Vor dem Versucht hatte ich das Thermostat überigens zurückgesetzt.