Homegear/Openhab für Homematic funktioniert nicht mehr nach Installation Intertechno

sebami · June 18, 2017, 7:55pm

Hallo Zusammen,

Ich bin mittlerweile echt am Verzweifeln. Seit Wochen versuche ich OpenHab mit Homegear für Homematic und Intertechno stabil zum laufen zu bekommen. Als HW nutze ich zwei CUL USB Sticks, einen mit 868 und einen mit 433 MHz.

Nach vielen Versuchen und Neuinstallationen liefen die Homematickomponenten nun einige Wochen stabil. Jetzt habe ich die Intertechnounterstützung installiert und schon bricht wieder alles zusammen. Mal läuft Homegear, mal nicht. Meist muss ich dafür Homegear oder auch den kompletten Raspberry neu starten. Intertechno weiter einzurichten bin ich noch gar nicht zu gekommen… Ich habe mal diverse Logs angehängt, vielleicht kann mir ja jemand helfen!?

Vielen lieben Dank!
Sebastian

PS: Bin kein Linuxprofi und helfe mir durch lesen und probieren…

homegear

06/18/17 21:26:09.551 Loading RPC server settings from /etc/homegear/rpcservers.conf
06/18/17 21:26:09.553 Loading RPC client settings from /etc/homegear/rpcclients.conf
06/18/17 21:26:09.554 Starting Homegear...
06/18/17 21:26:09.555 Homegear version 0.7.2-1207
06/18/17 21:26:09.555 Git commit SHA of libhomegear-base: -
06/18/17 21:26:09.555 Git branch of libhomegear-base:     -
06/18/17 21:26:09.555 Git commit SHA of Homegear:         -
06/18/17 21:26:09.555 Git branch of Homegear:             -
06/18/17 21:26:09.556 Info: Setting allowed core file size to "4294967295" for user with id 0 and group with id 0.
06/18/17 21:26:09.556 Info: Core file size now is "4294967295".
06/18/17 21:26:09.556 Info: Setting maximum thread priority to "100" for user with id 0 and group with id 0.
06/18/17 21:26:09.556 Info: Maximum thread priority now is "100".
06/18/17 21:26:09.582 Info: Backing up database...
06/18/17 21:26:09.589 Can't execute "PRAGMA journal_mode=DELETE": database is locked
06/18/17 21:26:09.589 Can't execute "PRAGMA journal_mode=DELETE": database is locked
06/18/17 21:26:09.941 Initializing database...
06/18/17 21:26:09.943 Info: Loading family module mod_homematicbidcos.so
06/18/17 21:26:09.955 /etc/homegear/families/homematicbidcos.conf
06/18/17 21:26:09.956 Info: Loading family module mod_homematicwired.so
06/18/17 21:26:09.962 /etc/homegear/families/homematicwired.conf
06/18/17 21:26:09.962 Info: Loading family module mod_intertechno.so
06/18/17 21:26:09.967 /etc/homegear/families/intertechno.conf
06/18/17 21:26:09.967 Info: Loading family module mod_miscellaneous.so
06/18/17 21:26:09.971 /etc/homegear/families/miscellaneous.conf
06/18/17 21:26:09.971 Warning: Running as root. The authors of Homegear recommend running Homegear as user.
06/18/17 21:26:09.971 Warning: Running as root. The authors of Homegear recommend running Homegear as user.
06/18/17 21:26:09.971 Starting script engine server...
06/18/17 21:26:09.975 Initializing licensing controller...
06/18/17 21:26:09.975 Loading licensing controller data...
06/18/17 21:26:09.975 Loading devices...
06/18/17 21:26:09.975 Loading XML RPC devices...
06/18/17 21:26:11.116 Loading device 2
06/18/17 21:26:11.116 Module HomeMatic BidCoS: Info: Central address set to 0xFDCFBC.
06/18/17 21:26:11.117 Module HomeMatic BidCoS: Loading peer 1
06/18/17 21:26:11.131 Module HomeMatic BidCoS: Loading peer 2
06/18/17 21:26:11.145 Module HomeMatic BidCoS: Loading peer 3
06/18/17 21:26:11.159 Info: Not initializing device family HomeMatic Wired, because no physical interface was found.
06/18/17 21:26:11.159 Info: Disposing family module mod_homematicwired.so
06/18/17 21:26:11.160 Loading XML RPC devices...
06/18/17 21:26:11.164 Loading device 3
06/18/17 21:26:11.165 Loading XML RPC devices...
06/18/17 21:26:11.167 Loading device 1
06/18/17 21:26:11.167 Initializing RPC client...
06/18/17 21:26:11.167 Starting XML RPC server RPCServer1 listening on :::2001...
06/18/17 21:26:11.170 Starting XML RPC server RPCServer2 listening on :::2002, SSL enabled...
06/18/17 21:26:11.170 RPC Server (Port 2001): Error: Server could not start listening on port 2001: Address already in use
06/18/17 21:26:11.170 RPC Server (Port 2001): Error: Server could not start listening on port 2001: Address already in use
06/18/17 21:26:11.202 Starting XML RPC server RPCServer3 listening on :::2003, SSL enabled, authentication enabled...
06/18/17 21:26:11.202 RPC Server (Port 2002): Error: Server could not start listening on port 2002: Address already in use
06/18/17 21:26:11.202 RPC Server (Port 2002): Error: Server could not start listening on port 2002: Address already in use
06/18/17 21:26:11.233 Starting CLI server...
06/18/17 21:26:11.234 RPC Server (Port 2003): Error: Server could not start listening on port 2003: Address already in use
06/18/17 21:26:11.234 RPC Server (Port 2003): Error: Server could not start listening on port 2003: Address already in use
06/18/17 21:26:11.234 Initializing event handler...
06/18/17 21:26:11.234 Loading events...
06/18/17 21:26:11.237 Starting flows server...
06/18/17 21:26:11.238 Starting IPC server...
06/18/17 21:26:11.241 Start listening for packets...
06/18/17 21:26:13.649 Startup complete. Waiting for physical interfaces to connect.
06/18/17 21:26:13.650 All physical interfaces are connected now.
06/18/17 21:26:13.650 Starting UPnP server...
06/18/17 21:26:13.652 Info: UPnP server: Binding to address: 192.168.178.31
06/18/17 21:26:13.652 Error: A core file exists in Homegear's working directory ("/var/lib/homegear/core"). Please send this file to the Homegear team including information about your system (Linux distribution, CPU architecture), the Homegear version, the current log files and information what might've caused the error.
06/18/17 21:26:13.652 Error: A core file exists in Homegear's working directory ("/var/lib/homegear/core"). Please send this file to the Homegear team including information about your system (Linux distribution, CPU architecture), the Homegear version, the current log files and information what might've caused the error.
06/18/17 21:26:13.652 UPnP Server: Info: Started listening.
06/18/17 21:26:16.170 RPC Server (Port 2001): Error: Server could not start listening on port 2001: Address already in use

homegear.err

05/17/17 10:34:50.823 Warning: No database found. Trying to restore backup.
05/17/17 10:34:51.049 Warning: Database could not be restored. Creating new database.
05/17/17 10:37:24.716 Could not set owner for device /dev/ttyUSB0: No such file or directory
05/17/17 10:37:24.716 Could not set permissions for device /dev/ttyUSB0: No such file or directory
05/17/17 10:37:26.256 Module HomeMatic BidCoS: CUL "My-CUL": Couldn't open CUL device "/dev/ttyUSB0": No such file or directory
05/17/17 10:37:26.256 Critical: At least one of the physical devices could not be opened... Exiting...
05/17/17 10:37:29.767 Could not set owner for device /dev/ttyUSB0: No such file or directory
05/17/17 10:37:29.767 Could not set permissions for device /dev/ttyUSB0: No such file or directory
05/17/17 10:37:30.952 Module HomeMatic BidCoS: CUL "My-CUL": Couldn't open CUL device "/dev/ttyUSB0": No such file or directory
05/17/17 10:37:30.952 Critical: At least one of the physical devices could not be opened... Exiting...
05/17/17 10:37:35.092 Could not set owner for device /dev/ttyUSB0: No such file or directory
05/17/17 10:37:35.092 Could not set permissions for device /dev/ttyUSB0: No such file or directory
05/17/17 10:37:36.304 Module HomeMatic BidCoS: CUL "My-CUL": Couldn't open CUL device "/dev/ttyUSB0": No such file or directory
05/17/17 10:37:36.304 Critical: At least one of the physical devices could not be opened... Exiting...
05/17/17 10:37:40.256 Could not set owner for device /dev/ttyUSB0: No such file or directory
05/17/17 10:37:40.256 Could not set permissions for device /dev/ttyUSB0: No such file or directory
05/17/17 10:37:41.443 Module HomeMatic BidCoS: CUL "My-CUL": Couldn't open CUL device "/dev/ttyUSB0": No such file or directory
05/17/17 10:37:41.444 Critical: At least one of the physical devices could not be opened... Exiting...
05/17/17 10:37:46.622 Could not set owner for device /dev/ttyUSB0: No such file or directory

homegear.log

06/18/17 21:28:13.041 Module HomeMatic BidCoS: CUL "My-CUL": Info: Sending (My-CUL): 0B09B001FDCFBC3D81870006
06/18/17 21:28:13.043 Module HomeMatic BidCoS: CUL "My-CUL": Info: Sending (My-CUL): 0B0DB001FDCFBC3D81A40006
06/18/17 21:28:13.161 Module HomeMatic BidCoS: CUL "My-CUL": Info: Sending (My-CUL): 0B09B001FDCFBC3D81870006
06/18/17 21:28:13.163 Module HomeMatic BidCoS: CUL "My-CUL": Info: Sending (My-CUL): 0B0DB001FDCFBC3D81A40006
06/18/17 21:28:13.165 Module HomeMatic BidCoS: CUL "My-CUL": Info: Sending (My-CUL): 0B03B001FDCFBC3C366F0006
06/18/17 21:28:13.602 Module HomeMatic BidCoS: CUL "My-CUL": Info: Sending (My-CUL): 0B09B001FDCFBC3D81870006
06/18/17 21:28:13.603 Module HomeMatic BidCoS: CUL "My-CUL": Info: Sending (My-CUL): 0B0DB001FDCFBC3D81A40006
06/18/17 21:28:14.042 Module HomeMatic BidCoS: CUL "My-CUL": Info: Sending (My-CUL): 0B09B001FDCFBC3D81870006
06/18/17 21:28:14.162 Module HomeMatic BidCoS: CUL "My-CUL": Info: Sending (My-CUL): 0B09B001FDCFBC3D81870006
06/18/17 21:28:14.163 Module HomeMatic BidCoS: CUL "My-CUL": Info: Sending (My-CUL): 0B0DB001FDCFBC3D81A40006
06/18/17 21:28:14.602 Module HomeMatic BidCoS: CUL "My-CUL": Info: Sending (My-CUL): 0B09B001FDCFBC3D81870006
06/18/17 21:28:15.162 Module HomeMatic BidCoS: CUL "My-CUL": Info: Sending (My-CUL): 0B09B001FDCFBC3D81870006
06/18/17 21:28:19.977 Info: Connection to CLI client number 26 closed.
06/18/17 21:28:23.544 RPC Server (Port 2001): Info: Client number 27 is calling RPC method: listBidcosInterfaces (2) Parameters:
06/18/17 21:28:38.547 RPC Server (Port 2001): Info: Client number 27 is calling RPC method: listBidcosInterfaces (2) Parameters:
06/18/17 21:28:53.551 RPC Server (Port 2001): Info: Client number 27 is calling RPC method: listBidcosInterfaces (2) Parameters:
06/18/17 21:29:08.554 RPC Server (Port 2001): Info: Client number 27 is calling RPC method: listBidcosInterfaces (2) Parameters:
06/18/17 21:29:23.558 RPC Server (Port 2001): Info: Client number 27 is calling RPC method: listBidcosInterfaces (2) Parameters:
06/18/17 21:29:38.561 RPC Server (Port 2001): Info: Client number 27 is calling RPC method: listBidcosInterfaces (2) Parameters:
06/18/17 21:29:53.565 RPC Server (Port 2001): Info: Client number 27 is calling RPC method: listBidcosInterfaces (2) Parameters:
06/18/17 21:30:08.568 RPC Server (Port 2001): Info: Client number 27 is calling RPC method: listBidcosInterfaces (2) Parameters:
06/18/17 21:30:23.571 RPC Server (Port 2001): Info: Client number 27 is calling RPC method: listBidcosInterfaces (2) Parameters:
06/18/17 21:30:38.574 RPC Server (Port 2001): Info: Client number 27 is calling RPC method: listBidcosInterfaces (2) Parameters:
06/18/17 21:30:53.577 RPC Server (Port 2001): Info: Client number 27 is calling RPC method: listBidcosInterfaces (2) Parameters:
06/18/17 21:31:08.580 RPC Server (Port 2001): Info: Client number 27 is calling RPC method: listBidcosInterfaces (2) Parameters:
06/18/17 21:31:23.584 RPC Server (Port 2001): Info: Client number 27 is calling RPC method: listBidcosInterfaces (2) Parameters:
06/18/17 21:31:38.587 RPC Server (Port 2001): Info: Client number 27 is calling RPC method: listBidcosInterfaces (2) Parameters:
06/18/17 21:31:53.591 RPC Server (Port 2001): Info: Client number 27 is calling RPC method: listBidcosInterfaces (2) Parameters:
06/18/17 21:32:08.594 RPC Server (Port 2001): Info: Client number 27 is calling RPC method: listBidcosInterfaces (2) Parameters:
06/18/17 21:32:23.598 RPC Server (Port 2001): Info: Client number 27 is calling RPC method: listBidcosInterfaces (2) Parameters:
06/18/17 21:32:38.601 RPC Server (Port 2001): Info: Client number 27 is calling RPC method: listBidcosInterfaces (2) Parameters:
06/18/17 21:32:53.846 RPC Server (Port 2001): Info: Client number 27 is calling RPC method: listBidcosInterfaces (2) Parameters:
06/18/17 21:33:08.849 RPC Server (Port 2001): Info: Client number 27 is calling RPC method: listBidcosInterfaces (2) Parameters:
06/18/17 21:33:21.429 RPC Server (Port 2001): Info: Client number 27 is calling RPC method: init (2) Parameters:
(String) binary://192.168.178.31:9126
06/18/17 21:33:21.429 Info: Removing server "binary://192.168.178.31".
06/18/17 21:33:21.433 RPC Server (Port 2001): Info: Client number 27 is calling RPC method: init (2) Parameters:
(String) binary://192.168.178.31:9126
(String) RF-1786b4a6
06/18/17 21:33:21.434 Info: Adding server "binary://192.168.178.31".
06/18/17 21:33:21.434 Info: Calling init methods on server "binary://192.168.178.31".
06/18/17 21:33:21.443 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.178.31:55348 accepted. Client number: 33
06/18/17 21:33:21.443 RPC Server (Port 2001): Info: RPC server client id for client number 33 is: 6
06/18/17 21:33:21.444 RPC Server (Port 2001): Info: Client number 33 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578135:0
(String) MASTER
06/18/17 21:33:21.459 RPC Server (Port 2001): Info: Client number 33 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578135:0
(String) VALUES
06/18/17 21:33:21.464 RPC Server (Port 2001): Info: Client number 33 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:0
(String) MASTER
06/18/17 21:33:21.479 RPC Server (Port 2001): Info: Client number 33 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:0
(String) VALUES
06/18/17 21:33:21.483 RPC Server (Port 2001): Info: Client number 33 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578170:0
(String) MASTER
06/18/17 21:33:21.498 RPC Server (Port 2001): Info: Client number 33 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578170:0
(String) VALUES
06/18/17 21:33:23.856 RPC Server (Port 2001): Info: Client number 33 is calling RPC method: listBidcosInterfaces (2) Parameters:
06/18/17 21:33:38.860 RPC Server (Port 2001): Info: Client number 33 is calling RPC method: listBidcosInterfaces (2) Parameters:
06/18/17 21:33:53.863 RPC Server (Port 2001): Info: Client number 33 is calling RPC method: listBidcosInterfaces (2) Parameters:
06/18/17 21:34:08.867 RPC Server (Port 2001): Info: Client number 33 is calling RPC method: listBidcosInterfaces (2) Parameters:
06/18/17 21:34:21.504 RPC Server (Port 2001): Info: Client number 33 is calling RPC method: init (2) Parameters:
(String) binary://192.168.178.31:9126
06/18/17 21:34:21.504 Info: Removing server "binary://192.168.178.31".
06/18/17 21:34:23.871 RPC Server (Port 2001): Info: Client number 33 is calling RPC method: listBidcosInterfaces (2) Parameters:
06/18/17 21:34:38.874 RPC Server (Port 2001): Info: Client number 33 is calling RPC method: listBidcosInterfaces (2) Parameters:
06/18/17 21:34:53.877 RPC Server (Port 2001): Info: Client number 33 is calling RPC method: listBidcosInterfaces (2) Parameters:
06/18/17 21:35:08.881 RPC Server (Port 2001): Info: Client number 33 is calling RPC method: listBidcosInterfaces (2) Parameters:
06/18/17 21:35:21.513 RPC Server (Port 2001): Info: Client number 33 is calling RPC method: init (2) Parameters:
(String) binary://192.168.178.31:9126
06/18/17 21:35:21.517 RPC Server (Port 2001): Info: Client number 33 is calling RPC method: init (2) Parameters:
(String) binary://192.168.178.31:9126
(String) RF-1786b4a6
06/18/17 21:35:21.518 Info: Adding server "binary://192.168.178.31".
06/18/17 21:35:21.518 Info: Calling init methods on server "binary://192.168.178.31".
06/18/17 21:35:21.526 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.178.31:55368 accepted. Client number: 36
06/18/17 21:35:21.527 RPC Server (Port 2001): Info: RPC server client id for client number 36 is: 7
06/18/17 21:35:21.527 RPC Server (Port 2001): Info: Client number 36 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578135:0
(String) MASTER
06/18/17 21:35:21.542 RPC Server (Port 2001): Info: Client number 36 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578135:0
(String) VALUES
06/18/17 21:35:21.547 RPC Server (Port 2001): Info: Client number 36 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:0
(String) MASTER
06/18/17 21:35:21.562 RPC Server (Port 2001): Info: Client number 36 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:0
(String) VALUES
06/18/17 21:35:21.566 RPC Server (Port 2001): Info: Client number 36 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578170:0
(String) MASTER
06/18/17 21:35:21.580 RPC Server (Port 2001): Info: Client number 36 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578170:0
(String) VALUES
06/18/17 21:35:23.888 RPC Server (Port 2001): Info: Client number 36 is calling RPC method: listBidcosInterfaces (2) Parameters:

machnetz · June 19, 2017, 6:58pm

Moin,

es wäre weitere Hilfe aus dem Forum wichtig, wenn du mal erzählst, auf welcher Basis dein System läuft. Mein System bspws. ist ein rPI-2 mit nanoCUL868 und läuft mit openhabian. Da kann man ohne großartig viel hin- und her zu kompilieren Openhab2 und homegear installieren.

Dann wäre es gut zu wissen, ob die (nano?)CUL-Sticks einwandfrei ansprechbar sind, also sind die seriellen Ports frei für die Sticks? (/dev/ttyUSB0 usw.)

Zeig mal den Inhalt der folgenden Dateien:

/etc/homegear/families/homematicbidcos.conf
/boot/config.txt
/boot/cmdline.txt

Dann sehen wir weiter. Gruß machnetz

machnetz · June 20, 2017, 7:58am

Moin sebami,

ich habe mir nocheinmal deine Logs angesehen …und wie ich dein Log interpretiere ist das kein dediziertes System, auf welchem du “nur” homegear 0.7 sowie Openhab einsetzt, sondern ein System mit “vielen” Funktionen:

Dann sind der/die Ports für den CUL sind nicht richtig konfiguriert: [quote=“sebami, post:1, topic:1325”]
05/17/17 10:37:26.256 Module HomeMatic BidCoS: CUL “My-CUL”: Couldn’t open CUL device “/dev/ttyUSB0”: No such file or directory
05/17/17 10:37:26.256 Critical: At least one of the physical devices could not be opened… Exiting…
[/quote]

Das bedeutet, das homegear schon mal keinen exclusiven Zugriff auf deinen CUL hat bzw. der Port gar nicht existiert. Mach mal bitte eine Ausgabe von “ls -altr /dev/tty*” in der Kommandozeile als root. Wenn du sichergestellt hast, dass deine Sticks erkannt werden, können wir weiter suchen.

Zeig auch mal deine Geräte im homegear, wenn du mittels homegear -r, fs 0, ls die angelernten Devices ausgibst.

Bis dahin - Gruß aus der schönsten Stadt der Welt von machnetz

sebami · June 23, 2017, 7:11pm

Hallo Machnetz,

Vielen Dank für Deine Rückmeldung und entschudige, dass ich noch nicht alle nötigen Informationen zusammengestellt habe. Ist eigentlich klar, dass man besser helfen kann wenn man alle Hintegrundinfos hat…

Also meine System ist eine rPI-3 mit nanoCUL FTDI 433 Mhz – CC1101 und nanoCUL FTDI 868 Mhz – CC1101 und es läuft ebenfalls mit openhabian. Wie gesagt, bis zu dem Moment wo ich Intertechno installieren wollte auch einige Wochen für Homematic sehr stabil.

homematicbidcos.conf

#######################################
################# 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
deviceType = cul

device = /dev/ttyUSB0

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

intertechno.conf

#######################################
################# CUL #################
#######################################

## The device family this interface is for
[CUL]

## Specify an unique id here to identify this device in Homegear
id = My-IT-CUL-1

## When default is set to "true" Homegear will assign this device
## to new peers.
default = true

deviceType = cul

device = /dev/ttyUSB1

## Should be 57600 for the "official" CUL.
baudrate = 57600

## You can pass additional comma seperated commands to the CUL on initialization.
## E. g. for isr8 and it425:
## addtionalCommands = isr8,it425
#additionalCommands =

config.txt

# For more options and information see
# http://rpf.io/configtxtreadme
# 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
#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

cmdline.txt

dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait

Hier die Ausgabe von ls -altr /dev/tty*

crw--w---- 1 root     tty        4,  0 Jun 18 16:08 /dev/tty0
crw--w---- 1 root     tty        4, 18 Jun 18 16:08 /dev/tty18
crw--w---- 1 root     tty        4, 16 Jun 18 16:08 /dev/tty16
crw--w---- 1 root     tty        4, 15 Jun 18 16:08 /dev/tty15
crw--w---- 1 root     tty        4, 14 Jun 18 16:08 /dev/tty14
crw--w---- 1 root     tty        4, 13 Jun 18 16:08 /dev/tty13
crw--w---- 1 root     tty        4, 12 Jun 18 16:08 /dev/tty12
crw--w---- 1 root     tty        4, 11 Jun 18 16:08 /dev/tty11
crw--w---- 1 root     tty        4, 10 Jun 18 16:08 /dev/tty10
crw--w---- 1 root     tty        4, 28 Jun 18 16:08 /dev/tty28
crw--w---- 1 root     tty        4, 27 Jun 18 16:08 /dev/tty27
crw--w---- 1 root     tty        4, 26 Jun 18 16:08 /dev/tty26
crw--w---- 1 root     tty        4, 25 Jun 18 16:08 /dev/tty25
crw--w---- 1 root     tty        4, 24 Jun 18 16:08 /dev/tty24
crw--w---- 1 root     tty        4, 23 Jun 18 16:08 /dev/tty23
crw--w---- 1 root     tty        4, 22 Jun 18 16:08 /dev/tty22
crw--w---- 1 root     tty        4, 21 Jun 18 16:08 /dev/tty21
crw--w---- 1 root     tty        4, 20 Jun 18 16:08 /dev/tty20
crw--w---- 1 root     tty        4,  2 Jun 18 16:08 /dev/tty2
crw--w---- 1 root     tty        4, 19 Jun 18 16:08 /dev/tty19
crw--w---- 1 root     tty        4, 17 Jun 18 16:08 /dev/tty17
crw--w---- 1 root     tty        4, 43 Jun 18 16:08 /dev/tty43
crw--w---- 1 root     tty        4, 42 Jun 18 16:08 /dev/tty42
crw--w---- 1 root     tty        4, 40 Jun 18 16:08 /dev/tty40
crw--w---- 1 root     tty        4,  4 Jun 18 16:08 /dev/tty4
crw--w---- 1 root     tty        4, 39 Jun 18 16:08 /dev/tty39
crw--w---- 1 root     tty        4, 38 Jun 18 16:08 /dev/tty38
crw--w---- 1 root     tty        4, 37 Jun 18 16:08 /dev/tty37
crw--w---- 1 root     tty        4, 36 Jun 18 16:08 /dev/tty36
crw--w---- 1 root     tty        4, 35 Jun 18 16:08 /dev/tty35
crw--w---- 1 root     tty        4, 34 Jun 18 16:08 /dev/tty34
crw--w---- 1 root     tty        4, 33 Jun 18 16:08 /dev/tty33
crw--w---- 1 root     tty        4, 32 Jun 18 16:08 /dev/tty32
crw--w---- 1 root     tty        4, 31 Jun 18 16:08 /dev/tty31
crw--w---- 1 root     tty        4, 30 Jun 18 16:08 /dev/tty30
crw--w---- 1 root     tty        4,  3 Jun 18 16:08 /dev/tty3
crw--w---- 1 root     tty        4, 29 Jun 18 16:08 /dev/tty29
crw--w---- 1 root     tty        4, 47 Jun 18 16:08 /dev/tty47
crw--w---- 1 root     tty        4, 46 Jun 18 16:08 /dev/tty46
crw--w---- 1 root     tty        4, 45 Jun 18 16:08 /dev/tty45
crw--w---- 1 root     tty        4, 44 Jun 18 16:08 /dev/tty44
crw--w---- 1 root     tty        4, 41 Jun 18 16:08 /dev/tty41
crw--w---- 1 root     tty        4, 51 Jun 18 16:08 /dev/tty51
crw--w---- 1 root     tty        4, 50 Jun 18 16:08 /dev/tty50
crw--w---- 1 root     tty        4,  5 Jun 18 16:08 /dev/tty5
crw--w---- 1 root     tty        4, 49 Jun 18 16:08 /dev/tty49
crw--w---- 1 root     tty        4, 48 Jun 18 16:08 /dev/tty48
crw--w---- 1 root     tty        4, 57 Jun 18 16:08 /dev/tty57
crw--w---- 1 root     tty        4, 56 Jun 18 16:08 /dev/tty56
crw--w---- 1 root     tty        4, 55 Jun 18 16:08 /dev/tty55
crw--w---- 1 root     tty        4, 54 Jun 18 16:08 /dev/tty54
crw--w---- 1 root     tty        4, 53 Jun 18 16:08 /dev/tty53
crw--w---- 1 root     tty        4, 52 Jun 18 16:08 /dev/tty52
crw------- 1 root     root       5,  3 Jun 18 16:08 /dev/ttyprintk
crw--w---- 1 root     tty        4,  8 Jun 18 16:08 /dev/tty8
crw--w---- 1 root     tty        4,  7 Jun 18 16:08 /dev/tty7
crw--w---- 1 root     tty        4, 63 Jun 18 16:08 /dev/tty63
crw--w---- 1 root     tty        4, 62 Jun 18 16:08 /dev/tty62
crw--w---- 1 root     tty        4, 61 Jun 18 16:08 /dev/tty61
crw--w---- 1 root     tty        4, 60 Jun 18 16:08 /dev/tty60
crw--w---- 1 root     tty        4,  6 Jun 18 16:08 /dev/tty6
crw--w---- 1 root     tty        4, 59 Jun 18 16:08 /dev/tty59
crw--w---- 1 root     tty        4, 58 Jun 18 16:08 /dev/tty58
crw--w---- 1 root     tty        4,  9 Jun 18 16:08 /dev/tty9
crw-rw---- 1 root     dialout  204, 64 Jun 18 16:08 /dev/ttyAMA0
crw--w---- 1 root     tty        4,  1 Jun 18 16:08 /dev/tty1
crw-rw---- 1 homegear homegear 188,  1 Jun 18 21:26 /dev/ttyUSB1
crw-rw-rw- 1 root     tty        5,  0 Jun 21 22:11 /dev/tty
crw-rw---- 1 homegear homegear 188,  0 Jun 21 22:21 /dev/ttyUSB0

Und hier die Geräte:

  ID │ Name                      │  Address │ Serial Number │ Type │ Type String               │ Firmware │ Config Pending │ Unreach │ Low Bat
────────────┼───────────────────────────┼──────────┼───────────────┼──────┼───────────────────────────┼──────────┼────────────────┼─────────┼────────
            │                           │          │               │      │                           │          │                │         │        
          1 │ Kinderzimmer              │   3D81A4 │    MEQ0578170 │ 0095 │               HM-CC-RT-DN │      1.4 │             No │     Yes │      No
          2 │ Julies Zimmer             │   3D8187 │    MEQ0578135 │ 0095 │               HM-CC-RT-DN │      1.4 │             No │     Yes │      No
          3 │ Schlafzimmer              │   3C366F │    MEQ0577914 │ 0095 │               HM-CC-RT-DN │      1.4 │             No │     Yes │      No
────────────┴───────────────────────────┴──────────┴───────────────┴──────┴───────────────────────────┴──────────┴────────────────┴─────────┴────────

Intertechno habe ich ich nicht angelernt.

Vielen Dank noch mal für die Unterstützung,
Sebastian

machnetz · June 21, 2017, 9:09pm

Hey Sebastian,

danke für deine Rückmeldung, klasse! Dat Ganze is aba n wenig unglücklich formatiert, probiere mal deinen Text in den 6ten. Punkt oberhalb des Editors (da ist ein Icon zu sehen wie: </> einzufügen… Das ist dann besser lesbar …

Gruß, machnetz

machnetz · June 21, 2017, 9:22pm

So, im Vergleich dazu mal meine /boot/cmdline.txt:

dwc_otg.lpm_enable=0 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait

und die /boot/config.txt:

dtparam=i2c_arm=on    
dtparam=spi=on
dtparam=audio=on
gpu_mem=16
enable_uart=1

Deine Datei ist wegen weiterer Dienste wahrscheinlich auch weiter “offen”, also angepasster. Deshalb unterscheidet sich meine Ausgabe zu deiner auch in vielen ganzen Zeilen. Ich sehe so spontan erst einmal keine groben Fehler …

Intertechno hast du - wie installiert?

Gruß, machnetz

sebami · June 22, 2017, 9:47am

Hallo machnetz,

Zum formatieren meines Eintrags komme ich vermutlich heute Abend. Vorab aber schon mal die Info, dass ich Intertechno via “apt-get install homegear-intertechno” nachinstalliert habe.

VG, Sebastian

sebami · June 23, 2017, 3:19pm

Anbei noch mal die letzten Infos anders formatiert. Hoffe so kann man mehr damit anfangen:

homematicbidcos.conf

#######################################
################# 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
deviceType = cul

device = /dev/ttyUSB0

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

intertechno.conf

#######################################
################# CUL #################
#######################################

## The device family this interface is for
[CUL]

## Specify an unique id here to identify this device in Homegear
id = My-IT-CUL-1

## When default is set to "true" Homegear will assign this device
## to new peers.
default = true

deviceType = cul

device = /dev/ttyUSB1

## Should be 57600 for the "official" CUL.
baudrate = 57600

## You can pass additional comma seperated commands to the CUL on initialization.
## E. g. for isr8 and it425:
## addtionalCommands = isr8,it425
#additionalCommands =

config.txt

# For more options and information see
# http://rpf.io/configtxtreadme
# 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
#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

cmdline.txt

dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait

Hier die Ausgabe von ls -altr /dev/tty*

crw--w---- 1 root     tty        4,  0 Jun 18 16:08 /dev/tty0
crw--w---- 1 root     tty        4, 18 Jun 18 16:08 /dev/tty18
crw--w---- 1 root     tty        4, 16 Jun 18 16:08 /dev/tty16
crw--w---- 1 root     tty        4, 15 Jun 18 16:08 /dev/tty15
crw--w---- 1 root     tty        4, 14 Jun 18 16:08 /dev/tty14
crw--w---- 1 root     tty        4, 13 Jun 18 16:08 /dev/tty13
crw--w---- 1 root     tty        4, 12 Jun 18 16:08 /dev/tty12
crw--w---- 1 root     tty        4, 11 Jun 18 16:08 /dev/tty11
crw--w---- 1 root     tty        4, 10 Jun 18 16:08 /dev/tty10
crw--w---- 1 root     tty        4, 28 Jun 18 16:08 /dev/tty28
crw--w---- 1 root     tty        4, 27 Jun 18 16:08 /dev/tty27
crw--w---- 1 root     tty        4, 26 Jun 18 16:08 /dev/tty26
crw--w---- 1 root     tty        4, 25 Jun 18 16:08 /dev/tty25
crw--w---- 1 root     tty        4, 24 Jun 18 16:08 /dev/tty24
crw--w---- 1 root     tty        4, 23 Jun 18 16:08 /dev/tty23
crw--w---- 1 root     tty        4, 22 Jun 18 16:08 /dev/tty22
crw--w---- 1 root     tty        4, 21 Jun 18 16:08 /dev/tty21
crw--w---- 1 root     tty        4, 20 Jun 18 16:08 /dev/tty20
crw--w---- 1 root     tty        4,  2 Jun 18 16:08 /dev/tty2
crw--w---- 1 root     tty        4, 19 Jun 18 16:08 /dev/tty19
crw--w---- 1 root     tty        4, 17 Jun 18 16:08 /dev/tty17
crw--w---- 1 root     tty        4, 43 Jun 18 16:08 /dev/tty43
crw--w---- 1 root     tty        4, 42 Jun 18 16:08 /dev/tty42
crw--w---- 1 root     tty        4, 40 Jun 18 16:08 /dev/tty40
crw--w---- 1 root     tty        4,  4 Jun 18 16:08 /dev/tty4
crw--w---- 1 root     tty        4, 39 Jun 18 16:08 /dev/tty39
crw--w---- 1 root     tty        4, 38 Jun 18 16:08 /dev/tty38
crw--w---- 1 root     tty        4, 37 Jun 18 16:08 /dev/tty37
crw--w---- 1 root     tty        4, 36 Jun 18 16:08 /dev/tty36
crw--w---- 1 root     tty        4, 35 Jun 18 16:08 /dev/tty35
crw--w---- 1 root     tty        4, 34 Jun 18 16:08 /dev/tty34
crw--w---- 1 root     tty        4, 33 Jun 18 16:08 /dev/tty33
crw--w---- 1 root     tty        4, 32 Jun 18 16:08 /dev/tty32
crw--w---- 1 root     tty        4, 31 Jun 18 16:08 /dev/tty31
crw--w---- 1 root     tty        4, 30 Jun 18 16:08 /dev/tty30
crw--w---- 1 root     tty        4,  3 Jun 18 16:08 /dev/tty3
crw--w---- 1 root     tty        4, 29 Jun 18 16:08 /dev/tty29
crw--w---- 1 root     tty        4, 47 Jun 18 16:08 /dev/tty47
crw--w---- 1 root     tty        4, 46 Jun 18 16:08 /dev/tty46
crw--w---- 1 root     tty        4, 45 Jun 18 16:08 /dev/tty45
crw--w---- 1 root     tty        4, 44 Jun 18 16:08 /dev/tty44
crw--w---- 1 root     tty        4, 41 Jun 18 16:08 /dev/tty41
crw--w---- 1 root     tty        4, 51 Jun 18 16:08 /dev/tty51
crw--w---- 1 root     tty        4, 50 Jun 18 16:08 /dev/tty50
crw--w---- 1 root     tty        4,  5 Jun 18 16:08 /dev/tty5
crw--w---- 1 root     tty        4, 49 Jun 18 16:08 /dev/tty49
crw--w---- 1 root     tty        4, 48 Jun 18 16:08 /dev/tty48
crw--w---- 1 root     tty        4, 57 Jun 18 16:08 /dev/tty57
crw--w---- 1 root     tty        4, 56 Jun 18 16:08 /dev/tty56
crw--w---- 1 root     tty        4, 55 Jun 18 16:08 /dev/tty55
crw--w---- 1 root     tty        4, 54 Jun 18 16:08 /dev/tty54
crw--w---- 1 root     tty        4, 53 Jun 18 16:08 /dev/tty53
crw--w---- 1 root     tty        4, 52 Jun 18 16:08 /dev/tty52
crw------- 1 root     root       5,  3 Jun 18 16:08 /dev/ttyprintk
crw--w---- 1 root     tty        4,  8 Jun 18 16:08 /dev/tty8
crw--w---- 1 root     tty        4,  7 Jun 18 16:08 /dev/tty7
crw--w---- 1 root     tty        4, 63 Jun 18 16:08 /dev/tty63
crw--w---- 1 root     tty        4, 62 Jun 18 16:08 /dev/tty62
crw--w---- 1 root     tty        4, 61 Jun 18 16:08 /dev/tty61
crw--w---- 1 root     tty        4, 60 Jun 18 16:08 /dev/tty60
crw--w---- 1 root     tty        4,  6 Jun 18 16:08 /dev/tty6
crw--w---- 1 root     tty        4, 59 Jun 18 16:08 /dev/tty59
crw--w---- 1 root     tty        4, 58 Jun 18 16:08 /dev/tty58
crw--w---- 1 root     tty        4,  9 Jun 18 16:08 /dev/tty9
crw-rw---- 1 root     dialout  204, 64 Jun 18 16:08 /dev/ttyAMA0
crw--w---- 1 root     tty        4,  1 Jun 18 16:08 /dev/tty1
crw-rw---- 1 homegear homegear 188,  1 Jun 18 21:26 /dev/ttyUSB1
crw-rw-rw- 1 root     tty        5,  0 Jun 21 22:11 /dev/tty
crw-rw---- 1 homegear homegear 188,  0 Jun 21 22:21 /dev/ttyUSB0

Und hier die Geräte:

  ID │ Name                      │  Address │ Serial Number │ Type │ Type String               │ Firmware │ Config Pending │ Unreach │ Low Bat
────────────┼───────────────────────────┼──────────┼───────────────┼──────┼───────────────────────────┼──────────┼────────────────┼─────────┼────────
        │                           │          │               │      │                           │          │                │         │        
      1 │ Kinderzimmer              │   3D81A4 │    MEQ0578170 │ 0095 │               HM-CC-RT-DN │      1.4 │             No │     Yes │      No
      2 │ Julies Zimmer             │   3D8187 │    MEQ0578135 │ 0095 │               HM-CC-RT-DN │      1.4 │             No │     Yes │      No
      3 │ Schlafzimmer              │   3C366F │    MEQ0577914 │ 0095 │               HM-CC-RT-DN │      1.4 │             No │     Yes │      No
────────────┴───────────────────────────┴──────────┴───────────────┴──────┴───────────────────────────┴──────────┴────────────────┴─────────┴────────

sathya · June 23, 2017, 7:23pm

Hallo @sebami,

Das spricht dafür, dass versucht wird Homegear doppelt zu starten. Beende einmal Homegear mit (alle folgenden Befehle als root):

service homegear stop

Überprüfe, dass es wirklich nicht mehr läuft:

ps -A | grep homegear

(sollte keine Ausgabe erzeugen).

Starte es anschließend mit:

service homegear start

Und poste das Log. Der Intertechno-CUL muss aus der homematicbidcos.conf wieder entfernt werden (und in die intertechno.conf). Dieser ist mit default = true konfiguriert. Damit wird dieser standardmäßig verwendet. Mit dem 433MHz-CUL ist jedoch keine 868MHz-Kommunikation (heißt keine Kommunikation mit HomeMatic-Geräten) möglich.

Viele Grüße

Sathya

sebami · June 24, 2017, 8:29pm

Hallo Sathya,

Danke für die Rückmeldung. Anbei das Log:

06/24/17 22:07:31.672 Loading RPC server settings from /etc/homegear/rpcservers.conf
06/24/17 22:07:31.674 Loading RPC client settings from /etc/homegear/rpcclients.conf
06/24/17 22:07:31.675 Starting Homegear...
06/24/17 22:07:31.675 Homegear version 0.7.2-1207
06/24/17 22:07:31.675 Git commit SHA of libhomegear-base: -
06/24/17 22:07:31.676 Git branch of libhomegear-base:     -
06/24/17 22:07:31.676 Git commit SHA of Homegear:         -
06/24/17 22:07:31.676 Git branch of Homegear:             -
06/24/17 22:07:31.677 Info: Setting allowed core file size to "4294967295" for user with id 0 and group with id 0.
06/24/17 22:07:31.677 Info: Core file size now is "4294967295".
06/24/17 22:07:31.677 Info: Setting maximum thread priority to "0" for user with id 0 and group with id 0.
06/24/17 22:07:31.677 Info: Maximum thread priority now is "0".
06/24/17 22:07:31.704 Info: Backing up database...
06/24/17 22:07:31.711 Can't execute "PRAGMA journal_mode=DELETE": database is locked
06/24/17 22:07:31.711 Can't execute "PRAGMA journal_mode=DELETE": database is locked
06/24/17 22:07:32.090 Initializing database...
06/24/17 22:07:32.092 Info: Loading family module mod_homematicbidcos.so
06/24/17 22:07:32.104 /etc/homegear/families/homematicbidcos.conf
06/24/17 22:07:32.105 Info: Loading family module mod_homematicwired.so
06/24/17 22:07:32.111 /etc/homegear/families/homematicwired.conf
06/24/17 22:07:32.112 Info: Loading family module mod_intertechno.so
06/24/17 22:07:32.116 /etc/homegear/families/intertechno.conf
06/24/17 22:07:32.117 Info: Loading family module mod_miscellaneous.so
06/24/17 22:07:32.120 /etc/homegear/families/miscellaneous.conf
06/24/17 22:07:32.121 Warning: Running as root. The authors of Homegear recommend running Homegear as user.
06/24/17 22:07:32.121 Warning: Running as root. The authors of Homegear recommend running Homegear as user.
06/24/17 22:07:32.121 Starting script engine server...
06/24/17 22:07:32.124 Initializing licensing controller...
06/24/17 22:07:32.125 Loading licensing controller data...
06/24/17 22:07:32.125 Loading devices...
06/24/17 22:07:32.125 Loading XML RPC devices...
06/24/17 22:07:33.263 Loading device 2
06/24/17 22:07:33.263 Module HomeMatic BidCoS: Info: Central address set to 0xFDCFBC.
06/24/17 22:07:33.264 Module HomeMatic BidCoS: Loading peer 1
06/24/17 22:07:33.278 Module HomeMatic BidCoS: Loading peer 2
06/24/17 22:07:33.292 Module HomeMatic BidCoS: Loading peer 3
06/24/17 22:07:33.306 Info: Not initializing device family HomeMatic Wired, because no physical interface was found.
06/24/17 22:07:33.306 Info: Disposing family module mod_homematicwired.so
06/24/17 22:07:33.307 Loading XML RPC devices...
06/24/17 22:07:33.311 Loading device 3
06/24/17 22:07:33.312 Loading XML RPC devices...
06/24/17 22:07:33.314 Loading device 1
06/24/17 22:07:33.314 Initializing RPC client...
06/24/17 22:07:33.314 Starting XML RPC server RPCServer1 listening on :::2001...
06/24/17 22:07:33.317 Starting XML RPC server RPCServer2 listening on :::2002, SSL enabled...
06/24/17 22:07:33.317 RPC Server (Port 2001): Error: Server could not start listening on port 2001: Address already in use
06/24/17 22:07:33.317 RPC Server (Port 2001): Error: Server could not start listening on port 2001: Address already in use
06/24/17 22:07:33.349 Starting XML RPC server RPCServer3 listening on :::2003, SSL enabled, authentication enabled...
06/24/17 22:07:33.349 RPC Server (Port 2002): Error: Server could not start listening on port 2002: Address already in use
06/24/17 22:07:33.349 RPC Server (Port 2002): Error: Server could not start listening on port 2002: Address already in use
06/24/17 22:07:33.381 Starting CLI server...
06/24/17 22:07:33.381 RPC Server (Port 2003): Error: Server could not start listening on port 2003: Address already in use
06/24/17 22:07:33.381 RPC Server (Port 2003): Error: Server could not start listening on port 2003: Address already in use
06/24/17 22:07:33.381 Initializing event handler...
06/24/17 22:07:33.381 Loading events...
06/24/17 22:07:33.384 Starting flows server...
06/24/17 22:07:33.385 Starting IPC server...
06/24/17 22:07:33.389 Start listening for packets...
06/24/17 22:07:33.389 Module HomeMatic BidCoS: CUL "My-CUL": CUL device is in use: /dev/ttyUSB0
06/24/17 22:07:33.389 Module HomeMatic BidCoS: CUL "My-CUL": CUL device is in use: /dev/ttyUSB0
06/24/17 22:07:33.390 Module Intertechno: Intertechno CUL "My-IT-CUL-1": Error in file PhysicalInterfaces/Cul.cpp line 105 in function virtual void MyFamily::Cul::startListening(): Device is in use: /dev/ttyUSB1
06/24/17 22:07:33.390 Module Intertechno: Intertechno CUL "My-IT-CUL-1": Error in file PhysicalInterfaces/Cul.cpp line 105 in function virtual void MyFamily::Cul::startListening(): Device is in use: /dev/ttyUSB1
06/24/17 22:07:33.390 Critical: At least one of the physical devices could not be opened... Exiting...
06/24/17 22:07:33.390 Critical: At least one of the physical devices could not be opened... Exiting...
06/24/17 22:07:35.400 Closing database...
06/24/17 22:07:35.460 Error: Can't execute "PRAGMA journal_mode = DELETE": database is locked
06/24/17 22:07:35.460 Error: Can't execute "PRAGMA journal_mode = DELETE": database is locked
06/24/17 22:07:35.460 Info: Disposing family module mod_miscellaneous.so
06/24/17 22:07:35.461 Info: Disposing family module mod_intertechno.so
06/24/17 22:07:35.461 Info: Disposing family module mod_homematicbidcos.so
06/24/17 22:07:38.317 RPC Server (Port 2001): Error: Server could not start listening on port 2001: Address already in use
06/24/17 22:07:38.318 RPC Server (Port 2001): Error: Server could not start listening on port 2001: Address already in use
06/24/17 22:07:38.350 RPC Server (Port 2002): Error: Server could not start listening on port 2002: Address already in use
06/24/17 22:07:38.350 RPC Server (Port 2002): Error: Server could not start listening on port 2002: Address already in use
06/24/17 22:07:38.381 RPC Server (Port 2003): Error: Server could not start listening on port 2003: Address already in use
06/24/17 22:07:38.381 RPC Server (Port 2003): Error: Server could not start listening on port 2003: Address already in use
06/24/17 22:07:38.382 RPC Server (Port 2003): Info: Waiting for threads to finish.
06/24/17 22:07:43.318 RPC Server (Port 2001): Error: Server could not start listening on port 2001: Address already in use
06/24/17 22:07:43.318 RPC Server (Port 2001): Error: Server could not start listening on port 2001: Address already in use
06/24/17 22:07:43.351 RPC Server (Port 2002): Error: Server could not start listening on port 2002: Address already in use
06/24/17 22:07:43.351 RPC Server (Port 2002): Error: Server could not start listening on port 2002: Address already in use
06/24/17 22:07:43.351 RPC Server (Port 2002): Info: Waiting for threads to finish.
06/24/17 22:07:48.319 RPC Server (Port 2001): Error: Server could not start listening on port 2001: Address already in use
06/24/17 22:07:48.319 RPC Server (Port 2001): Error: Server could not start listening on port 2001: Address already in use
06/24/17 22:07:48.319 RPC Server (Port 2001): Info: Waiting for threads to finish.

Das habe ich allerdings nicht ganz verstanden. Ich habe doch zwei CUL einen für 433 und einen für 868 eben weil mit dem 433Mhz keine Homematic Komponenten ansprechen kann. Habe ich sie falsch zugeordnet?

Übrigens funktioniert das System nach einem Restart von Homegear für wenige Minuten!

VG, Sebastian

sathya · June 24, 2017, 8:36pm

Hallo @sebami,

Wie kommst du an das Log? Es sieht für mich so aus, als würdest du in der Shell homegear eintippen? Das startet Homegear erneut und würde die Fehlermeldungen erklären. Das Log kannst du mit

nano /var/log/homegear/homegear.log

öffnen. Oder über Programme wie “scp”, “Filezilla” oder “WinSCP” herunterladen. Wenn Homegear läuft, startet die Eingabe von homegear in der Shell Homegear ein zweites Mal. Das kann nicht funktionieren.

Die Konfiguration des 433-MHz-CUL darf nur nicht in die Datei homematicbidcos.conf. Diese Datei ist ausschließlich für die Konfiguration von HomeMatic BidCoS gedacht. Ein 433-MHz-Modul macht dort also keinen Sinn. Den 433-MHz-CUL kannst du stattdessen in der intertechno.conf hinzufügen.

Viele Grüße

Sathya

sebami · June 25, 2017, 12:57pm

Hallo Sathya,

Sorry, weis eigentlich auch nicht so genau warum ich das gemacht habe… Das mit dem Log ist eigentlich klar… Anbei nun noch ein Versuch. Habe alles seit dem Neustart von Homegear angefügt:

06/25/17 14:51:26.289 (Shutdown) => Shutdown complete.
06/25/17 14:51:37.567 Starting Homegear...
06/25/17 14:51:37.567 Homegear version 0.7.3-1221
06/25/17 14:51:37.567 Git commit SHA of libhomegear-base: -
06/25/17 14:51:37.568 Git branch of libhomegear-base:     -
06/25/17 14:51:37.568 Git commit SHA of Homegear:         -
06/25/17 14:51:37.568 Git branch of Homegear:             -
06/25/17 14:51:37.569 Info: Setting allowed core file size to "4294967295" for user with id 0 and group with id 0.
06/25/17 14:51:37.569 Info: Core file size now is "4294967295".
06/25/17 14:51:37.569 Info: Setting maximum thread priority to "4294967295" for user with id 0 and group with id 0.
06/25/17 14:51:37.569 Info: Maximum thread priority now is "4294967295".
06/25/17 14:51:37.594 Info: Backing up database...
06/25/17 14:51:38.836 Initializing database...
06/25/17 14:51:38.843 Info: Loading family module mod_homematicbidcos.so
06/25/17 14:51:38.866 /etc/homegear/families/homematicbidcos.conf
06/25/17 14:51:38.868 Info: Loading family module mod_homematicwired.so
06/25/17 14:51:38.879 /etc/homegear/families/homematicwired.conf
06/25/17 14:51:38.880 Info: Loading family module mod_intertechno.so
06/25/17 14:51:38.889 /etc/homegear/families/intertechno.conf
06/25/17 14:51:38.890 Info: Loading family module mod_miscellaneous.so
06/25/17 14:51:38.895 /etc/homegear/families/miscellaneous.conf
06/25/17 14:51:38.896 Info: Setting up physical interfaces and GPIOs...
06/25/17 14:51:38.897 Info: Dropping privileges to user homegear (110) and group homegear (116)
06/25/17 14:51:38.897 Info: Homegear is (now) running as user with id 110 and group with id 116.
06/25/17 14:51:38.898 Starting script engine server...
06/25/17 14:51:38.904 Initializing licensing controller...
06/25/17 14:51:38.904 Loading licensing controller data...
06/25/17 14:51:38.904 Loading devices...
06/25/17 14:51:38.904 Loading XML RPC devices...
06/25/17 14:51:40.091 Loading device 2
06/25/17 14:51:40.091 Module HomeMatic BidCoS: Info: Central address set to 0xFDCFBC.
06/25/17 14:51:40.092 Module HomeMatic BidCoS: Loading peer 1
06/25/17 14:51:40.106 Module HomeMatic BidCoS: Loading peer 2
06/25/17 14:51:40.148 Module HomeMatic BidCoS: Loading peer 3
06/25/17 14:51:40.197 Info: Not initializing device family HomeMatic Wired, because no physical interface was found.
06/25/17 14:51:40.197 Info: Disposing family module mod_homematicwired.so
06/25/17 14:51:40.197 Loading XML RPC devices...
06/25/17 14:51:40.211 Loading device 3
06/25/17 14:51:40.211 Loading XML RPC devices...
06/25/17 14:51:40.213 Loading device 1
06/25/17 14:51:40.214 Initializing RPC client...
06/25/17 14:51:40.214 Starting XML RPC server RPCServer1 listening on :::2001...
06/25/17 14:51:40.216 Starting XML RPC server RPCServer2 listening on :::2002, SSL enabled...
06/25/17 14:51:40.217 RPC Server (Port 2001): Info: RPC Server started listening on address :: and port 2001
06/25/17 14:51:40.249 Starting XML RPC server RPCServer3 listening on :::2003, SSL enabled, authentication enabled...
06/25/17 14:51:40.249 RPC Server (Port 2002): Info: RPC Server started listening on address :: and port 2002
06/25/17 14:51:40.280 Starting CLI server...
06/25/17 14:51:40.280 RPC Server (Port 2003): Info: RPC Server started listening on address :: and port 2003
06/25/17 14:51:40.280 Initializing event handler...
06/25/17 14:51:40.281 Loading events...
06/25/17 14:51:40.284 Starting flows server...
06/25/17 14:51:40.285 Starting IPC server...
06/25/17 14:51:40.288 Start listening for packets...
06/25/17 14:51:42.709 Startup complete. Waiting for physical interfaces to connect.
06/25/17 14:51:42.709 All physical interfaces are connected now.
06/25/17 14:51:42.709 Starting UPnP server...
06/25/17 14:51:42.711 Info: UPnP server: Binding to address: 192.168.178.31
06/25/17 14:51:42.711 UPnP Server: Info: Started listening.
06/25/17 14:51:53.401 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.178.31:53628 accepted. Client number: 11
06/25/17 14:51:53.406 RPC Server (Port 2001): Info: RPC server client id for client number 11 is: 0
06/25/17 14:51:53.407 RPC Server (Port 2001): Info: Client number 11 is calling RPC method: listBidcosInterfaces (2) Parameters:
06/25/17 14:51:53.426 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.178.31:53630 accepted. Client number: 12
06/25/17 14:51:53.427 RPC Server (Port 2001): Info: RPC server client id for client number 12 is: 1
06/25/17 14:51:53.428 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578135:0
(String) MASTER
06/25/17 14:51:53.448 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578135:0
(String) VALUES
06/25/17 14:51:53.461 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578135:4
(String) MASTER
06/25/17 14:51:53.465 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578135:4
(String) VALUES
06/25/17 14:51:53.522 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578135:1
(String) MASTER
06/25/17 14:51:53.525 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578135:1
(String) VALUES
06/25/17 14:51:53.527 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578135:2
(String) MASTER
06/25/17 14:51:53.530 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578135:2
(String) VALUES
06/25/17 14:51:53.533 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578135:3
(String) MASTER
06/25/17 14:51:53.535 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578135:3
(String) VALUES
06/25/17 14:51:53.538 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578135:5
(String) MASTER
06/25/17 14:51:53.541 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578135:5
(String) VALUES
06/25/17 14:51:53.543 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578135:6
(String) MASTER
06/25/17 14:51:53.546 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578135:6
(String) VALUES
06/25/17 14:51:53.618 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:0
(String) MASTER
06/25/17 14:51:53.627 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:0
(String) VALUES
06/25/17 14:51:53.635 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:4
(String) MASTER
06/25/17 14:51:53.637 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:4
(String) VALUES
06/25/17 14:51:53.669 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:1
(String) MASTER
06/25/17 14:51:53.672 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:1
(String) VALUES
06/25/17 14:51:53.675 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:2
(String) MASTER
06/25/17 14:51:53.677 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:2
(String) VALUES
06/25/17 14:51:53.680 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:3
(String) MASTER
06/25/17 14:51:53.683 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:3
(String) VALUES
06/25/17 14:51:53.685 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:5
(String) MASTER
06/25/17 14:51:53.688 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:5
(String) VALUES
06/25/17 14:51:53.691 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:6
(String) MASTER
06/25/17 14:51:53.693 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:6
(String) VALUES
06/25/17 14:51:53.775 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578170:0
(String) MASTER
06/25/17 14:51:53.784 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578170:0
(String) VALUES
06/25/17 14:51:53.791 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578170:4
(String) MASTER
06/25/17 14:51:53.794 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578170:4
(String) VALUES
06/25/17 14:51:53.827 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578170:1
(String) MASTER
06/25/17 14:51:53.830 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578170:1
(String) VALUES
06/25/17 14:51:53.833 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578170:2
(String) MASTER
06/25/17 14:51:53.837 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578170:2
(String) VALUES
06/25/17 14:51:53.840 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578170:3
(String) MASTER
06/25/17 14:51:53.842 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578170:3
(String) VALUES
06/25/17 14:51:53.845 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578170:5
(String) MASTER
06/25/17 14:51:53.848 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578170:5
(String) VALUES
06/25/17 14:51:53.850 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578170:6
(String) MASTER
06/25/17 14:51:53.853 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578170:6
(String) VALUES
06/25/17 14:52:08.944 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: listBidcosInterfaces (2) Parameters:
06/25/17 14:52:23.947 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: listBidcosInterfaces (2) Parameters:
06/25/17 14:52:38.951 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: listBidcosInterfaces (2) Parameters:
06/25/17 14:52:53.954 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: listBidcosInterfaces (2) Parameters:
06/25/17 14:53:08.967 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: listBidcosInterfaces (2) Parameters:
06/25/17 14:53:23.970 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: listBidcosInterfaces (2) Parameters:
06/25/17 14:53:38.973 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: listBidcosInterfaces (2) Parameters:
06/25/17 14:53:53.977 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: listBidcosInterfaces (2) Parameters:
06/25/17 14:54:08.980 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: listBidcosInterfaces (2) Parameters:
06/25/17 14:54:23.984 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: listBidcosInterfaces (2) Parameters:
06/25/17 14:54:38.987 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: listBidcosInterfaces (2) Parameters:

Bzgl. der 433-MHZ-CUL bin ich eigentlich der Meinung diese nur in der intertechno.conf eingebunden zu haben. Oder habe ich da ggf. etwas falsch gemacht!? Kannst Du da was erkennen?

Viele Grüße, Sebastian

sathya · June 26, 2017, 12:05pm

Hallo @sebami,

In deiner geposteten homematicbidcos.conf darf dieser drin, daher die Anmerkung meinerseits. Wenn dieser nur in der intertechno.conf ist, sollte es eigentlich klappen. Außer /dev/ttyUSB0 und /dev/ttyUSB1 sind vertauscht.

Das Log zeigt keine Fehler. Zieh den 433-MHz-CUL mal ab und kommentiere ihn in allen Konfigurationen aus. Klappt es dann? Bzw. sind dann Fehler im Log sichtbar?

Viele Grüße

Sathya

sebami · June 28, 2017, 7:39pm

Hallo Sathya,

Habe den CUL abgezogen und in der intertechno.conf auskommentiert. Anbei schon mal as log

06/28/17 21:21:26.857 Starting flows server...
06/28/17 21:21:26.860 Starting IPC server...
06/28/17 21:21:26.863 Start listening for packets...
06/28/17 21:21:29.274 Startup complete. Waiting for physical interfaces to connect.
06/28/17 21:21:29.274 All physical interfaces are connected now.
06/28/17 21:21:29.274 Starting UPnP server...
06/28/17 21:21:29.275 Info: UPnP server: Binding to address: 192.168.178.31
06/28/17 21:21:29.276 UPnP Server: Info: Started listening.
06/28/17 21:21:58.229 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.178.31:47348 accepted. Client number: 9
06/28/17 21:21:58.230 RPC Server (Port 2001): Info: RPC server client id for client number 9 is: 0
06/28/17 21:21:58.308 RPC Server (Port 2001): Info: Client number 9 is calling RPC method: getDeviceDescription (1) Parameters:
(String) BidCoS-RF
06/28/17 21:21:58.496 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.178.31:47350 accepted. Client number: 10
06/28/17 21:21:58.497 RPC Server (Port 2001): Info: RPC server client id for client number 10 is: 1
06/28/17 21:21:58.500 RPC Server (Port 2001): Info: Client number 10 is calling RPC method: listBidcosInterfaces (1) Parameters:
06/28/17 21:21:58.641 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.178.31:47358 accepted. Client number: 11
06/28/17 21:21:58.642 RPC Server (Port 2001): Info: RPC server client id for client number 11 is: 2
06/28/17 21:21:58.643 RPC Server (Port 2001): Info: Client number 11 is calling RPC method: init (2) Parameters:
(String) binary://192.168.178.31:9126
(String) RF-1786b4a6
06/28/17 21:21:58.644 Info: Adding server "binary://192.168.178.31".
06/28/17 21:21:58.644 Info: Calling init methods on server "binary://192.168.178.31".
06/28/17 21:21:58.676 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.178.31:47360 accepted. Client number: 12
06/28/17 21:21:58.677 RPC Server (Port 2001): Info: RPC server client id for client number 12 is: 3
06/28/17 21:21:58.677 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: listDevices (2) Parameters:
06/28/17 21:21:58.736 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getDeviceInfo (2) Parameters:
06/28/17 21:21:58.759 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamsetDescription (2) Parameters:
(String) MEQ0578135:0
(String) MASTER
06/28/17 21:21:58.855 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamsetDescription (2) Parameters:
(String) MEQ0578135:0
(String) VALUES
06/28/17 21:21:58.873 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamsetDescription (2) Parameters:
(String) MEQ0578135:1
(String) MASTER
06/28/17 21:21:58.877 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamsetDescription (2) Parameters:
(String) MEQ0578135:1
(String) VALUES
06/28/17 21:21:58.880 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamsetDescription (2) Parameters:
(String) MEQ0578135:2
(String) MASTER
06/28/17 21:21:58.883 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamsetDescription (2) Parameters:
(String) MEQ0578135:2
(String) VALUES
06/28/17 21:21:58.885 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamsetDescription (2) Parameters:
(String) MEQ0578135:3
(String) MASTER
06/28/17 21:21:58.888 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamsetDescription (2) Parameters:
(String) MEQ0578135:3
(String) VALUES
06/28/17 21:21:58.891 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamsetDescription (2) Parameters:
(String) MEQ0578135:4
(String) MASTER
06/28/17 21:21:58.896 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamsetDescription (2) Parameters:
(String) MEQ0578135:4
(String) VALUES
06/28/17 21:21:58.992 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamsetDescription (2) Parameters:
(String) MEQ0578135:5
(String) MASTER
06/28/17 21:21:59.001 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamsetDescription (2) Parameters:
(String) MEQ0578135:5
(String) VALUES
06/28/17 21:21:59.006 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamsetDescription (2) Parameters:
(String) MEQ0578135:6
(String) MASTER
06/28/17 21:21:59.021 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamsetDescription (2) Parameters:
(String) MEQ0578135:6
(String) VALUES
06/28/17 21:21:59.188 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getAllSystemVariables (2) Parameters:
06/28/17 21:21:59.192 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getAllScripts (2) Parameters:
06/28/17 21:21:59.270 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578170:0
(String) MASTER
06/28/17 21:21:59.289 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578135:0
(String) MASTER
06/28/17 21:21:59.298 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578170:0
(String) VALUES
06/28/17 21:21:59.301 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578135:0
(String) VALUES
06/28/17 21:21:59.330 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578135:4
(String) MASTER
06/28/17 21:21:59.333 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578170:4
(String) MASTER
06/28/17 21:21:59.336 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578135:4
(String) VALUES
06/28/17 21:21:59.339 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578170:4
(String) VALUES
06/28/17 21:21:59.386 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578135:1
(String) MASTER
06/28/17 21:21:59.389 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578170:1
(String) MASTER
06/28/17 21:21:59.392 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578135:1
(String) VALUES
06/28/17 21:21:59.395 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578170:1
(String) VALUES
06/28/17 21:21:59.404 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578170:2
(String) MASTER
06/28/17 21:21:59.407 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578135:2
(String) MASTER
06/28/17 21:21:59.412 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578135:2
(String) VALUES
06/28/17 21:21:59.416 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578135:3
(String) MASTER
06/28/17 21:21:59.421 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578170:2
(String) VALUES
06/28/17 21:21:59.425 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578170:3
(String) MASTER
06/28/17 21:21:59.428 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578170:3
(String) VALUES
06/28/17 21:21:59.432 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578170:5
(String) MASTER
06/28/17 21:21:59.435 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578135:3
(String) VALUES
06/28/17 21:21:59.448 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578135:5
(String) MASTER
06/28/17 21:21:59.453 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578135:5
(String) VALUES
06/28/17 21:21:59.457 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578170:5
(String) VALUES
06/28/17 21:21:59.463 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578135:6
(String) MASTER
06/28/17 21:21:59.465 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578170:6
(String) MASTER
06/28/17 21:21:59.468 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578135:6
(String) VALUES
06/28/17 21:21:59.470 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578170:6
(String) VALUES
06/28/17 21:21:59.600 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:0
(String) MASTER
06/28/17 21:21:59.611 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:0
(String) VALUES
06/28/17 21:21:59.619 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:4
(String) MASTER
06/28/17 21:21:59.623 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:4
(String) VALUES
06/28/17 21:21:59.650 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:1
(String) MASTER
06/28/17 21:21:59.653 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:1
(String) VALUES
06/28/17 21:21:59.656 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:2
(String) MASTER
06/28/17 21:21:59.659 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:2
(String) VALUES
06/28/17 21:21:59.663 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:3
(String) MASTER
06/28/17 21:21:59.666 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:3
(String) VALUES
06/28/17 21:21:59.670 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:5
(String) MASTER
06/28/17 21:21:59.673 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:5
(String) VALUES
06/28/17 21:21:59.676 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:6
(String) MASTER
06/28/17 21:21:59.679 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:6
(String) VALUES
06/28/17 21:22:28.653 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: listBidcosInterfaces (2) Parameters:

Leider geht es ein paar Minuten später wieder nicht. Hier das log zu der Zeit:

(String) MEQ0577914:0
(String) VALUES
06/28/17 21:30:00.362 RPC Server (Port 2001): Info: Client number 25 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:4
(String) MASTER
06/28/17 21:30:00.365 RPC Server (Port 2001): Info: Client number 25 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:4
(String) VALUES
06/28/17 21:30:00.379 RPC Server (Port 2001): Info: Client number 25 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:1
(String) MASTER
06/28/17 21:30:00.382 RPC Server (Port 2001): Info: Client number 25 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:1
(String) VALUES
06/28/17 21:30:00.385 RPC Server (Port 2001): Info: Client number 25 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:2
(String) MASTER
06/28/17 21:30:00.387 RPC Server (Port 2001): Info: Client number 25 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:2
(String) VALUES
06/28/17 21:30:00.390 RPC Server (Port 2001): Info: Client number 25 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:3
(String) MASTER
06/28/17 21:30:00.392 RPC Server (Port 2001): Info: Client number 25 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:3
(String) VALUES
06/28/17 21:30:00.395 RPC Server (Port 2001): Info: Client number 25 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:5
(String) MASTER
06/28/17 21:30:00.397 RPC Server (Port 2001): Info: Client number 25 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:5
(String) VALUES
06/28/17 21:30:00.400 RPC Server (Port 2001): Info: Client number 25 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:6
(String) MASTER
06/28/17 21:30:00.402 RPC Server (Port 2001): Info: Client number 25 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:6
(String) VALUES
06/28/17 21:30:13.771 RPC Server (Port 2001): Info: Client number 25 is calling RPC method: listBidcosInterfaces (2) Parameters:
06/28/17 21:30:28.775 RPC Server (Port 2001): Info: Client number 25 is calling RPC method: listBidcosInterfaces (2) Parameters:
06/28/17 21:30:43.778 RPC Server (Port 2001): Info: Client number 25 is calling RPC method: listBidcosInterfaces (2) Parameters:
06/28/17 21:30:58.782 RPC Server (Port 2001): Info: Client number 25 is calling RPC method: listBidcosInterfaces (2) Parameters:
06/28/17 21:31:00.490 RPC Server (Port 2001): Info: Client number 25 is calling RPC method: init (2) Parameters:
(String) binary://192.168.178.31:9126
06/28/17 21:31:00.490 Info: Removing server "binary://192.168.178.31".
06/28/17 21:31:13.785 RPC Server (Port 2001): Info: Client number 25 is calling RPC method: listBidcosInterfaces (2) Parameters:
06/28/17 21:31:26.031 Info: Peer 1 is set to unreachable, because no packet was received within 600 seconds. The Last packet was received at 01/18/70 09:17:57.685
06/28/17 21:31:26.032 Module HomeMatic BidCoS: CUL "My-CUL": Info: Sending (My-CUL): 0B0DB001FDCFBC3D81A40006
06/28/17 21:31:26.592 Module HomeMatic BidCoS: CUL "My-CUL": Info: Sending (My-CUL): 0B0DB001FDCFBC3D81A40006
06/28/17 21:31:27.030 Info: Peer 2 is set to unreachable, because no packet was received within 600 seconds. The Last packet was received at 01/18/70 09:17:57.685
06/28/17 21:31:27.031 Module HomeMatic BidCoS: CUL "My-CUL": Info: Sending (My-CUL): 0B09B001FDCFBC3D81870006
06/28/17 21:31:27.033 Module HomeMatic BidCoS: CUL "My-CUL": Info: Sending (My-CUL): 0B0DB001FDCFBC3D81A40006
06/28/17 21:31:27.152 Module HomeMatic BidCoS: CUL "My-CUL": Info: Sending (My-CUL): 0B0DB001FDCFBC3D81A40006
06/28/17 21:31:27.591 Module HomeMatic BidCoS: CUL "My-CUL": Info: Sending (My-CUL): 0B09B001FDCFBC3D81870006
06/28/17 21:31:27.593 Module HomeMatic BidCoS: CUL "My-CUL": Info: Sending (My-CUL): 0B0DB001FDCFBC3D81A40006
06/28/17 21:31:28.029 Info: Peer 3 is set to unreachable, because no packet was received within 600 seconds. The Last packet was received at 01/18/70 09:17:57.686
06/28/17 21:31:28.029 Module HomeMatic BidCoS: CUL "My-CUL": Info: Sending (My-CUL): 0B07B001FDCFBC3C366F0006
06/28/17 21:31:28.031 Module HomeMatic BidCoS: CUL "My-CUL": Info: Sending (My-CUL): 0B09B001FDCFBC3D81870006
06/28/17 21:31:28.034 Module HomeMatic BidCoS: CUL "My-CUL": Info: Sending (My-CUL): 0B0DB001FDCFBC3D81A40006
06/28/17 21:31:28.151 Module HomeMatic BidCoS: CUL "My-CUL": Info: Sending (My-CUL): 0B09B001FDCFBC3D81870006
06/28/17 21:31:28.153 Module HomeMatic BidCoS: CUL "My-CUL": Info: Sending (My-CUL): 0B0DB001FDCFBC3D81A40006
06/28/17 21:31:28.589 Module HomeMatic BidCoS: CUL "My-CUL": Info: Sending (My-CUL): 0B07B001FDCFBC3C366F0006
06/28/17 21:31:28.591 Module HomeMatic BidCoS: CUL "My-CUL": Info: Sending (My-CUL): 0B09B001FDCFBC3D81870006
06/28/17 21:31:28.594 Module HomeMatic BidCoS: CUL "My-CUL": Info: Sending (My-CUL): 0B0DB001FDCFBC3D81A40006
06/28/17 21:31:28.789 RPC Server (Port 2001): Info: Client number 25 is calling RPC method: listBidcosInterfaces (2) Parameters:
06/28/17 21:31:29.030 Module HomeMatic BidCoS: CUL "My-CUL": Info: Sending (My-CUL): 0B07B001FDCFBC3C366F0006
06/28/17 21:31:29.032 Module HomeMatic BidCoS: CUL "My-CUL": Info: Sending (My-CUL): 0B09B001FDCFBC3D81870006
06/28/17 21:31:29.149 Module HomeMatic BidCoS: CUL "My-CUL": Info: Sending (My-CUL): 0B07B001FDCFBC3C366F0006
06/28/17 21:31:29.151 Module HomeMatic BidCoS: CUL "My-CUL": Info: Sending (My-CUL): 0B09B001FDCFBC3D81870006
06/28/17 21:31:29.154 Module HomeMatic BidCoS: CUL "My-CUL": Info: Sending (My-CUL): 0B0DB001FDCFBC3D81A40006
06/28/17 21:31:29.590 Module HomeMatic BidCoS: CUL "My-CUL": Info: Sending (My-CUL): 0B07B001FDCFBC3C366F0006
06/28/17 21:31:29.592 Module HomeMatic BidCoS: CUL "My-CUL": Info: Sending (My-CUL): 0B09B001FDCFBC3D81870006
06/28/17 21:31:30.031 Module HomeMatic BidCoS: CUL "My-CUL": Info: Sending (My-CUL): 0B07B001FDCFBC3C366F0006
06/28/17 21:31:30.150 Module HomeMatic BidCoS: CUL "My-CUL": Info: Sending (My-CUL): 0B07B001FDCFBC3C366F0006
06/28/17 21:31:30.152 Module HomeMatic BidCoS: CUL "My-CUL": Info: Sending (My-CUL): 0B09B001FDCFBC3D81870006
06/28/17 21:31:30.591 Module HomeMatic BidCoS: CUL "My-CUL": Info: Sending (My-CUL): 0B07B001FDCFBC3C366F0006
06/28/17 21:31:31.151 Module HomeMatic BidCoS: CUL "My-CUL": Info: Sending (My-CUL): 0B07B001FDCFBC3C366F0006
06/28/17 21:31:43.792 RPC Server (Port 2001): Info: Client number 25 is calling RPC method: listBidcosInterfaces (2) Parameters:
06/28/17 21:31:58.795 RPC Server (Port 2001): Info: Client number 25 is calling RPC method: listBidcosInterfaces (2) Parameters:
06/28/17 21:32:00.501 RPC Server (Port 2001): Info: Client number 25 is calling RPC method: init (2) Parameters:
(String) binary://192.168.178.31:9126
06/28/17 21:32:00.505 RPC Server (Port 2001): Info: Client number 25 is calling RPC method: init (2) Parameters:
(String) binary://192.168.178.31:9126
(String) RF-1786b4a6
06/28/17 21:32:00.506 Info: Adding server "binary://192.168.178.31".
06/28/17 21:32:00.506 Info: Calling init methods on server "binary://192.168.178.31".
06/28/17 21:32:00.514 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.178.31:47454 accepted. Client number: 28
06/28/17 21:32:00.515 RPC Server (Port 2001): Info: RPC server client id for client number 28 is: 9
06/28/17 21:32:00.515 RPC Server (Port 2001): Info: Client number 28 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578135:0
(String) MASTER
06/28/17 21:32:00.529 RPC Server (Port 2001): Info: Client number 28 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578135:0
(String) VALUES
06/28/17 21:32:00.535 RPC Server (Port 2001): Info: Client number 28 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578170:0
(String) MASTER
06/28/17 21:32:00.549 RPC Server (Port 2001): Info: Client number 28 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578170:0
(String) VALUES
06/28/17 21:32:00.555 RPC Server (Port 2001): Info: Client number 28 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:0
(String) MASTER
06/28/17 21:32:00.569 RPC Server (Port 2001): Info: Client number 28 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:0
(String) VALUES
06/28/17 21:32:13.802 RPC Server (Port 2001): Info: Client number 28 is calling RPC method: listBidcosInterfaces (2) Parameters:
06/28/17 21:32:28.805 RPC Server (Port 2001): Info: Client number 28 is calling RPC method: listBidcosInterfaces (2) Parameters:
06/28/17 21:32:43.809 RPC Server (Port 2001): Info: Client number 28 is calling RPC method: listBidcosInterfaces (2) Parameters:
06/28/17 21:32:58.812 RPC Server (Port 2001): Info: Client number 28 is calling RPC method: listBidcosInterfaces (2) Parameters:
06/28/17 21:33:00.576 RPC Server (Port 2001): Info: Client number 28 is calling RPC method: init (2) Parameters:
(String) binary://192.168.178.31:9126
06/28/17 21:33:00.576 Info: Removing server "binary://192.168.178.31".
06/28/17 21:33:00.581 RPC Server (Port 2001): Info: Client number 28 is calling RPC method: init (2) Parameters:
(String) binary://192.168.178.31:9126
(String) RF-1786b4a6
06/28/17 21:33:00.581 Info: Adding server "binary://192.168.178.31".
06/28/17 21:33:00.582 Info: Calling init methods on server "binary://192.168.178.31".
06/28/17 21:33:00.590 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.178.31:47464 accepted. Client number: 31
06/28/17 21:33:00.590 RPC Server (Port 2001): Info: RPC server client id for client number 31 is: 10
06/28/17 21:33:00.591 RPC Server (Port 2001): Info: Client number 31 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578135:0
(String) MASTER
06/28/17 21:33:00.603 RPC Server (Port 2001): Info: Client number 31 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578135:0
(String) VALUES
06/28/17 21:33:00.608 RPC Server (Port 2001): Info: Client number 31 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578170:0
(String) MASTER
06/28/17 21:33:00.620 RPC Server (Port 2001): Info: Client number 31 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578170:0
(String) VALUES
06/28/17 21:33:00.624 RPC Server (Port 2001): Info: Client number 31 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:0
(String) MASTER
06/28/17 21:33:00.636 RPC Server (Port 2001): Info: Client number 31 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:0
(String) VALUES
06/28/17 21:33:13.819 RPC Server (Port 2001): Info: Client number 31 is calling RPC method: listBidcosInterfaces (2) Parameters:
06/28/17 21:33:28.822 RPC Server (Port 2001): Info: Client number 31 is calling RPC method: listBidcosInterfaces (2) Parameters:
06/28/17 21:33:43.826 RPC Server (Port 2001): Info: Client number 31 is calling RPC method: listBidcosInterfaces (2) Parameters:
06/28/17 21:33:58.829 RPC Server (Port 2001): Info: Client number 31 is calling RPC method: listBidcosInterfaces (2) Parameters:
06/28/17 21:34:00.642 RPC Server (Port 2001): Info: Client number 31 is calling RPC method: init (2) Parameters:
(String) binary://192.168.178.31:9126
06/28/17 21:34:00.642 Info: Removing server "binary://192.168.178.31".
06/28/17 21:34:00.646 RPC Server (Port 2001): Info: Client number 31 is calling RPC method: init (2) Parameters:
(String) binary://192.168.178.31:9126
(String) RF-1786b4a6
06/28/17 21:34:00.647 Info: Adding server "binary://192.168.178.31".
06/28/17 21:34:00.648 Info: Calling init methods on server "binary://192.168.178.31".
06/28/17 21:34:00.652 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.178.31:47474 accepted. Client number: 34
06/28/17 21:34:00.653 RPC Server (Port 2001): Info: RPC server client id for client number 34 is: 11
06/28/17 21:34:00.653 RPC Server (Port 2001): Info: Client number 34 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578135:0
(String) MASTER
06/28/17 21:34:00.666 RPC Server (Port 2001): Info: Client number 34 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578135:0
(String) VALUES
06/28/17 21:34:00.672 RPC Server (Port 2001): Info: Client number 34 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578170:0
(String) MASTER
06/28/17 21:34:00.685 RPC Server (Port 2001): Info: Client number 34 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578170:0
(String) VALUES
06/28/17 21:34:00.689 RPC Server (Port 2001): Info: Client number 34 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:0
(String) MASTER
06/28/17 21:34:00.702 RPC Server (Port 2001): Info: Client number 34 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:0
(String) VALUES
06/28/17 21:34:13.836 RPC Server (Port 2001): Info: Client number 34 is calling RPC method: listBidcosInterfaces (2) Parameters:
06/28/17 21:34:28.839 RPC Server (Port 2001): Info: Client number 34 is calling RPC method: listBidcosInterfaces (2) Parameters:
06/28/17 21:34:43.842 RPC Server (Port 2001): Info: Client number 34 is calling RPC method: listBidcosInterfaces (2) Parameters:
06/28/17 21:34:58.846 RPC Server (Port 2001): Info: Client number 34 is calling RPC method: listBidcosInterfaces (2) Parameters:
06/28/17 21:35:00.707 RPC Server (Port 2001): Info: Client number 34 is calling RPC method: init (2) Parameters:
(String) binary://192.168.178.31:9126
06/28/17 21:35:00.707 Info: Removing server "binary://192.168.178.31".
06/28/17 21:35:00.712 RPC Server (Port 2001): Info: Client number 34 is calling RPC method: init (2) Parameters:
(String) binary://192.168.178.31:9126
(String) RF-1786b4a6
06/28/17 21:35:00.712 Info: Adding server "binary://192.168.178.31".
06/28/17 21:35:00.713 Info: Calling init methods on server "binary://192.168.178.31".
06/28/17 21:35:00.719 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.178.31:47492 accepted. Client number: 37
06/28/17 21:35:00.719 RPC Server (Port 2001): Info: RPC server client id for client number 37 is: 12
06/28/17 21:35:00.720 RPC Server (Port 2001): Info: Client number 37 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578135:0
(String) MASTER
06/28/17 21:35:00.733 RPC Server (Port 2001): Info: Client number 37 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578135:0
(String) VALUES
06/28/17 21:35:00.737 RPC Server (Port 2001): Info: Client number 37 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578170:0
(String) MASTER
06/28/17 21:35:00.749 RPC Server (Port 2001): Info: Client number 37 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578170:0
(String) VALUES
06/28/17 21:35:00.753 RPC Server (Port 2001): Info: Client number 37 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:0
(String) MASTER
06/28/17 21:35:00.766 RPC Server (Port 2001): Info: Client number 37 is calling RPC method: getParamset (2) Parameters:

Wenn Du jetzt nichts findest würde ich das System nun noch mal neu aufsetzen, von Anfang mit der Intertechno Komponente. Vielleicht geht es ja dann…

VG, Sebastian

sathya · July 1, 2017, 6:27pm

Hallo @sebami,

ich sehe kein einziges empfangenes Paket in den Logs. Wenn du die Anlerntaste auf einem deiner Geräte oder einen Fernbedienungsknopf drückst, taucht dann ein Paket im Log auf?

Den nanoCUL kannst du auch mit “screen” testen:

screen /dev/ttyUSB0 56400

Dann dort eingeben:

Ar<Return>

Jetzt sollten dort Pakete von deinen Geräten geloggt werden. Beenden mit [Strg]+[a], “:quit”.

Viele Grüße

Sathya

sebami · August 2, 2017, 8:16pm

Hallo Sathya,

Nachdem ich etwas die Lust verloren hatte weiter zu suchen habe ich mich vor ein paar Tagen wieder an mein System gesetzt und war endlich erfolgreich

Was genau das Problem war weis ich nicht, aber nach einem kurzem Umweg über FHEM habe ich jetzt sowohl meine Homematic Komponenten als auch meine Intertechno Steckdoesen über Homegear am laufen! Zumindest bei Intertechno kenne ich das Problem, ich hatte die falsche Baudrate eingestellt…

Eine Frage bleibt aber: Intertechno ist unzuverlässig. Scheinbar kommt nicht jeder Befehl an, die Steckdosen schalten nicht immer. Hast Du eine Idee was ich machen kann?

Vielen Dank,
Sebastian

sathya · August 11, 2017, 10:21am

Hallo @sebami,

Intertechno ist leider unidirektional und nutzt Amplitudenmodulation. Durch ersteres kann nicht festgestellt werden, ob ein Paket tatsächlich angekommen ist, letzteres verringert die Reichweite.

Funktioniert es bereits unzuverlässig, wenn CUL und Intertechnosteckdose im gleichen Raum sind? Eine gute Antenne hilft sicherlich. Ansonsten kannst du noch in der intertechno.conf mit additionalCommands rumspielen (siehe dazu http://culfw.de/commandref.html#cmd_i). Mit isr kannst du die Anzahl der Paketsendewiederholungen setzen. Mit it kannst du Zeit für einen Wellenpuls verändern.

Viele Grüße

Sathya

sebami · August 11, 2017, 1:20pm

Hallo Sathya,

Vielen Dank, das werde ich probieren.

Leider hat sich aber in der Zwischenzeit ein neues Problem ergeben. Nach dem der aktuelle Aufbau (3 Intertechno Steckdosen und ein Homematic Thermostate) lief, wollte ich nun meine weiteren Homematic Thermostate sowie eine weitere IT Steckdose einbinden. Seit dem (zumindest ist es mir dann aufgefallen) funktionieren meine Homematic Thermostate nicht mehr… Sie werden grundsätzlich angezeigt, ich kann in Openhab2 auch Werte wie Temperatur oder Signalstärke auslesen, aber sobald ich die Temperatur setzen will geht das Gerät kurz auf unreach. Hier die 100 letzten Einträge des Log dazu, dort ist das auch zu erkennen, für mich als Laien aber nicht warum:

(String) VALUES
08/11/17 15:18:34.392 RPC Server (Port 2001): Info: Client number 1037 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:3
(String) VALUES
08/11/17 15:18:34.395 RPC Server (Port 2001): Info: Client number 1037 is calling RPC method: getParamset (2) Parameters:
(String) ITD0073559F:0
(String) MASTER
08/11/17 15:18:34.398 RPC Server (Port 2001): Info: Client number 1037 is calling RPC method: listDevices (2) Parameters:
08/11/17 15:18:34.432 RPC Server (Port 2001): Info: Client number 1037 is calling RPC method: getParamset (2) Parameters:
(String) ITD0073559F:0
(String) VALUES
08/11/17 15:18:34.436 RPC Server (Port 2001): Info: Client number 1037 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:4
(String) MASTER
08/11/17 15:18:34.438 RPC Server (Port 2001): Info: Client number 1037 is calling RPC method: getDeviceInfo (2) Parameters:
08/11/17 15:18:34.469 RPC Server (Port 2001): Info: Client number 1037 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:4
(String) VALUES
08/11/17 15:18:34.473 RPC Server (Port 2001): Info: Client number 1037 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:5
(String) MASTER
08/11/17 15:18:34.476 RPC Server (Port 2001): Info: Client number 1037 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:5
(String) VALUES
08/11/17 15:18:34.479 RPC Server (Port 2001): Info: Client number 1037 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:6
(String) MASTER
08/11/17 15:18:34.482 RPC Server (Port 2001): Info: Client number 1037 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:6
(String) VALUES
08/11/17 15:18:34.497 RPC Server (Port 2001): Info: Client number 1037 is calling RPC method: getParamsetDescription (2) Parameters:
(String) ITD007372FE:0
(String) MASTER
08/11/17 15:18:34.500 RPC Server (Port 2001): Info: Client number 1037 is calling RPC method: getParamsetDescription (2) Parameters:
(String) ITD007372FE:0
(String) VALUES
08/11/17 15:18:34.503 RPC Server (Port 2001): Info: Client number 1037 is calling RPC method: getParamsetDescription (2) Parameters:
(String) ITD007372FE:1
(String) MASTER
08/11/17 15:18:34.506 RPC Server (Port 2001): Info: Client number 1037 is calling RPC method: getParamsetDescription (2) Parameters:
(String) ITD007372FE:1
(String) VALUES
08/11/17 15:18:34.510 RPC Server (Port 2001): Info: Client number 1037 is calling RPC method: listDevices (2) Parameters:
08/11/17 15:18:34.545 RPC Server (Port 2001): Info: Client number 1037 is calling RPC method: getDeviceInfo (2) Parameters:
08/11/17 15:18:34.576 RPC Server (Port 2001): Info: Client number 1037 is calling RPC method: getParamsetDescription (2) Parameters:
(String) ITD00737B6A:0
(String) MASTER
08/11/17 15:18:34.579 RPC Server (Port 2001): Info: Client number 1037 is calling RPC method: getParamsetDescription (2) Parameters:
(String) ITD00737B6A:0
(String) VALUES
08/11/17 15:18:34.582 RPC Server (Port 2001): Info: Client number 1037 is calling RPC method: getParamsetDescription (2) Parameters:
(String) ITD00737B6A:1
(String) MASTER
08/11/17 15:18:34.584 RPC Server (Port 2001): Info: Client number 1037 is calling RPC method: getParamsetDescription (2) Parameters:
(String) ITD00737B6A:1
(String) VALUES
08/11/17 15:18:34.589 RPC Server (Port 2001): Info: Client number 1037 is calling RPC method: listDevices (2) Parameters:
08/11/17 15:18:34.639 RPC Server (Port 2001): Info: Client number 1037 is calling RPC method: getDeviceInfo (2) Parameters:
08/11/17 15:18:34.671 RPC Server (Port 2001): Info: Client number 1037 is calling RPC method: getParamsetDescription (2) Parameters:
(String) ITD00735598:0
(String) MASTER
08/11/17 15:18:34.673 RPC Server (Port 2001): Info: Client number 1037 is calling RPC method: getParamsetDescription (2) Parameters:
(String) ITD00735598:0
(String) VALUES
08/11/17 15:18:34.676 RPC Server (Port 2001): Info: Client number 1037 is calling RPC method: getParamsetDescription (2) Parameters:
(String) ITD00735598:1
(String) MASTER
08/11/17 15:18:34.679 RPC Server (Port 2001): Info: Client number 1037 is calling RPC method: getParamsetDescription (2) Parameters:
(String) ITD00735598:1
(String) VALUES
08/11/17 15:18:34.684 RPC Server (Port 2001): Info: Client number 1037 is calling RPC method: getParamset (2) Parameters:
(String) ITD007372FE:0
(String) MASTER
08/11/17 15:18:34.687 RPC Server (Port 2001): Info: Client number 1037 is calling RPC method: getParamset (2) Parameters:
(String) ITD007372FE:0
(String) VALUES
08/11/17 15:18:34.924 RPC Server (Port 2001): Info: Client number 1037 is calling RPC method: getParamset (2) Parameters:
(String) ITD00737B6A:0
(String) MASTER
08/11/17 15:18:34.927 RPC Server (Port 2001): Info: Client number 1037 is calling RPC method: getParamset (2) Parameters:
(String) ITD00737B6A:0
(String) VALUES
08/11/17 15:18:35.143 RPC Server (Port 2001): Info: Client number 1037 is calling RPC method: listBidcosInterfaces (2) Parameters:
08/11/17 15:18:50.146 RPC Server (Port 2001): Info: Client number 1037 is calling RPC method: listBidcosInterfaces (2) Parameters:
08/11/17 15:19:05.150 RPC Server (Port 2001): Info: Client number 1037 is calling RPC method: listBidcosInterfaces (2) Parameters:
08/11/17 15:19:15.615 RPC Server (Port 2001): Info: Client number 1037 is calling RPC method: setValue (2) Parameters:
(String) MEQ0578135:4
(String) SET_TEMPERATURE
(Float) 20
08/11/17 15:19:15.618 Module HomeMatic BidCoS: CUL "My-CUL": Info: Sending (My-CUL): 0C2CB011FDFAA93D8187860428
08/11/17 15:19:16.178 Module HomeMatic BidCoS: CUL "My-CUL": Info: Sending (My-CUL): 0C2CB011FDFAA93D8187860428
08/11/17 15:19:16.738 Module HomeMatic BidCoS: CUL "My-CUL": Info: Sending (My-CUL): 0C2CB011FDFAA93D8187860428
08/11/17 15:19:18.178 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.178.31:37860 accepted. Client number: 1040
08/11/17 15:19:18.179 RPC Server (Port 2001): Info: RPC server client id for client number 1040 is: 336
08/11/17 15:19:18.180 RPC Server (Port 2001): Info: Client number 1040 is calling RPC method: setValue (2) Parameters:
(String) MEQ0578135:4
(String) SET_TEMPERATURE
(Float) 20
08/11/17 15:19:20.742 RPC Server (Port 2001): Info: Client number 1040 is calling RPC method: listBidcosInterfaces (2) Parameters:
08/11/17 15:19:20.825 Module HomeMatic BidCoS: Info: Setting peer to unreachable, because the queue processing was interrupted.

Ich habe die Devices bereits “ungepairt” und wieder neu verbunden, das System neu gestartet, auch komplett vom Strom genommen, aber nichts hat geholfen

Vielen Dank,
Sebastian

sathya · August 11, 2017, 4:06pm

Hallo @sebami,

bist du dir sicher, dass für Intertechno der 433MHz-CUL und für HomeMatic der 868MHz-CUL verwendet wird? Das kann nämlich wechseln, also mal ist der eine, mal der andere /dev/ttyUSB0. Ein Ausweg ist die Einbindung über /dev/serial/by-id/ (oder hast du das schon so eingerichtet?). Probier mal, ob es klappt, wenn du nur den HomeMatic-CUL verwendest.

Viele Grüße

Sathya

sebami · August 11, 2017, 7:22pm

Hallo Sathya,

Das war tatsächlich das Problem! Vielen Dank!! Über das Thema wa ich so noch nie gestolpert, jetzt weis ich wie es geht

Das einzige Problem das ich jetzt noch habe ist das einbinden weiterer Intertechno Steckdosen. Die ersten drei konnte ich erst einbinden, nachdem ich sie ein mal in FHEM laufen hatte (was problemlos ging). Ich hatte mir den Code notiert und dann umgerechnet für homegear verwendet. Meine vierte Dose lief nie in FHEM und nun bekomme ich sie nicht bei homegear eingebunden. Kann das sein? Ich habe einen willkürlichen Code gewählt und auch schon mehrere probiert. Die Dosen sind alle neue Bauart, ich verstehe nicht was das Problem sein könnte. Bin kurz davor noch mal FHEM aufzusetzen und es darüber erneut zu probieren.

VG, Sebastian