CUL Homegear kein pairing möglich

Deutsche Foren Installation
#1

Moin,

ich habe homegear auf einem RPI3 installiert und bin nach den Anweisungen aus, dem doc https://doc.homegear.eu/data/homegear-homematicbidcos/configuration.html vorgegangen. Ich habe den Busware CUL V3. Firmware 1.66. Raspbian Jessie

Ich habe die config.txt und die anderen Änderungen die auf allen RPI notwendig sind durchgeführt. Ich habe schon viele Beiträge zu ähnlichen Problemen gesehen, aber mein Problem nicht in Griff bekommen.

Zuerst bin ich auch in die Falle getreten und hatte homegear in der Debian Version installiert. Dann deinstalliert und neue Pakete für Raspian Jessie installiert.

Unter dem User pi gibt homegear -r folgendes aus:

 homegear -r

04/27/17 10:48:17.265 Could not connect to socket. Error: Permission denied
04/27/17 10:48:17.265 Could not connect to socket. Error: Permission denied

Als root:
root@raspismarthome:~# homegear -r
Connected to Homegear (version 0.6.20-987).

sudo screen /dev/ttyACM0 9600
V Enter
gibt folgendes aus:
“V 1.66 CUL868”

Ar Enter und pairing mode beim Fensterkontakt gibt oder auch beim Bewegungsmelder
0F298610440E840000000AA8F50E0000EB

Wenn ich jetzt allerdings
als Root:

sudo homegear -r

families select 0

pairing on

Die Garäte in paringmodus vesetze…

peers list aufrufe… kommt:
(Family)> peers list
No peers are paired to this central.

Nun komme ich nicht weiter. Hat jem. eine Idee, wie ich es eingrenzen kann. Die Geräte sind neu. Ich habe trotzdem auch nen Werksreset schon probiert.

Ich würde mich über Hilfe zum Eingrenzen sehr freuen.

LG

Lars

PS wie bette ich die Codes richtig in den Beitrag, finde das nicht!

#2

Was zeigen denn die Fensterkontakte beim pairen an? Hast Du noch weiter Geräte wo dass ggf. funktioniert oder du probieren kannst?

Thomas

#3

Schalte mal in der homegear Konsole auf dl 5 und schaue dir auf einem zweiten Fenster dann mal tail -f /var/log/homegear/homegear.log an, während du pon gemacht hast und pairen willst.

Dann sieht man vielleicht was, wie @dibbler42 schon sagt :thumbsup:

#4

Moin, vielen Dank für Eure Antworten.

der Fensterkontakt blinkt einfach rot, bis die 20 sec. Paringmode rum sind. Der Bewegungsmelder genauso.

Ich habe mal den Vorschlag von pmayer gemacht und habe im 2ten Fenster folgende Ausgabe nach mehreren Versuchen:

root@raspismarthome:~# tail -f /var/log/homegear/homegear.log
04/27/17 18:09:16.417 Debug (My-CUL): Packet processing of packet 0F058610440E5B                        0000000A60D40E0000 took 0 ms.
04/27/17 18:09:23.051 UPnP Server: Debug: Sending notify packets.
04/27/17 18:09:24.423 Debug: SSDP server: Binding to address: 192.168.0.104
04/27/17 18:09:24.424 Debug: Searching for SSDP devices ...
04/27/17 18:09:36.092 Debug (My-CUL): Packet 0FD48610440E840000000AA8E30E0000 en                        ters raisePacketReceived.
04/27/17 18:09:36.092 Debug (My-CUL): Packet 0FD48610440E840000000AA8E30E0000 is                         now passed to the EventHandler.
04/27/17 18:09:36.092 HomeMatic BidCoS packet received (My-CUL, RSSI: -86 dBm):                         0FD48610440E840000000AA8E30E0000
04/27/17 18:09:36.093 Debug (My-CUL): Packet processing of packet 0FD48610440E84                        0000000AA8E30E0000 took 1 ms.
04/27/17 18:09:50.140 Debug: SSDP server: Binding to address: 192.168.0.104
04/27/17 18:09:50.140 Debug: Searching for SSDP devices ...
04/27/17 18:10:15.857 Debug: SSDP server: Binding to address: 192.168.0.104
04/27/17 18:10:15.857 Debug: Searching for SSDP devices ...
04/27/17 18:10:16.470 Connection to client number 1673 closed.
04/27/17 18:10:23.032 UPnP Server: Debug: Sending notify packets.
04/27/17 18:10:24.206 Debug: Joining read thread of CLI client 5
04/27/17 18:10:24.206 Debug: CLI client 5 removed.
04/27/17 18:10:41.574 Debug: SSDP server: Binding to address: 192.168.0.104
04/27/17 18:10:41.574 Debug: Searching for SSDP devices ...
04/27/17 18:10:42.095 Info: CLI connection accepted. Client number: 1683
04/27/17 18:10:42.095 Listening for incoming commands from client number 1683.
04/27/17 18:10:53.711 Connection to client number 1683 closed.
04/27/17 18:11:07.291 Debug: SSDP server: Binding to address: 192.168.0.104
04/27/17 18:11:07.291 Debug: Searching for SSDP devices ...
04/27/17 18:11:07.401 Info: CLI connection accepted. Client number: 1685
04/27/17 18:11:07.401 Listening for incoming commands from client number 1685.
04/27/17 18:11:11.808 Debug (My-CUL): Packet 0FD18610440E7E0000000AA8E50E0000 enters raisePacket        Received.
04/27/17 18:11:11.808 Debug (My-CUL): Packet 0FD18610440E7E0000000AA8E50E0000 is now passed to t        he EventHandler.
04/27/17 18:11:11.807 HomeMatic BidCoS packet received (My-CUL, RSSI: -95 dBm): 0FD18610440E7E00        00000AA8E50E0000
04/27/17 18:11:11.808 Debug (My-CUL): Packet processing of packet 0FD18610440E7E0000000AA8E50E00        00 took 0 ms.
04/27/17 18:11:23.011 UPnP Server: Debug: Sending notify packets.
04/27/17 18:11:24.420 Debug: Joining read thread of CLI client 6
04/27/17 18:11:24.420 Debug: CLI client 6 removed.
04/27/17 18:11:33.006 Debug: SSDP server: Binding to address: 192.168.0.104
04/27/17 18:11:33.006 Debug: Searching for SSDP devices ...
04/27/17 18:11:58.722 Debug: SSDP server: Binding to address: 192.168.0.104
04/27/17 18:11:58.722 Debug: Searching for SSDP devices ...
04/27/17 18:12:15.843 Debug (My-CUL): Packet 0FD58610440E840000000AA8E30E0000 enters raisePacket        Received.
04/27/17 18:12:15.843 Debug (My-CUL): Packet 0FD58610440E840000000AA8E30E0000 is now passed to t        he EventHandler.
04/27/17 18:12:15.843 HomeMatic BidCoS packet received (My-CUL, RSSI: -84 dBm): 0FD58610440E8400        00000AA8E30E0000
04/27/17 18:12:15.844 Debug (My-CUL): Packet processing of packet 0FD58610440E840000000AA8E30E00        00 took 1 ms.
04/27/17 18:12:23.091 UPnP Server: Debug: Sending notify packets.
04/27/17 18:12:24.439 Debug: SSDP server: Binding to address: 192.168.0.104
04/27/17 18:12:24.439 Debug: Searching for SSDP devices ...
04/27/17 18:12:50.156 Debug: SSDP server: Binding to address: 192.168.0.104
04/27/17 18:12:50.157 Debug: Searching for SSDP devices ...
04/27/17 18:13:15.874 Debug: SSDP server: Binding to address: 192.168.0.104
04/27/17 18:13:15.874 Debug: Searching for SSDP devices ...
04/27/17 18:13:23.072 UPnP Server: Debug: Sending notify packets.
04/27/17 18:13:41.591 Debug: SSDP server: Binding to address: 192.168.0.104
04/27/17 18:13:41.591 Debug: Searching for SSDP devices ...
04/27/17 18:14:07.305 Debug: SSDP server: Binding to address: 192.168.0.104
04/27/17 18:14:07.305 Debug: Searching for SSDP devices ...
04/27/17 18:14:23.052 UPnP Server: Debug: Sending notify packets.
04/27/17 18:14:33.022 Debug: SSDP server: Binding to address: 192.168.0.104
04/27/17 18:14:33.022 Debug: Searching for SSDP devices ...
04/27/17 18:14:41.095 Debug (My-CUL): Packet 0FD68610440E840000000AA8E30E0000 enters raisePacketReceived
04/27/17 18:14:41.096 Debug (My-CUL): Packet 0FD68610440E840000000AA8E30E0000 is now passed to the Event
04/27/17 18:14:41.095 HomeMatic BidCoS packet received (My-CUL, RSSI: -84 dBm): 0FD68610440E840000000AA8
04/27/17 18:14:41.096 Debug (My-CUL): Packet processing of packet 0FD68610440E840000000AA8E30E0000 took
04/27/17 18:14:58.739 Debug: SSDP server: Binding to address: 192.168.0.104
04/27/17 18:14:58.739 Debug: Searching for SSDP devices ...
04/27/17 18:15:23.032 UPnP Server: Debug: Sending notify packets.
04/27/17 18:15:24.456 Debug: SSDP server: Binding to address: 192.168.0.104
04/27/17 18:15:24.456 Debug: Searching for SSDP devices ...
04/27/17 18:15:50.173 Debug: SSDP server: Binding to address: 192.168.0.104
04/27/17 18:15:50.174 Debug: Searching for SSDP devices ...
04/27/17 18:15:56.059 Debug (My-CUL): Packet 0FD38610440E7E0000000AA8E50E0000 enters raisePacketReceived
04/27/17 18:15:56.060 Debug (My-CUL): Packet 0FD38610440E7E0000000AA8E50E0000 is now passed to the Event
04/27/17 18:15:56.059 HomeMatic BidCoS packet received (My-CUL, RSSI: -96 dBm): 0FD38610440E7E0000000AA8
04/27/17 18:15:56.060 Debug (My-CUL): Packet processing of packet 0FD38610440E7E0000000AA8E50E0000 took
04/27/17 18:16:15.890 Debug: SSDP server: Binding to address: 192.168.0.104
04/27/17 18:16:15.891 Debug: Searching for SSDP devices ...
04/27/17 18:16:23.011 UPnP Server: Debug: Sending notify packets.
04/27/17 18:16:41.611 Debug: SSDP server: Binding to address: 192.168.0.104
04/27/17 18:16:41.611 Debug: Searching for SSDP devices ...
root@raspismarthome:~# tail -f /var/log/homegear/homegear.log
04/27/17 18:09:16.417 Debug (My-CUL): Packet processing of packet 0F058610440E5B                        0000000A60D40E0000 took 0 ms.
04/27/17 18:09:23.051 UPnP Server: Debug: Sending notify packets.
04/27/17 18:09:24.423 Debug: SSDP server: Binding to address: 192.168.0.104
04/27/17 18:09:24.424 Debug: Searching for SSDP devices ...
04/27/17 18:09:36.092 Debug (My-CUL): Packet 0FD48610440E840000000AA8E30E0000 en                        ters raisePacketReceived.
04/27/17 18:09:36.092 Debug (My-CUL): Packet 0FD48610440E840000000AA8E30E0000 is                         now passed to the EventHandler.
04/27/17 18:09:36.092 HomeMatic BidCoS packet received (My-CUL, RSSI: -86 dBm):                         0FD48610440E840000000AA8E30E0000
04/27/17 18:09:36.093 Debug (My-CUL): Packet processing of packet 0FD48610440E84                        0000000AA8E30E0000 took 1 ms.
04/27/17 18:09:50.140 Debug: SSDP server: Binding to address: 192.168.0.104
04/27/17 18:09:50.140 Debug: Searching for SSDP devices ...
04/27/17 18:10:15.857 Debug: SSDP server: Binding to address: 192.168.0.104
04/27/17 18:10:15.857 Debug: Searching for SSDP devices ...
04/27/17 18:10:16.470 Connection to client number 1673 closed.
04/27/17 18:10:23.032 UPnP Server: Debug: Sending notify packets.
04/27/17 18:10:24.206 Debug: Joining read thread of CLI client 5
04/27/17 18:10:24.206 Debug: CLI client 5 removed.
04/27/17 18:10:41.574 Debug: SSDP server: Binding to address: 192.168.0.104
04/27/17 18:10:41.574 Debug: Searching for SSDP devices ...
04/27/17 18:10:42.095 Info: CLI connection accepted. Client number: 1683
04/27/17 18:10:42.095 Listening for incoming commands from client number 1683.
04/27/17 18:10:53.711 Connection to client number 1683 closed.
04/27/17 18:11:07.291 Debug: SSDP server: Binding to address: 192.168.0.104
04/27/17 18:11:07.291 Debug: Searching for SSDP devices ...
04/27/17 18:11:07.401 Info: CLI connection accepted. Client number: 1685
04/27/17 18:11:07.401 Listening for incoming commands from client number 1685.
04/27/17 18:11:11.808 Debug (My-CUL): Packet 0FD18610440E7E0000000AA8E50E0000 enters raisePacket        Received.
04/27/17 18:11:11.808 Debug (My-CUL): Packet 0FD18610440E7E0000000AA8E50E0000 is now passed to t        he EventHandler.
04/27/17 18:11:11.807 HomeMatic BidCoS packet received (My-CUL, RSSI: -95 dBm): 0FD18610440E7E00        00000AA8E50E0000
04/27/17 18:11:11.808 Debug (My-CUL): Packet processing of packet 0FD18610440E7E0000000AA8E50E00        00 took 0 ms.
04/27/17 18:11:23.011 UPnP Server: Debug: Sending notify packets.
04/27/17 18:11:24.420 Debug: Joining read thread of CLI client 6
04/27/17 18:11:24.420 Debug: CLI client 6 removed.
04/27/17 18:11:33.006 Debug: SSDP server: Binding to address: 192.168.0.104
04/27/17 18:11:33.006 Debug: Searching for SSDP devices ...
04/27/17 18:11:58.722 Debug: SSDP server: Binding to address: 192.168.0.104
04/27/17 18:11:58.722 Debug: Searching for SSDP devices ...
04/27/17 18:12:15.843 Debug (My-CUL): Packet 0FD58610440E840000000AA8E30E0000 enters raisePacket        eived.
04/27/17 18:16:51.846 Debug (My-CUL): Packet 0FD78610440E840000000AA8E30E0000 is now passed to the Event
04/27/17 18:16:51.846 HomeMatic BidCoS packet received (My-CUL, RSSI: -84 dBm): 0FD78610440E840000000AA8
04/27/17 18:16:51.847 Debug (My-CUL): Packet processing of packet 0FD78610440E840000000AA8E30E0000 took
04/27/17 18:17:07.325 Debug: SSDP server: Binding to address: 192.168.0.104
04/27/17 18:17:07.325 Debug: Searching for SSDP devices ...
04/27/17 18:17:23.093 UPnP Server: Debug: Sending notify packets.
04/27/17 18:17:33.042 Debug: SSDP server: Binding to address: 192.168.0.104
04/27/17 18:17:33.042 Debug: Searching for SSDP devices ...
04/27/17 18:17:56.559 Debug (My-CUL): Packet 0FD48610440E7E0000000AA8E50E0000 enters raisePacketReceived
04/27/17 18:17:56.560 Debug (My-CUL): Packet 0FD48610440E7E0000000AA8E50E0000 is now passed to the Event
04/27/17 18:17:56.559 HomeMatic BidCoS packet received (My-CUL, RSSI: -95 dBm): 0FD48610440E7E0000000AA8
04/27/17 18:17:56.560 Debug (My-CUL): Packet processing of packet 0FD48610440E7E0000000AA8E50E0000 took
04/27/17 18:17:58.759 Debug: SSDP server: Binding to address: 192.168.0.104
04/27/17 18:17:58.759 Debug: Searching for SSDP devices ...
04/27/17 18:18:23.072 UPnP Server: Debug: Sending notify packets.
04/27/17 18:18:24.475 Debug: SSDP server: Binding to address: 192.168.0.104
04/27/17 18:18:24.476 Debug: Searching for SSDP devices ...
04/27/17 18:18:50.191 Debug: SSDP server: Binding to address: 192.168.0.104
04/27/17 18:18:50.191 Debug: Searching for SSDP devices ...
04/27/17 18:19:15.907 Debug: SSDP server: Binding to address: 192.168.0.104
04/27/17 18:19:15.907 Debug: Searching for SSDP devices ...
04/27/17 18:19:23.051 UPnP Server: Debug: Sending notify packets.
04/27/17 18:19:41.630 Debug: SSDP server: Binding to address: 192.168.0.104
04/27/17 18:19:41.630 Debug: Searching for SSDP devices ...
04/27/17 18:19:52.349 Debug (My-CUL): Packet 0FD88610440E840000000AA8E20E0000 enters raisePacketReceived
04/27/17 18:19:52.349 Debug (My-CUL): Packet 0FD88610440E840000000AA8E20E0000 is now passed to the Event
04/27/17 18:19:52.349 HomeMatic BidCoS packet received (My-CUL, RSSI: -84 dBm): 0FD88610440E840000000AA8
04/27/17 18:19:52.349 Debug (My-CUL): Packet processing of packet 0FD88610440E840000000AA8E20E0000 took
04/27/17 18:20:07.342 Debug: SSDP server: Binding to address: 192.168.0.104
04/27/17 18:20:07.342 Debug: Searching for SSDP devices ...
04/27/17 18:20:23.038 UPnP Server: Debug: Sending notify packets.
04/27/17 18:20:33.056 Debug: SSDP server: Binding to address: 192.168.0.104
04/27/17 18:20:33.056 Debug: Searching for SSDP devices ...
04/27/17 18:20:58.768 Debug: SSDP server: Binding to address: 192.168.0.104
04/27/17 18:20:58.768 Debug: Searching for SSDP devices ...
04/27/17 18:21:08.239 Connection to client number 1685 closed.
04/27/17 18:21:13.792 Info: CLI connection accepted. Client number: 1709
04/27/17 18:21:13.792 Listening for incoming commands from client number 1709.
04/27/17 18:21:23.018 UPnP Server: Debug: Sending notify packets.
04/27/17 18:21:24.485 Debug: SSDP server: Binding to address: 192.168.0.104
04/27/17 18:21:24.485 Debug: Searching for SSDP devices ...
04/27/17 18:21:25.804 Debug: Joining read thread of CLI client 7
04/27/17 18:21:25.804 Debug: CLI client 7 removed.
04/27/17 18:21:50.202 Debug: SSDP server: Binding to address: 192.168.0.104
04/27/17 18:21:50.202 Debug: Searching for SSDP devices ...
04/27/17 18:22:15.919 Debug: SSDP server: Binding to address: 192.168.0.104
04/27/17 18:22:15.920 Debug: Searching for SSDP devices ...
04/27/17 18:22:23.000 UPnP Server: Debug: Sending notify packets.
04/27/17 18:22:38.351 Debug (My-CUL): Packet 0FD98610440E840000000AA8E20E0000 enters raisePacketReceived.
04/27/17 18:22:38.351 Debug (My-CUL): Packet 0FD98610440E840000000AA8E20E0000 is now passed to the EventHandler.
04/27/17 18:22:38.350 HomeMatic BidCoS packet received (My-CUL, RSSI: -85 dBm): 0FD98610440E840000000AA8E20E0000
04/27/17 18:22:38.351 Debug (My-CUL): Packet processing of packet 0FD98610440E840000000AA8E20E0000 took 0 ms.
04/27/17 18:22:41.637 Debug: SSDP server: Binding to address: 192.168.0.104
04/27/17 18:22:41.638 Debug: Searching for SSDP devices ...
04/27/17 18:23:07.350 Debug: SSDP server: Binding to address: 192.168.0.104
04/27/17 18:23:07.350 Debug: Searching for SSDP devices ...
04/27/17 18:23:23.080 UPnP Server: Debug: Sending notify packets.
04/27/17 18:23:33.063 Debug: SSDP server: Binding to address: 192.168.0.104
04/27/17 18:23:33.064 Debug: Searching for SSDP devices ...
04/27/17 18:23:58.780 Debug: SSDP server: Binding to address: 192.168.0.104
04/27/17 18:23:58.780 Debug: Searching for SSDP devices ...
04/27/17 18:24:23.059 UPnP Server: Debug: Sending notify packets.
04/27/17 18:24:24.497 Debug: SSDP server: Binding to address: 192.168.0.104
04/27/17 18:24:24.498 Debug: Searching for SSDP devices

Eine Idee dazu?

#5

Hmm… wie weit ist denn die Entfernung von CUL zu Fensterkontakt?

#6

Hallo zusammen,
ich habe genau das gleiche Problem und kann es nicht weiter einkreisen. Gibt es mittlerweile einen Lösungsansatz ? Wenn ich FHEM einsetze funktioniert das Pairing ohne Probleme.
Im Gegensatz zur Dokumentation gibt es bei mir in der Homegearkonsole den Befehl ‘devices …’ nicht.

Bin für jeden Hinweis dankbar.

#7

Hallo @leihen,

tut mir leid für die sehr späte Antwort. Falls das Problem noch aktuell ist, poste das Log vom Anlernvorgang. Das sollte uns zeigen, was lost ist. Die Ebene devices gibt es tatsächlich nicht mehr. Auf doc.homegear.eu ist sie auch nicht mehr aufgeführt.

Viele Grüße

Sathya

#8

Hello,

I am having the same problem as mentioned here. Log looks like this-

11/16/17 12:49:50.027 UPnP Server: Debug: Sending notify packets.
11/16/17 12:49:54.688 Debug (My-CUL): Packet 0F2E861053524B0000000A88E88F0000 enters raisePacketReceived.
11/16/17 12:49:54.688 Debug (My-CUL): Packet 0F2E861053524B0000000A88E88F0000 is now passed to the EventHandler.
11/16/17 12:49:54.688 HomeMatic BidCoS packet received (My-CUL, RSSI: -17 dBm): 0F2E861053524B0000000A88E88F0000
11/16/17 12:49:54.689 Debug (My-CUL): Packet processing of packet 0F2E861053524B0000000A88E88F0000 took 1 ms.
11/16/17 12:50:44.383 Debug (My-CUL): Packet 2710008E2D4B76355897036EF20C66BFBA2F1C4666DBB1DA4A589B10B291EE7BE2D97CBD50DDDACF enters raisePacketReceived.
11/16/17 12:50:44.383 Debug (My-CUL): Packet 2710008E2D4B76355897036EF20C66BFBA2F1C4666DBB1DA4A589B10B291EE7BE2D97CBD50DDDACF is now passed to the EventHandler.
11/16/17 12:50:44.383 HomeMatic BidCoS packet received (My-CUL, RSSI: -34 dBm): 2710008E2D4B76355897036EF20C66BFBA2F1C4666DBB1DA4A589B10B291EE7BE2D97CBD50DDDACF
11/16/17 12:50:44.383 Debug (My-CUL): Packet processing of packet 2710008E2D4B76355897036EF20C66BFBA2F1C4666DBB1DA4A589B10B291EE7BE2D97CBD50DDDACF took 0 ms.
11/16/17 12:50:50.039 UPnP Server: Debug: Sending notify packets.

Can you please tell me how far the CUL should be from the homematic device for the proper communication?

Thanks.

#9

Hey, this should be from 10cm to what is possible in your location. For pairing you should be near ~1m of the communication module.

#10

Hey @sudarshangb,

there is no pairing packet visible in your log. The long packet is no BidCoS packet. Are you trying to pair a HomeMatic IP device?

Cheers,

Sathya