Nano CUL & openHAB2 & homegear - kein Pairing

[wero]

Hallo,

ich habe einen Raspberry mit OpenHAB2, Homegear und einen Nano CUL.
Alles soweit problemlos konfiguriert.
Ich bekomme aber kein Pairing mit Homematic oder Max Geräten.

Wäre super, wenn mir jemand einen Hinweis zur Ursache geben kann.

Das ist mein /etc//homegear/homematicbidcos.conf:

[CUL]
id = 868
default = true
deviceType = cul
device = /dev/ttyUSB1
responseDelay = 95

Und die homegear.log:
10/12/18 23:17:40.358 IPC Server: Info: Connection accepted. Client number: 8
10/12/18 23:17:40.359 IPC Server: Info: Client 0 successfully registered RPC method “cliOutput” (this method is registered by 1 client(s)).
10/12/18 23:17:40.359 IPC Server: Info: Client 0 successfully registered RPC method “cliOutput-0” (this method is registered by 1 client(s)).
10/12/18 23:17:44.361 IPC Server: Info: Client number 0 is calling RPC method: familyExists Parameters:
(Integer64) 0
10/12/18 23:17:57.894 HomeMatic BidCoS packet received (868, RSSI: -46 dBm): 1A0884005E4C8C0000002B006A4F45513133303835303730010100
10/12/18 23:17:57.895 Module HomeMatic BidCoS: Info: Pushing pending queues.
10/12/18 23:17:57.988 Module HomeMatic BidCoS: CUL “868”: Info: Sending (868): 1001A001FD00015E4C8C00050000000000
10/12/18 23:17:58.188 Module HomeMatic BidCoS: CUL “868”: Info: Sending (868): 1001A001FD00015E4C8C00050000000000
10/12/18 23:17:58.388 Module HomeMatic BidCoS: CUL “868”: Info: Sending (868): 1001A001FD00015E4C8C00050000000000
10/12/18 23:18:34.412 IPC Server: Info: Client number 0 is calling RPC method: familyExists Parameters:
(Integer64) 4
10/12/18 23:19:42.829 IPC Server: Info: Connection to IPC server’s client number 8 closed.
10/12/18 23:20:17.679 IPC Server: Info: IPC client 0 removed.

[pmayer]

Hey @wero,

zeig mal bitte den oberen Teil deiner homematicbidcos.conf, natürlich mit anonymisiertem Schlüssel.

Außerdem ist Max! nicht mit Homematic kompatibel, auch wenn sie mit dem selben Funkmodul (nicht gleichzeitig) funktionieren.
Um Max-Geräte zu nutzen brauchst du homegear-max und musst entsprechend die Einstellungen in der max.conf machen.

Gruß,
Patrik

[wero]

Man kann doch nach meinem Verständnis mit families select 4 auch Max bei homegear pairen.

[General]
centralAdress = 0xFD0001
currentRfKeyIndex = 1
processBroadcastWithAesEnabled = false

[wero]

aber stimmt, da ist ja noch eine Max.conf

Grüße Welf

[pmayer]

Benutz doch bitte die Formatierungsfunktionen des Forums:

Man kann doch nach meinem Verständnis mit families select 4 auch Max bei homegear pairen.

Ja, dafür muss die family Max! (4) aber installiert und konfiguriert sein und ein eigenes Kommunikationsmodul haben:

pi@homegearpi-31-91-85:~$ sudo homegear -r
Connected to Homegear (version 0.7.26-1810).

Please type >>help<< to list all available commands.
> ls
   ID │ Name                          
──────┼───────────────────────────────
    0 │ HomeMatic BidCoS              
    4 │ MAX!                          
    5 │ Philips hue                   
   15 │ EnOcean                       
  254 │ Miscellaneous                 
──────┴───────────────────────────────
>

[wero]

MAX und andere Module sind installiert:

Please type >>help<< to list all available commands.

ls
ID │ Name
──────┼───────────────────────────────
0 │ HomeMatic BidCoS
1 │ HomeMatic Wired
2 │ Insteon
4 │ MAX!
6 │ Sonos
9 │ Kodi
10 │ IPCam
11 │ Beckhoff
14 │ KNX
15 │ EnOcean
16 │ Intertechno
254 │ Miscellaneous
──────┴───────────────────────────────

Die max.conf sieht jetzt so aus:

[General]

moduleEnabled = true

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

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

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

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

## Options: cul, coc, cc1100
deviceType = cul

device = /dev/ttyUSB1

## Should be "40" for MAX!
responseDelay = 40

Und nach Neustart und Pairing-Versuch mit Max-Fensterkontakt folgende Einträge in der homegear.log:

    10/13/18 22:50:56.228 Starting Homegear...
10/13/18 22:50:56.231 Homegear version 0.7.30-1900
10/13/18 22:50:56.231 Git commit SHA of libhomegear-base: -
10/13/18 22:50:56.231 Git branch of libhomegear-base:     -
10/13/18 22:50:56.231 Git commit SHA of Homegear:         -
10/13/18 22:50:56.231 Git branch of Homegear:             -
10/13/18 22:50:56.233 Info: Setting allowed core file size to "4294967295" for user with id 0 and group with id 0.
10/13/18 22:50:56.233 Info: Core file size now is "4294967295".
10/13/18 22:50:56.233 Info: Setting maximum thread priority to "4294967295" for user with id 0 and group with id 0.
10/13/18 22:50:56.233 Info: Maximum thread priority now is "4294967295".
10/13/18 22:50:56.349 Info: Backing up database...
10/13/18 22:50:56.586 Initializing database...
10/13/18 22:50:56.626 Info: Loading family module mod_ipcam.so
10/13/18 22:50:56.667 /etc/homegear/families/ipcam.conf
10/13/18 22:50:56.700 Info: Loading family module mod_kodi.so
10/13/18 22:50:56.750 /etc/homegear/families/kodi.conf
10/13/18 22:50:56.754 Info: Loading family module mod_homematicbidcos.so
10/13/18 22:50:56.830 /etc/homegear/families/homematicbidcos.conf
10/13/18 22:50:56.863 Info: Loading family module mod_miscellaneous.so
10/13/18 22:50:56.897 /etc/homegear/families/miscellaneous.conf
10/13/18 22:50:56.897 Info: Loading family module mod_knx.so
10/13/18 22:50:56.949 /etc/homegear/families/knx.conf
10/13/18 22:50:56.950 Info: Loading family module mod_beckhoff.so
10/13/18 22:50:56.966 /etc/homegear/families/beckhoff.conf
10/13/18 22:50:56.971 Module Beckhoff: Error in file Interfaces.cpp line 45 in function virtual void MyFamily::Interfaces::create(): The $
10/13/18 22:50:56.992 Info: Loading family module mod_intertechno.so
10/13/18 22:50:57.023 /etc/homegear/families/intertechno.conf
10/13/18 22:50:57.027 Info: Loading family module mod_homematicwired.so
10/13/18 22:50:57.054 /etc/homegear/families/homematicwired.conf
10/13/18 22:50:57.063 Info: Loading family module mod_insteon.so
10/13/18 22:50:57.108 /etc/homegear/families/insteon.conf
10/13/18 22:50:57.117 Info: Loading family module mod_sonos.so
10/13/18 22:50:57.143 /etc/homegear/families/sonos.conf
10/13/18 22:50:57.149 Info: Loading family module mod_philipshue.so
10/13/18 22:50:57.166 /etc/homegear/families/philipshue.conf
10/13/18 22:50:57.172 Info: Loading family module mod_max.so
10/13/18 22:50:57.233 /etc/homegear/families/max.conf
10/13/18 22:50:57.246 Info: Loading family module mod_enocean.so
10/13/18 22:50:57.302 /etc/homegear/families/enocean.conf
10/13/18 22:50:57.309 Info: Setting up physical interfaces and GPIOs...
10/13/18 22:50:57.319 Info: Dropping privileges to user homegear (114) and group homegear (122)
10/13/18 22:50:57.321 Info: Homegear is (now) running as user with id 114 and group with id 122.
10/13/18 22:50:57.350 Starting script engine server...
10/13/18 22:50:57.391 Initializing licensing controller...
10/13/18 22:50:57.391 Loading licensing controller data...
10/13/18 22:50:57.391 Loading devices...
10/13/18 22:50:57.391 Loading XML RPC devices...
10/13/18 22:50:59.308 Loading device 1
10/13/18 22:50:59.317 Module HomeMatic BidCoS: Info: Central address set to 0xFD0001.
10/13/18 22:50:59.324 Loading XML RPC devices...
10/13/18 22:50:59.456 Loading device 2
10/13/18 22:50:59.460 Loading XML RPC devices...
10/13/18 22:50:59.495 Loading device 6
10/13/18 22:50:59.500 Loading XML RPC devices...
10/13/18 22:50:59.688 Loading device 11
10/13/18 22:50:59.696 Info: Not initializing device family Philips hue, because it is disabled in it's configuration file.
10/13/18 22:50:59.697 Info: Disposing family module mod_philipshue.so
10/13/18 22:50:59.697 Loading XML RPC devices...
10/13/18 22:50:59.722 Loading device 10
10/13/18 22:50:59.726 Loading XML RPC devices...
10/13/18 22:50:59.729 Warning: Unknown parameter property: label
10/13/18 22:50:59.729 Warning: Unknown parameter property: label
10/13/18 22:50:59.731 Loading device 7
10/13/18 22:50:59.732 Loading XML RPC devices...
10/13/18 22:50:59.737 Loading device 4
10/13/18 22:50:59.738 Loading XML RPC devices...
10/13/18 22:50:59.745 Warning: Unknown parameter property: label
10/13/18 22:50:59.746 Warning: Unknown parameter property: label
10/13/18 22:50:59.748 Warning: Unknown parameter property: label
10/13/18 22:50:59.748 Warning: Unknown parameter property: label
10/13/18 22:50:59.751 Warning: Unknown parameter property: label
10/13/18 22:50:59.751 Warning: Unknown parameter property: label
10/13/18 22:50:59.773 Warning: Unknown parameter property: label
10/13/18 22:50:59.774 Warning: Unknown parameter property: label
10/13/18 22:50:59.777 Warning: Unknown parameter property: label
10/13/18 22:50:59.778 Warning: Unknown parameter property: label
10/13/18 22:50:59.781 Warning: Unknown parameter property: label
10/13/18 22:50:59.781 Warning: Unknown parameter property: label
10/13/18 22:50:59.784 Warning: Unknown parameter property: label
10/13/18 22:50:59.784 Warning: Unknown parameter property: label
10/13/18 22:50:59.787 Warning: Unknown parameter property: label
10/13/18 22:50:59.787 Warning: Unknown parameter property: label
10/13/18 22:50:59.789 Warning: Unknown parameter property: label
10/13/18 22:50:59.790 Warning: Unknown parameter property: label
10/13/18 22:50:59.794 Warning: Unknown parameter property: label
10/13/18 22:50:59.794 Warning: Unknown parameter property: label
10/13/18 22:50:59.795 Loading device 9
10/13/18 22:50:59.797 Loading XML RPC devices...
10/13/18 22:50:59.798 Loading device 12
10/13/18 22:50:59.805 Loading XML RPC devices...
10/13/18 22:51:00.021 Loading device 5
10/13/18 22:51:00.022 Loading XML RPC devices...
10/13/18 22:51:00.041 Loading device 8
10/13/18 22:51:00.042 Loading XML RPC devices...
10/13/18 22:51:00.052 Loading device 3
10/13/18 22:51:00.074 Initializing RPC client...
10/13/18 22:51:00.075 Starting XML RPC server RPCServer1 listening on :::2001...
10/13/18 22:51:00.081 RPC Server (Port 2001): Warning: SSL is not enabled for this RPC server. It is strongly recommended to disable all $
10/13/18 22:51:00.082 RPC Server (Port 2001): Warning: RPC server has no authorization enabled. Everybody on your local network can login$
10/13/18 22:51:00.082 RPC Server (Port 2001): Info: Enabling session authentication for WebSockets.
10/13/18 22:51:00.083 Starting XML RPC server RPCServer2 listening on :::2002, SSL enabled...
10/13/18 22:51:00.090 RPC Server (Port 2002): Warning: RPC server has no authorization enabled. Everybody on your local network can login$
10/13/18 22:51:00.090 RPC Server (Port 2002): Info: Enabling session authentication for WebSockets.
10/13/18 22:51:00.091 RPC Server (Port 2001): Info: RPC Server started listening on address :: and port 2001
10/13/18 22:51:00.199 Starting XML RPC server RPCServer3 listening on :::2003, SSL enabled, authentication enabled...
10/13/18 22:51:00.199 RPC Server (Port 2002): Info: RPC Server started listening on address :: and port 2002
10/13/18 22:51:00.206 RPC Server (Port 2003): Info: Enabling basic authentication.
10/13/18 22:51:00.206 RPC Server (Port 2003): Info: Enabling client certificate authentication.
10/13/18 22:51:00.268 Initializing event handler...
10/13/18 22:51:00.269 Loading events...
10/13/18 22:51:00.270 Start listening for packets...
10/13/18 22:51:05.077 Starting Node-BLUE server...
10/13/18 22:51:05.078 Module Sonos: Event server "My-Sonos-1234": Info: Started listening on address 192.168.66.28 and port 7373
10/13/18 22:51:05.171 Starting IPC server...
10/13/18 22:51:05.176 Startup complete. Waiting for physical interfaces to connect.
10/13/18 22:51:05.176 Info: Waiting for physical interfaces to connect (0 of 180s).
10/13/18 22:51:05.177 All physical interfaces are connected now.
10/13/18 22:51:05.177 Starting UPnP server...
10/13/18 22:51:05.178 Info: UPnP server: Binding to address: 192.168.66.28
10/13/18 22:51:05.179 UPnP Server: Info: Started listening.
10/13/18 22:52:28.094 IPC Server: Info: Connection accepted. Client number: 9
10/13/18 22:52:28.094 IPC Server: Info: Client 0 successfully registered RPC method "cliOutput" (this method is registered by 1 client(s)$
10/13/18 22:52:28.095 IPC Server: Info: Client 0 successfully registered RPC method "cliOutput-0" (this method is registered by 1 client($
10/13/18 22:53:58.226 IPC Server: Info: Client number 0 is calling RPC method: familyExists Parameters:
(Integer64) 4
10/13/18 22:54:54.445 IPC Server: Info: Connection to IPC server's client number 9 closed.
10/13/18 22:55:05.661 IPC Server: Info: IPC client 0 removed.

Grüße Welf

[wero]

sorry, irgendwie klappt das bei mir noch nicht so mit dem Kopieren in die Formatierungsfunktion

[pmayer]

10/13/18 22:51:05.177 All physical interfaces are connected now.

Das sieht gut aus…

In deinem Log sehe ich keine Pakete, da ist nur der Startvorgang drin.
Deinstallier mal bitte alle module die du nicht brauchst, das schafft erst mal mehr Überblick.

Was ist das für ein CUL?

[wero]

https://www.smart-home-komponente.de/nano-cul/nano-cul-868-extern/

[pmayer]

Hm, sollte von dem aus was ich sehe funktionieren. Wie sieht ein Pairing-Versuch im Log auf Loglevel 4 aus?

sudo homegear -r 
dl 4

[wero]

10/13/18 23:59:39.737 Starting Homegear...

10/13/18 23:59:39.737 Homegear version 0.7.30-1900
10/13/18 23:59:39.737 Git commit SHA of libhomegear-base: -
10/13/18 23:59:39.737 Git branch of libhomegear-base: -
10/13/18 23:59:39.737 Git commit SHA of Homegear: -
10/13/18 23:59:39.737 Git branch of Homegear: -
10/13/18 23:59:39.737 Info: Setting allowed core file size to “4294967295” for user with id 0 and group with id 0.
10/13/18 23:59:39.737 Info: Core file size now is “4294967295”.
10/13/18 23:59:39.737 Info: Setting maximum thread priority to “4294967295” for user with id 0 and group with id 0.
10/13/18 23:59:39.737 Info: Maximum thread priority now is “4294967295”.
10/13/18 23:59:39.744 Info: Backing up database…
10/13/18 23:59:39.803 Initializing database…
10/13/18 23:59:39.807 Info: Loading family module mod_homematicbidcos.so
10/13/18 23:59:39.818 /etc/homegear/families/homematicbidcos.conf
10/13/18 23:59:39.820 Info: Loading family module mod_miscellaneous.so
10/13/18 23:59:39.823 /etc/homegear/families/miscellaneous.conf
10/13/18 23:59:39.824 Info: Loading family module mod_homematicwired.so
10/13/18 23:59:39.829 /etc/homegear/families/homematicwired.conf
10/13/18 23:59:39.830 Info: Loading family module mod_philipshue.so
10/13/18 23:59:39.834 /etc/homegear/families/philipshue.conf
10/13/18 23:59:39.835 Info: Loading family module mod_max.so
10/13/18 23:59:39.842 /etc/homegear/families/max.conf
10/13/18 23:59:39.842 Info: Setting up physical interfaces and GPIOs…
10/13/18 23:59:39.843 Info: Dropping privileges to user homegear (114) and group homegear (122)
10/13/18 23:59:39.843 Info: Homegear is (now) running as user with id 114 and group with id 122.
10/13/18 23:59:39.849 Starting script engine server…
10/13/18 23:59:39.857 Initializing licensing controller…
10/13/18 23:59:39.857 Loading licensing controller data…
10/13/18 23:59:39.857 Loading devices…
10/13/18 23:59:39.857 Loading XML RPC devices…
10/13/18 23:59:40.633 Loading device 1
10/13/18 23:59:40.634 Module HomeMatic BidCoS: Info: Central address set to 0xFD0001.
10/13/18 23:59:40.635 Loading XML RPC devices…
10/13/18 23:59:40.678 Loading device 2
10/13/18 23:59:40.679 Loading XML RPC devices…
10/13/18 23:59:40.740 Loading device 11
10/13/18 23:59:40.741 Info: Not initializing device family Philips hue, because it is disabled in it’s configuration file.
10/13/18 23:59:40.741 Info: Disposing family module mod_philipshue.so
10/13/18 23:59:40.741 Loading XML RPC devices…
10/13/18 23:59:40.743 Loading device 3
10/13/18 23:59:40.743 Initializing RPC client…
10/13/18 23:59:40.743 Starting XML RPC server RPCServer3 listening on :::2003, SSL enabled, authentication enabled…
10/13/18 23:59:40.746 RPC Server (Port 2003): Info: Enabling basic authentication.
10/13/18 23:59:40.746 RPC Server (Port 2003): Info: Enabling client certificate authentication.
10/13/18 23:59:40.746 RPC Server (Port 2003): Info: Enabling session authentication for WebSockets.
10/13/18 23:59:40.777 Initializing event handler…
10/13/18 23:59:40.778 Loading events…
10/13/18 23:59:40.778 Start listening for packets…
10/13/18 23:59:45.583 Starting Node-BLUE server…
10/13/18 23:59:45.608 Starting IPC server…
10/13/18 23:59:45.615 Startup complete. Waiting for physical interfaces to connect.
10/13/18 23:59:45.616 Info: Waiting for physical interfaces to connect (0 of 180s).
10/13/18 23:59:45.616 All physical interfaces are connected now.
10/13/18 23:59:45.616 Starting UPnP server…
10/13/18 23:59:45.618 Warning: Not starting server, because no suitable RPC server for serving the XML description is avai$
10/14/18 00:00:00.557 IPC Server: Info: Connection accepted. Client number: 5
10/14/18 00:00:00.558 IPC Server: Info: Client 0 successfully registered RPC method “cliOutput” (this method is registered$
10/14/18 00:00:00.559 IPC Server: Info: Client 0 successfully registered RPC method “cliOutput-0” (this method is register$
10/14/18 00:00:05.654 IPC Server: Info: Connection to IPC server’s client number 5 closed.
10/14/18 00:00:45.811 IPC Server: Info: IPC client 0 removed.
10/14/18 00:03:03.358 IPC Server: Info: Connection accepted. Client number: 6
10/14/18 00:03:03.358 IPC Server: Info: Client 1 successfully registered RPC method “cliOutput” (this method is registered$
10/14/18 00:03:03.370 IPC Server: Info: Client 1 successfully registered RPC method “cliOutput-1” (this method is register$
10/14/18 00:03:25.666 IPC Server: Info: Client number 1 is calling RPC method: familyExists Parameters:
(Integer64) 4
10/14/18 00:03:33.735 MAX packet received (My-MAX-CUL, RSSI: 0x39): 09010800001004011372
10/14/18 00:03:39.216 Module MAX: Warning: Packet is shorter than value of packet length byte: Z70001A760000100F51133722348

10/14/18 00:03:39.216 MAX packet received (My-MAX-CUL): 0D001A760000100F511337223408
10/14/18 00:03:44.683 Module MAX: Warning: Packet is shorter than value of packet length byte: Z70F00107860000040F51137223$

10/14/18 00:03:44.683 MAX packet received (My-MAX-CUL): 0DF00107860000040F5113722347
10/14/18 00:03:50.163 HomeMatic BidCoS packet received (868, RSSI: -49 dBm): 09F40A76000004F45533
10/14/18 00:03:55.629 Module HomeMatic BidCoS: Warning: Packet is shorter than value of packet length byte: 10000108000004$

10/14/18 00:03:55.629 HomeMatic BidCoS packet received (868): 0C0001080000040F5113722345
10/14/18 00:04:01.110 HomeMatic BidCoS packet received (868, RSSI: -57 dBm): 09001080000100445333
10/14/18 00:04:19.439 IPC Server: Info: Connection to IPC server’s client number 6 closed.

[pmayer]

Text markieren und dann </> im Menü drücken… du kannst deinen Post nachträglich editieren.

Homegear kann mit dem CUL reden. Welches Gerät (Typennummer) versuchst du zu pairen?

[wero]

Danke für den Tipp mit der Textmarkierung und überhaupt Danke für die Unterstützung auch zu später Stunde!!

Der MAX-Fensterkontakt hat die Ziffer 1372234.

Ich habe nach o.g. Versuch die centralAdress mal geändert (war noch der Default-Wert) und nach Neustart Homegear nochmal das Pairing mit dem Fensterkontakt probiert. Jetzt kommt die Meldung, dass irgendein Device schon registriert wäre. Bislang waren aber alle Pairings erfolglos (Peers List war leer) - die Nummer des Fensterkontakt kann ich dort nicht erkennen - der Fensterkontakt ist auch fabrikneu von Amazon.
Das wird für mich immer seltsamer …
Und wiese startet auch das BidCos-Pairing, wenn ich doch nur MAX ausgewählt habe (fs 4)?

Hier das Log dazu:

10/14/18 00:21:29.290 IPC Server: Info: Connection accepted. Client number: 5
10/14/18 00:21:29.290 IPC Server: Info: Client 0 successfully registered RPC method "cliOutput" (this method is registered by 1 clie$
10/14/18 00:21:29.291 IPC Server: Info: Client 0 successfully registered RPC method "cliOutput-0" (this method is registered by 1 cl$
10/14/18 00:21:35.252 IPC Server: Info: Client number 0 is calling RPC method: familyExists Parameters:
(Integer64) 4
10/14/18 00:21:43.613 Module MAX: Warning: Packet is shorter than value of packet length byte: 171004001A0786000000001004004F4551313$

10/14/18 00:21:43.613 MAX packet received (My-MAX-CUL): 18004001A0786000000001004004F45513133373232333440B
10/14/18 00:21:49.094 HomeMatic BidCoS packet received (868, RSSI: -65 dBm): 09000001004004F45513
10/14/18 00:21:54.574 HomeMatic BidCoS packet received (868, RSSI: -32 dBm): 097100400A076000040F
10/14/18 00:22:00.039 HomeMatic BidCoS packet received (868, RSSI: -49 dBm): 09040A7600000100F513
10/14/18 00:22:05.521 HomeMatic BidCoS packet received (868, RSSI: -49 dBm): 097040A7600000404533
10/14/18 00:22:10.986 MAX packet received (My-MAX-CUL, RSSI: 0x48): 171004001A0786001800000100441133334C110010800004
10/14/18 00:22:10.987 Module MAX: Error: Pairing packet rejected, because this peer is already paired to another central.
10/14/18 00:22:27.102 IPC Server: Info: Connection to IPC server's client number 5 closed.
10/14/18 00:23:11.167 IPC Server: Info: IPC client 0 removed.

[wero]

habe eben auch das erste Pairing zu einem fabrikneuen MAX Thermostat Basic versucht:

10/14/18 11:42:22.680 IPC Server: Info: Connection accepted. Client number: 8
10/14/18 11:42:22.680 IPC Server: Info: Client 3 successfully registered RPC method "cliOutput" (this method is registered by 1 client(s)).
10/14/18 11:42:22.681 IPC Server: Info: Client 3 successfully registered RPC method "cliOutput-3" (this method is registered by 1 client(s)).
10/14/18 11:42:24.945 IPC Server: Info: Client number 3 is calling RPC method: familyExists Parameters:
(Integer64) 4
10/14/18 11:42:38.692 HomeMatic BidCoS packet received (868, RSSI: -23 dBm): 0900017D0000101F3334
10/14/18 11:42:57.789 MAX packet received (My-MAX-CUL, RSSI: 0x32): 090A6B00001A14455131
10/14/18 11:43:02.790 Module MAX: Warning: Packet is shorter than value of packet length byte: Z7004017D00010A4511040467E

10/14/18 11:43:02.790 MAX packet received (My-MAX-CUL): 0C04017D00010A45110404670E
10/14/18 11:43:07.777 MAX packet received (My-MAX-CUL, RSSI: 0x27): 091A7D000010A4411040
10/14/18 11:43:12.779 HomeMatic BidCoS packet received (868, RSSI: -49 dBm): 090040176B0000114453
10/14/18 11:43:17.780 HomeMatic BidCoS packet received (868, RSSI: -72 dBm): 0904017D0000010AF511
10/14/18 11:43:22.782 MAX packet received (My-MAX-CUL, RSSI: 0x4A): 090A000010A441033335
10/14/18 11:44:51.814 IPC Server: Info: Connection to IPC server's client number 8 closed.
10/14/18 11:45:00.930 IPC Server: Info: IPC client 3 removed.

[wero]

die Nummer des Thermostat ist 1040467

[wero]

und noch eine Info - ich hatte mir bei Amazon Warehousedeals Homematic Rollladenaktoren gekauft. Beim Pairen passiert dort rein gar nichts - auch wenn ich die Aktoren auf Werkseinstellungen zurücksetze:

10/14/18 11:22:14.611 IPC Server: Info: Connection accepted. Client number: 5
10/14/18 11:22:14.612 IPC Server: Info: Client 0 successfully registered RPC method "cliOutput" (this method is registered by 1 client(s)).
10/14/18 11:22:14.613 IPC Server: Info: Client 0 successfully registered RPC method "cliOutput-0" (this method is registered by 1 client(s)).
10/14/18 11:22:19.076 IPC Server: Info: Client number 0 is calling RPC method: familyExists Parameters:
(Integer64) 0
10/14/18 11:23:55.857 IPC Server: Info: Connection to IPC server's client number 5 closed.
10/14/18 11:23:59.263 IPC Server: Info: IPC client 0 removed.

[pmayer]

Wie viele CUL’s hast du?

[wero]

ich hatte jetzt weitgehend alle families gelöscht:

Please type >>help<< to list all available commands.
> ls
   ID │ Name                          
──────┼───────────────────────────────
    0 │ HomeMatic BidCoS              
    1 │ HomeMatic Wired               
    4 │ MAX!                          
  254 │ Miscellaneous                 
──────┴───────────────────────────────
> 

Ich habe jetzt den dritten bislang unbenutzten CUL ausprobiert (21:01) und bekomme u.a. Fehlermeldung “file desciptor not valid”:

10/14/18 21:01:08.825 IPC Server: Info: Connection accepted. Client number: 5
10/14/18 21:01:08.825 IPC Server: Info: Client 0 successfully registered RPC method "cliOutput" (this method is registered by 1 client(s)).
10/14/18 21:01:08.827 IPC Server: Info: Client 0 successfully registered RPC method "cliOutput-0" (this method is registered by 1 client(s)).
10/14/18 21:01:16.160 IPC Server: Info: Client number 0 is calling RPC method: familyExists Parameters:
(Integer64) 4
10/14/18 21:01:28.537 Module MAX: CUL "My-MAX-CUL": Warning: Too short packet received: 10

10/14/18 21:01:34.016 HomeMatic BidCoS packet received (868, RSSI: -74 dBm): 0971204001A078600000
10/14/18 21:01:44.974 MAX packet received (My-MAX-CUL, RSSI: 0x4A): 171204001A0786000000001004004F455131333703171204
10/14/18 21:01:45.013 Module MAX: CUL "My-MAX-CUL": Info: Sending (My-MAX-CUL, WOR: no): 0B000001FD6C0A1A07860000
10/14/18 21:01:45.101 HomeMatic BidCoS packet received (868, RSSI: -74 dBm): 0971204001A078600000
10/14/18 21:01:45.219 Module MAX: CUL "My-MAX-CUL": Info: Sending (My-MAX-CUL, WOR: no): 0B000001FD6C0A1A07860000
10/14/18 21:01:45.309 Module HomeMatic BidCoS: CUL "868": Error: Too small packet received. Assuming CUL error. I'm closing and reopening device: 00022A76DCA0122

10/14/18 21:01:45.310 Module HomeMatic BidCoS: CUL "868": Couldn't read from CUL device, because the file descriptor is not valid: /dev/ttyUSB1. Trying to reopen...
10/14/18 21:01:45.420 Module MAX: CUL "My-MAX-CUL": Info: Sending (My-MAX-CUL, WOR: no): 0B000001FD6C0A1A07860000
10/14/18 21:01:56.550 IPC Server: Info: Connection to IPC server's client number 5 closed.
10/14/18 21:02:43.820 IPC Server: Info: IPC client 0 removed.

Wenn ich den PI neu starte mit dem zweiten CUL, der bislang Signale empfangen hatte (siehe letztes, das ich Dir gesendet hast), dann bekomme ich die gleiche Fehlermeldung auch bei diesem CUL (21:08):

10/14/18 21:08:31.960 IPC Server: Info: Connection accepted. Client number: 5
10/14/18 21:08:31.960 IPC Server: Info: Client 0 successfully registered RPC method "cliOutput" (this method is registered by 1 client(s)).
10/14/18 21:08:31.961 IPC Server: Info: Client 0 successfully registered RPC method "cliOutput-0" (this method is registered by 1 client(s)).
10/14/18 21:08:35.018 IPC Server: Info: Client number 0 is calling RPC method: familyExists Parameters:
(Integer64) 4
10/14/18 21:08:42.091 HomeMatic BidCoS packet received (868, RSSI: -122 dBm): 0971304001A0786FD6C0
10/14/18 21:08:53.070 MAX packet received (My-MAX-CUL, RSSI: 0x48): 171304001A0786FD6C0A001004004F455131333732323040
10/14/18 21:08:53.110 Module MAX: CUL "My-MAX-CUL": Info: Sending (My-MAX-CUL, WOR: no): 0B010001FD6C0A1A07860000
10/14/18 21:08:53.198 HomeMatic BidCoS packet received (868, RSSI: -122 dBm): 0971304001A0786FD6C0
10/14/18 21:08:53.310 Module MAX: CUL "My-MAX-CUL": Info: Sending (My-MAX-CUL, WOR: no): 0B010001FD6C0A1A07860000
10/14/18 21:08:53.405 Module HomeMatic BidCoS: CUL "868": Error: Too small packet received. Assuming CUL error. I'm closing and reopening device: ZC122A76DCA0121

10/14/18 21:08:53.406 Module HomeMatic BidCoS: CUL "868": Couldn't read from CUL device, because the file descriptor is not valid: /dev/ttyUSB1. Trying to reopen...
10/14/18 21:08:53.511 Module MAX: CUL "My-MAX-CUL": Info: Sending (My-MAX-CUL, WOR: no): 0B010001FD6C0A1A07860000
10/14/18 21:09:13.633 IPC Server: Info: Connection to IPC server's client number 5 closed.
10/14/18 21:10:08.113 IPC Server: Info: IPC client 0 removed.

Es kann doch nicht sein, dass alle CUL defekt sind. Ich möchte ehrlich gesagt nicht meine openhab2 Installation für FHEM platt machen. Gibt es noch irgendeine andere Möglichkeit, das Problem einzugrenzen?

Grüße Welf

[pmayer]

Da muss @sathya was zu sagen… die Meldung so kenne ich nicht.

Hast du da ein aktuelles Stretch laufen? apt update & apt full-upgrade?
Eventuell kannst du auch mal den /dev/serial/by-id/... nehmen, statt /dev/ttyUSB1.

[wero]

Ich habe jetzt homegear komplett deinstalliert und neu installiert (weiterhin nur die families siehe oben).

Die Fehlermeldungen sind zwar im Prinzip weg - ein Pairing klappt aber weiterhin nicht.
Mich wundert, dass ich bei FS4 immer auch Paketmeldungen von BidCos bekomme - bei FS0 aber überhaupt keine BidCos Pakete empfangen werden.

1. Versuch MAX-Fensterkontakt (keine Fehlermeldung aber kein Pairing)
2. Versuch Homematic Rolladenaktor (kein Signal empfangen)
3. Versuch MAX-Fensterkontakt (keine Fehlermeldung aber kein Pairing)
4. Versuch MAX-Fensterkontakt (Paketlängenfehler und angeblich bereits gepaired)
5. Versuch Homematic Rolladenaktor (kein Signal empfangen)
6. Versuch Homematic Rolladenaktor (Versuch mit fs 4 - kein Signal empfangen)

Es war immer Fensterkontakt 1372234 und Rolladenaktor 1964083

Bin weiter ratlos!

10/17/18 21:05:21.314 Starting Homegear...
10/17/18 21:05:21.314 Homegear version 0.7.30-1900
10/17/18 21:05:21.314 Git commit SHA of libhomegear-base: -
10/17/18 21:05:21.314 Git branch of libhomegear-base:     -
10/17/18 21:05:21.314 Git commit SHA of Homegear:         -
10/17/18 21:05:21.314 Git branch of Homegear:             -
10/17/18 21:05:21.315 Info: Setting allowed core file size to "4294967295" for user with id 0 and group with id 0.
10/17/18 21:05:21.315 Info: Core file size now is "4294967295".
10/17/18 21:05:21.315 Info: Setting maximum thread priority to "4294967295" for user with id 0 and group with id 0.
10/17/18 21:05:21.315 Info: Maximum thread priority now is "4294967295".
10/17/18 21:05:21.325 Info: Backing up database...
10/17/18 21:05:21.383 Initializing database...
10/17/18 21:05:21.388 Info: Loading family module mod_homematicbidcos.so
10/17/18 21:05:21.399 /etc/homegear/families/homematicbidcos.conf
10/17/18 21:05:21.407 Info: Loading family module mod_miscellaneous.so
10/17/18 21:05:21.412 /etc/homegear/families/miscellaneous.conf
10/17/18 21:05:21.413 Info: Loading family module mod_homematicwired.so
10/17/18 21:05:21.420 /etc/homegear/families/homematicwired.conf
10/17/18 21:05:21.421 Info: Loading family module mod_max.so
10/17/18 21:05:21.427 /etc/homegear/families/max.conf
10/17/18 21:05:21.428 Info: Setting up physical interfaces and GPIOs...
10/17/18 21:05:21.428 Info: Dropping privileges to user homegear (114) and group homegear (122)
10/17/18 21:05:21.429 Info: Homegear is (now) running as user with id 114 and group with id 122.
10/17/18 21:05:21.436 Starting script engine server...
10/17/18 21:05:21.444 Initializing licensing controller...
10/17/18 21:05:21.444 Loading licensing controller data...
10/17/18 21:05:21.444 Loading devices...
10/17/18 21:05:21.444 Loading XML RPC devices...
10/17/18 21:05:22.312 Loading device 1
10/17/18 21:05:22.321 Module HomeMatic BidCoS: Info: Central address set to 0xFD1812.
10/17/18 21:05:22.326 Loading XML RPC devices...
10/17/18 21:05:22.379 Loading device 2
10/17/18 21:05:22.380 Loading XML RPC devices...
10/17/18 21:05:22.449 Loading device 4
10/17/18 21:05:22.450 Loading XML RPC devices...
10/17/18 21:05:22.452 Loading device 3
10/17/18 21:05:22.452 Initializing RPC client...
10/17/18 21:05:22.452 Starting XML RPC server RPCServer1 listening on :::2001...
10/17/18 21:05:22.456 RPC Server (Port 2001): Warning: SSL is not enabled for this RPC server. It is strongly recommended to disable all unencrypted RPC s$
10/17/18 21:05:22.456 RPC Server (Port 2001): Warning: RPC server has no authorization enabled. Everybody on your local network can login into this instal$
10/17/18 21:05:22.456 RPC Server (Port 2001): Info: Enabling session authentication for WebSockets.10/17/18 21:05:22.457 Starting XML RPC server RPCServer2 listening on :::2002, SSL enabled...
10/17/18 21:05:22.457 RPC Server (Port 2001): Info: RPC Server started listening on address :: and port 2001
10/17/18 21:05:22.461 RPC Server (Port 2002): Warning: RPC server has no authorization enabled. Everybody on your local network can login into this instal$
10/17/18 21:05:22.461 RPC Server (Port 2002): Info: Enabling session authentication for WebSockets.
10/17/18 21:05:22.496 Starting XML RPC server RPCServer3 listening on :::2003, SSL enabled, authentication enabled...
10/17/18 21:05:22.496 RPC Server (Port 2002): Info: RPC Server started listening on address :: and port 2002
10/17/18 21:05:22.499 RPC Server (Port 2003): Info: Enabling basic authentication.
10/17/18 21:05:22.499 RPC Server (Port 2003): Info: Enabling client certificate authentication.
10/17/18 21:05:22.499 RPC Server (Port 2003): Info: Enabling session authentication for WebSockets.
10/17/18 21:05:22.529 Initializing event handler...
10/17/18 21:05:22.529 Loading events...
10/17/18 21:05:22.530 Start listening for packets...
10/17/18 21:05:27.335 Starting Node-BLUE server...
10/17/18 21:05:27.347 Starting IPC server...
10/17/18 21:05:27.357 Startup complete. Waiting for physical interfaces to connect.
10/17/18 21:05:27.357 Info: Waiting for physical interfaces to connect (0 of 180s).
10/17/18 21:05:27.357 All physical interfaces are connected now.
10/17/18 21:05:27.357 Starting UPnP server...
10/17/18 21:05:27.362 Info: UPnP server: Binding to address: 192.168.66.28
10/17/18 21:05:27.362 UPnP Server: Info: Started listening.
10/17/18 21:07:08.574 IPC Server: Info: Connection accepted. Client number: 8
10/17/18 21:07:08.574 IPC Server: Info: Client 0 successfully registered RPC method "cliOutput" (this method is registered by 1 client(s)).
10/17/18 21:07:08.575 IPC Server: Info: Client 0 successfully registered RPC method "cliOutput-0" (this method is registered by 1 client(s)).
10/17/18 21:07:16.837 IPC Server: Info: Client number 0 is calling RPC method: familyExists Parameters:
(Integer64) 4
10/17/18 21:07:27.417 HomeMatic BidCoS packet received (868, RSSI: -17 dBm): 09540A76DCA0040F5113
10/17/18 21:07:32.899 MAX packet received (My-MAX-CUL, RSSI: 0x65): 100108F6001004453333333300100176D6
10/17/18 21:07:38.379 HomeMatic BidCoS packet received (868, RSSI: -49 dBm): 17540A08F001004453333333007540A76D6001004F513133
10/17/18 21:07:43.876 HomeMatic BidCoS packet received (868, RSSI: -49 dBm): 09540A76D6CA00404533
10/17/18 21:07:49.358 HomeMatic BidCoS packet received (868, RSSI: -122 dBm): 0971504001A0786FD6C0
10/17/18 21:07:54.839 MAX packet received (My-MAX-CUL, RSSI: 0x48): 100108FCA00404537223031100108F0010
10/17/18 21:08:09.800 IPC Server: Info: Connection to IPC server's client number 8 closed.10/17/18 21:08:27.626 IPC Server: Info: IPC client 0 removed.
10/17/18 21:12:12.525 IPC Server: Info: Connection accepted. Client number: 9
10/17/18 21:12:12.526 IPC Server: Info: Client 1 successfully registered RPC method "cliOutput" (this method is registered by 1 client(s)).
10/17/18 21:12:12.526 IPC Server: Info: Client 1 successfully registered RPC method "cliOutput-1" (this method is registered by 1 client(s)).
10/17/18 21:12:17.007 IPC Server: Info: Client number 1 is calling RPC method: familyExists Parameters:
(Integer64) 0
10/17/18 21:13:01.276 IPC Server: Info: Connection to IPC server's client number 9 closed.
10/17/18 21:13:27.917 IPC Server: Info: IPC client 1 removed.
10/17/18 21:15:29.739 IPC Server: Info: Connection accepted. Client number: 10
10/17/18 21:15:29.740 IPC Server: Info: Client 2 successfully registered RPC method "cliOutput" (this method is registered by 1 client(s)).
10/17/18 21:15:29.740 IPC Server: Info: Client 2 successfully registered RPC method "cliOutput-2" (this method is registered by 1 client(s)).
10/17/18 21:15:32.493 IPC Server: Info: Client number 2 is calling RPC method: familyExists Parameters:
(Integer64) 4
10/17/18 21:15:40.300 HomeMatic BidCoS packet received (868, RSSI: -49 dBm): 097150401A6DCA004F55
10/17/18 21:15:45.783 MAX packet received (My-MAX-CUL): 1600108F60040533333331100108F601004F5113722400
10/17/18 21:15:51.265 HomeMatic BidCoS packet received (868, RSSI: -49 dBm): 09640A76DC0A00404533
10/17/18 21:15:56.730 HomeMatic BidCoS packet received (868, RSSI: -65 dBm): 091001086F600100F551
10/17/18 21:16:02.195 MAX packet received (My-MAX-CUL, RSSI: 0x48): 1040108F600100411372234F7640A7DCA0
10/17/18 21:16:07.661 HomeMatic BidCoS packet received (868, RSSI: -49 dBm): 09640A76DCA000404511
10/17/18 21:16:22.575 IPC Server: Info: Connection to IPC server's client number 10 closed.
10/17/18 21:16:28.085 IPC Server: Info: IPC client 2 removed.
10/17/18 21:18:15.060 IPC Server: Info: Connection accepted. Client number: 11
10/17/18 21:18:15.060 IPC Server: Info: Client 3 successfully registered RPC method "cliOutput" (this method is registered by 1 client(s)).
10/17/18 21:18:15.061 IPC Server: Info: Client 3 successfully registered RPC method "cliOutput-3" (this method is registered by 1 client(s)).
10/17/18 21:18:19.263 IPC Server: Info: Client number 3 is calling RPC method: familyExists Parameters:
(Integer64) 4
10/17/18 21:18:26.755 HomeMatic BidCoS packet received (868, RSSI: -57 dBm): 09004004F45513133373
10/17/18 21:18:32.238 Module MAX: Warning: Packet is shorter than value of packet length byte: Z7640A76F6001004313733332^MB663176DC015^MZ171704001A0786FD6$

10/17/18 21:18:32.238 MAX packet received (My-MAX-CUL): 1F40A76F60010043137333320B663176DC01050071704001A0786FD6C0A04309
10/17/18 21:18:37.705 HomeMatic BidCoS packet received (868, RSSI: -122 dBm): 0971704001A0786FD6C0
10/17/18 21:18:43.170 HomeMatic BidCoS packet received (868, RSSI: -122 dBm): 0971704001A0786FD6C010/17/18 21:18:48.651 HomeMatic BidCoS packet received (868, RSSI: -72 dBm): 09001A0786FD6C0A0010
10/17/18 21:18:54.133 MAX packet received (My-MAX-CUL, RSSI: 0x2F): 171704001A07860FD6C01717FD6C0A001004004F45513133
10/17/18 21:18:54.134 Module MAX: Error: Pairing packet rejected, because this peer is already paired to another central.
10/17/18 21:19:03.375 IPC Server: Info: Connection to IPC server's client number 11 closed.
10/17/18 21:19:28.316 IPC Server: Info: IPC client 3 removed.
10/17/18 21:23:04.435 IPC Server: Info: Connection accepted. Client number: 12
10/17/18 21:23:04.437 IPC Server: Info: Client 4 successfully registered RPC method "cliOutput" (this method is registered by 1 client(s)).
10/17/18 21:23:04.438 IPC Server: Info: Client 4 successfully registered RPC method "cliOutput-4" (this method is registered by 1 client(s)).
10/17/18 21:23:15.996 IPC Server: Info: Client number 4 is calling RPC method: familyExists Parameters:
(Integer64) 0
10/17/18 21:23:55.231 IPC Server: Info: Connection to IPC server's client number 12 closed.
10/17/18 21:24:28.586 IPC Server: Info: IPC client 4 removed.
10/17/18 21:24:47.301 IPC Server: Info: Connection accepted. Client number: 13
10/17/18 21:24:47.302 IPC Server: Info: Client 5 successfully registered RPC method "cliOutput" (this method is registered by 1 client(s)).
10/17/18 21:24:47.303 IPC Server: Info: Client 5 successfully registered RPC method "cliOutput-5" (this method is registered by 1 client(s)).
10/17/18 21:24:50.594 IPC Server: Info: Client number 5 is calling RPC method: familyExists Parameters:
(Integer64) 4
10/17/18 21:25:30.817 IPC Server: Info: Connection to IPC server's client number 13 closed.