Winmatic geht nicht

[shb256]

Hallo Leute,

ich habe versucht WinMatic an Homegear anzulernen, dass anlernen selbst klappt auch, leider hat der Channel 1 keine einstellbaren Parameter. Dort sollte sowas wie die Montageseite oder die Haltekraft stehen.
Zusätzlich erhalte ich die Servicemeldungen Gerätekommunikation aktuell gestört und Konfigurationsdaten stehen zur Übertragung an.
Und das ist auch die Stelle, an der ich etwas ratlos bin, warum will er Konfigurationsdateien übertragen und wieso kann er das auch nicht?
Ich habe etwas an dem WinMatic rumgedrückt, danach ist zeitweise, “Gerätekommunikation aktuell gestört” verschwunden, aber nur für 2,3 Minuten.

Ich nutzte Homegear 0.5.9 mit dem LAN Adapter.
Homegear ist mit openHAB gekoppelt, in openHAB hab ich nur die IP von der CCU auf homegear geändert, deswegen sollte die config auch richtig sein. Mit der CCU läuft sie ja.

Danke für die Hilfe.

Mit freundlichen Grüßen

stefan

[sathya]

Hey Stefan,

leider habe ich Homegear mit der WinMatic noch nicht testen können, weil ich selbst leider keine besitze. Generell sollte es aber funktionieren. Ich habe gerade mal zum Testen eine WinMatic manuell bei mir hinzugefügt und mit der Konfigurationssoftware hast du tatsächlich keine einstellbaren Parameter auf Kanal 1. Die sind aber da, werden auch übertragen und sind setzbar. Ich schau mir gleich an, warum die Konfigurationssoftware sie nicht anzeigt - das ist schnell gelöst.

Das zweite Problem kann ich nur mit deiner Hilfe lösen:
[ul]
[li] Setz den Debuglevel von Homegear in “/etc/homegear/main.conf” auf 4 und starte Homegear neu.[/li]
[li] Entferne die WinMatic aus Homegear (nicht ablernen, das wird vermutlich nicht gehen).[/li]
[li] Setze die WinMatic in den Werkszustand zurück wie auf Seite 30 der Anleitung beschrieben [1].[/li]
[li] Lerne die WinMatic erneut an die Masterfernbedienung und dann an Homegear an. Deaktivier den Anlernmodus in Homegear und versetz die WinMatic sicherheitshalber noch zwei Mal in den Anlernmodus, damit alle Konfigurationsparameter sicher übertragen sind. Öffne und schließe einmal das Fenster mit der Fernbedienung und schick mir die beiden Homegear-Log-Dateien (/var/log/homegear.log und /var/log/homegear.err).[/li][/ul]

In den Logs sollte ich sofort sehen, wo das Problem liegt und dir eine Lösung posten können .

Liebe Grüße

Sathya

[1] http://www.eq-3.de/Downloads/eq3/pdf_produkte/HM-Sec-Win_UM_GE_081218.pdf

[shb256]

Danke für die schnelle Antwort.
so hab die winmatic von der ccu abgelernt mit werksreset, dies ging auch mit homegear, danach hat sie sich porblemlos wieder an der ccu anlernen lassen.

Ich habe WinMatic nicht an einer Masterfernbedienung angelernt, da ich soetwas bis jetzt nie gebraucht habe. Ist das zwingend nötig? Mit der CCU und fhem ging es auch problemlos ohne.

hier die logs

[code]root@ubilinux:/var/log/homegear# /etc/init.d/homegear start
11/02/14 14:11:13.686 Info: Loading family module mod_max.so
11/02/14 14:11:13.702 Info: Loading family module mod_homematicbidcos.so
11/02/14 14:11:13.721 Info: Loading family module mod_homematicwired.so
11/02/14 14:11:13.733 Info: Loading family module mod_insteon.so
11/02/14 14:11:13.748 Info: Loading family module mod_philipshue.so
11/02/14 14:11:13.761 Module HomeMatic BidCoS: LAN-Konfigurationsadapter “My-HM-CFG-LAN”: Info: Enabling AES encryption for communication with HM-CFG-LAN.
11/02/14 14:11:13.765 Info: Disposing family module mod_philipshue.so
11/02/14 14:11:13.765 Info: Disposing family module mod_max.so
11/02/14 14:11:13.766 Info: Disposing family module mod_insteon.so
11/02/14 14:11:13.766 Info: Disposing family module mod_homematicwired.so
11/02/14 14:11:13.766 Info: Disposing family module mod_homematicbidcos.so
[…] Starting Homegear: homegear11/02/14 14:11:13.821 Loading RPC server settings from /etc/homegear/rpcservers.conf
11/02/14 14:11:13.823 Loading RPC client settings from /etc/homegear/rpcclients.conf
. ok
root@ubilinux:/var/log/homegear# homegear -r

fs 0
Device family “HomeMatic BidCoS” selected.
For information about the family’s commands type: “help”
(Family)> ds 1
Device selected.
For information about the device’s commands type: “help”
(Device)> ls
ID │ Name │ Address │ Serial Number │ Type │ Type String │ Firmware │ Config Pending │ Unreach
────────────┼───────────────────────────┼──────────┼───────────────┼──────┼───────────────────────────┼──────────┼────────────────┼────────
│ │ │ │ │ │ │ │
1 │ HM-LC-Sw1-Pl JEQ0054923 │ 199214 │ JEQ0054923 │ 0011 │ HM-LC-Sw1-Pl │ 1.9 │ No │ No
────────────┴───────────────────────────┴──────────┴───────────────┴──────┴───────────────────────────┴──────────┴────────────────┴────────
(Device)> pon
Pairing mode enabled.
(Device)> ls
ID │ Name │ Address │ Serial Number │ Type │ Type String │ Firmware │ Config Pending │ Unreach
────────────┼───────────────────────────┼──────────┼───────────────┼──────┼───────────────────────────┼──────────┼────────────────┼────────
│ │ │ │ │ │ │ │
1 │ HM-LC-Sw1-Pl JEQ0054923 │ 199214 │ JEQ0054923 │ 0011 │ HM-LC-Sw1-Pl │ 1.9 │ No │ No
2 │ │ 174C77 │ IEQ0505136 │ 0028 │ HM-Sec-Win │ 1.5 │ Yes │ No
────────────┴───────────────────────────┴──────────┴───────────────┴──────┴───────────────────────────┴──────────┴────────────────┴────────
(Device)> ls
ID │ Name │ Address │ Serial Number │ Type │ Type String │ Firmware │ Config Pending │ Unreach
────────────┼───────────────────────────┼──────────┼───────────────┼──────┼───────────────────────────┼──────────┼────────────────┼────────
│ │ │ │ │ │ │ │
1 │ HM-LC-Sw1-Pl JEQ0054923 │ 199214 │ JEQ0054923 │ 0011 │ HM-LC-Sw1-Pl │ 1.9 │ No │ No
2 │ │ 174C77 │ IEQ0505136 │ 0028 │ HM-Sec-Win │ 1.5 │ Yes │ Yes
────────────┴───────────────────────────┴──────────┴───────────────┴──────┴───────────────────────────┴──────────┴────────────────┴────────
(Device)> [/code]
homegear.err

root@ubilinux:/var/log/homegear# cat homegear.err 11/02/14 14:12:02.039 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "My-HM-CFG-LAN": Info: No response to packet after 3 tries: 1005B001FD2176174C7702050000000001 11/02/14 14:12:04.080 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "My-HM-CFG-LAN": Info: No response to packet after 3 tries: 1005B001FD2176174C7702050000000001 11/02/14 14:12:06.160 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "My-HM-CFG-LAN": Info: No response to packet after 3 tries: 1005B001FD2176174C7702050000000001 11/02/14 14:12:08.271 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "My-HM-CFG-LAN": Info: No response to packet after 3 tries: 1005B001FD2176174C7702050000000001
homegear.log

root@ubilinux:/var/log/homegear# cat homegear.log 11/02/14 14:11:13.834 Info: Loading family module mod_max.so 11/02/14 14:11:13.850 Info: Loading family module mod_homematicbidcos.so 11/02/14 14:11:13.870 Info: Loading family module mod_homematicwired.so 11/02/14 14:11:13.883 Info: Loading family module mod_insteon.so 11/02/14 14:11:13.898 Info: Loading family module mod_philipshue.so 11/02/14 14:11:13.965 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "My-HM-CFG-LAN": Info: Enabling AES encryption for communication with HM-CFG-LAN. 11/02/14 14:11:13.965 Initializing database... 11/02/14 14:11:13.976 Initializing family controller... 11/02/14 14:11:13.976 Module HomeMatic BidCoS: Loading XML RPC devices... 11/02/14 14:11:15.078 Info: Not initializing device family HomeMatic Wired, bacause no physical interface was found. 11/02/14 14:11:15.078 Info: Not initializing device family INSTEON, bacause no physical interface was found. 11/02/14 14:11:15.079 Info: Not initializing device family MAX!, bacause no physical interface was found. 11/02/14 14:11:15.079 Info: Not initializing device family Philips hue, bacause no physical interface was found. 11/02/14 14:11:15.079 Loading devices... 11/02/14 14:11:15.080 Module HomeMatic BidCoS: Loading HomeMatic BidCoS device 1 11/02/14 14:11:15.082 Module HomeMatic BidCoS: Loading peer 1 11/02/14 14:11:15.096 Module HomeMatic BidCoS: Loading HomeMatic BidCoS device 2 11/02/14 14:11:15.099 Start listening for packets... 11/02/14 14:11:15.099 Initializing RPC client... 11/02/14 14:11:15.100 Starting XML RPC server RPCServer1 listening on 0.0.0.0:2001... 11/02/14 14:11:15.100 Info: Connecting to host 192.168.200.3 on port 1000... 11/02/14 14:11:15.104 Starting XML RPC server RPCServer2 listening on 0.0.0.0:2002, SSL enabled... 11/02/14 14:11:15.104 RPC Server (Port 2001): Info: RPC Server started listening on address 0.0.0.0 and port 2001 11/02/14 14:11:15.121 Starting XML RPC server RPCServer3 listening on 0.0.0.0:2003, SSL enabled, authentification enabled... 11/02/14 14:11:15.121 RPC Server (Port 2002): Info: RPC Server started listening on address 0.0.0.0 and port 2002 11/02/14 14:11:15.124 Info: Connected to host 192.168.200.3 on port 1000. Client number is: 0 11/02/14 14:11:15.129 RPC Server (Port 2001): Info: Connection from 192.168.200.35:50987 accepted. Client number: 3 11/02/14 14:11:15.134 RPC Server (Port 2001): Info: Client number 3 is calling RPC method: listBidcosInterfaces Parameters: 11/02/14 14:11:15.140 RPC Server (Port 2001): Info: Connection to client number 3 closed (3). 11/02/14 14:11:15.142 Starting CLI server... 11/02/14 14:11:15.143 RPC Server (Port 2003): Info: RPC Server started listening on address 0.0.0.0 and port 2003 11/02/14 14:11:15.143 Initializing event handler... 11/02/14 14:11:15.143 Loading events... 11/02/14 14:11:15.144 Startup complete. 11/02/14 14:11:16.145 All physical interfaces are connected now. 11/02/14 14:11:16.159 RPC Server (Port 2001): Info: Connection from 192.168.200.35:50988 accepted. Client number: 6 11/02/14 14:11:16.160 RPC Server (Port 2001): Info: Client number 6 is calling RPC method: listBidcosInterfaces Parameters: 11/02/14 14:11:16.164 RPC Server (Port 2001): Info: Connection to client number 6 closed (3). 11/02/14 14:11:18.085 RPC Server (Port 2001): Info: Connection from 192.168.200.35:50995 accepted. Client number: 7 11/02/14 14:11:18.086 RPC Server (Port 2001): Info: Client number 7 is calling RPC method: getServiceMessages Parameters: 11/02/14 14:11:18.097 RPC Server (Port 2001): Info: Connection to client number 7 closed (3). 11/02/14 14:11:21.162 RPC Server (Port 2001): Info: Connection from 192.168.200.35:50996 accepted. Client number: 8 11/02/14 14:11:21.163 RPC Server (Port 2001): Info: Client number 8 is calling RPC method: listBidcosInterfaces Parameters: 11/02/14 14:11:21.169 RPC Server (Port 2001): Info: Connection to client number 8 closed (3). 11/02/14 14:11:21.405 Info: CLI connection accepted. Client number: 9 11/02/14 14:11:23.085 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51003 accepted. Client number: 10 11/02/14 14:11:23.090 RPC Server (Port 2001): Info: Client number 10 is calling RPC method: getServiceMessages Parameters: 11/02/14 14:11:23.168 RPC Server (Port 2001): Info: Connection to client number 10 closed (3). 11/02/14 14:11:25.390 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x49): 0CC986701A257800000000DA3C 11/02/14 14:11:25.391 Info (My-HM-CFG-LAN): Packet processing took 1 ms. 11/02/14 14:11:26.195 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51004 accepted. Client number: 11 11/02/14 14:11:26.195 RPC Server (Port 2001): Info: Client number 11 is calling RPC method: listBidcosInterfaces Parameters: 11/02/14 14:11:26.200 RPC Server (Port 2001): Info: Connection to client number 11 closed (3). 11/02/14 14:11:28.113 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51011 accepted. Client number: 12 11/02/14 14:11:28.168 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getServiceMessages Parameters: 11/02/14 14:11:28.196 RPC Server (Port 2001): Info: Connection to client number 12 closed (3). 11/02/14 14:11:31.214 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51014 accepted. Client number: 13 11/02/14 14:11:31.214 RPC Server (Port 2001): Info: Client number 13 is calling RPC method: listBidcosInterfaces Parameters: 11/02/14 14:11:31.222 RPC Server (Port 2001): Info: Connection to client number 13 closed (3). 11/02/14 14:11:33.143 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51021 accepted. Client number: 14 11/02/14 14:11:33.144 RPC Server (Port 2001): Info: Client number 14 is calling RPC method: getServiceMessages Parameters: 11/02/14 14:11:33.221 RPC Server (Port 2001): Info: Connection to client number 14 closed (3). 11/02/14 14:11:36.324 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51022 accepted. Client number: 15 11/02/14 14:11:36.327 RPC Server (Port 2001): Info: Client number 15 is calling RPC method: listBidcosInterfaces Parameters: 11/02/14 14:11:36.334 RPC Server (Port 2001): Info: Connection to client number 15 closed (3). 11/02/14 14:11:37.460 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x3D): 0C3C867019E34800000000D439 11/02/14 14:11:37.461 Info (My-HM-CFG-LAN): Packet processing took 1 ms. 11/02/14 14:11:38.123 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51029 accepted. Client number: 16 11/02/14 14:11:38.124 RPC Server (Port 2001): Info: Client number 16 is calling RPC method: getServiceMessages Parameters: 11/02/14 14:11:38.139 RPC Server (Port 2001): Info: Connection to client number 16 closed (3). 11/02/14 14:11:41.355 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51030 accepted. Client number: 17 11/02/14 14:11:41.357 RPC Server (Port 2001): Info: Client number 17 is calling RPC method: listBidcosInterfaces Parameters: 11/02/14 14:11:41.362 RPC Server (Port 2001): Info: Connection to client number 17 closed (3). 11/02/14 14:11:43.133 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51037 accepted. Client number: 18 11/02/14 14:11:43.134 RPC Server (Port 2001): Info: Client number 18 is calling RPC method: getServiceMessages Parameters: 11/02/14 14:11:43.144 RPC Server (Port 2001): Info: Connection to client number 18 closed (3). 11/02/14 14:11:45.420 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x40): 0BC9A2581A257813D2B80000 11/02/14 14:11:45.421 Info (My-HM-CFG-LAN): Packet processing took 1 ms. 11/02/14 14:11:45.505 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x39): 0EC9820213D2B81A2578010100002B 11/02/14 14:11:45.506 Info (My-HM-CFG-LAN): Packet processing took 0 ms. 11/02/14 14:11:46.453 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51038 accepted. Client number: 19 11/02/14 14:11:46.455 RPC Server (Port 2001): Info: Client number 19 is calling RPC method: listBidcosInterfaces Parameters: 11/02/14 14:11:46.459 RPC Server (Port 2001): Info: Connection to client number 19 closed (3). 11/02/14 14:11:48.292 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51045 accepted. Client number: 20 11/02/14 14:11:48.295 RPC Server (Port 2001): Info: Client number 20 is calling RPC method: getServiceMessages Parameters: 11/02/14 14:11:48.306 RPC Server (Port 2001): Info: Connection to client number 20 closed (3). 11/02/14 14:11:51.573 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51047 accepted. Client number: 21 11/02/14 14:11:51.574 RPC Server (Port 2001): Info: Client number 21 is calling RPC method: listBidcosInterfaces Parameters: 11/02/14 14:11:51.578 RPC Server (Port 2001): Info: Connection to client number 21 closed (3). 11/02/14 14:11:52.590 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x30): 1A028400174C7700000015002849455130353035313336C1000100 11/02/14 14:11:52.596 Module HomeMatic BidCoS: Info: Pushing pending queues. 11/02/14 14:11:52.596 Info (My-HM-CFG-LAN): Packet processing took 6 ms. 11/02/14 14:11:52.649 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "My-HM-CFG-LAN": Info: Sending (My-HM-CFG-LAN): 102AA001FD2176174C7700050000000000 11/02/14 14:11:53.135 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x32): 0E2A8002174C77FD2176004BB91E6B 11/02/14 14:11:53.136 Info (My-HM-CFG-LAN): Packet processing took 1 ms. 11/02/14 14:11:53.142 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51056 accepted. Client number: 22 11/02/14 14:11:53.144 RPC Server (Port 2001): Info: Client number 22 is calling RPC method: getServiceMessages Parameters: 11/02/14 14:11:53.155 RPC Server (Port 2001): Info: Connection to client number 22 closed (3). 11/02/14 14:11:53.194 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "My-HM-CFG-LAN": Info: Sending (My-HM-CFG-LAN): 132BA001FD2176174C77000802010AFD0B210C76 11/02/14 14:11:53.810 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x2F): 0E2B8002174C77FD217600C8D0C339 11/02/14 14:11:53.810 Info (My-HM-CFG-LAN): Packet processing took 0 ms. 11/02/14 14:11:53.870 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "My-HM-CFG-LAN": Info: Sending (My-HM-CFG-LAN): 0B2CA001FD2176174C770006 11/02/14 14:11:54.450 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x2B): 0E2C8002174C77FD2176009166A5B9 11/02/14 14:11:54.486 Module HomeMatic BidCoS: Added peer 0x174C77. 11/02/14 14:11:54.488 Module HomeMatic BidCoS: Info: Parameter AES_ACTIVE of peer 2 and channel 1 was set to 0x01. 11/02/14 14:11:54.493 Module HomeMatic BidCoS: Info: Parameter AES_ACTIVE of peer 2 and channel 2 was set to 0x01. 11/02/14 14:11:54.496 Info (My-HM-CFG-LAN): Packet processing took 46 ms. 11/02/14 14:11:54.510 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "My-HM-CFG-LAN": Info: Sending (My-HM-CFG-LAN): 102DB001FD2176174C7700040000000000 11/02/14 14:11:55.209 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x2E): 162DA010174C77FD217602020103190AFD0B210C760000 11/02/14 14:11:55.268 Info (My-HM-CFG-LAN): Packet processing took 58 ms. 11/02/14 14:11:55.327 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "My-HM-CFG-LAN": Info: Sending (My-HM-CFG-LAN): 102EA001FD2176174C7701040000000001 11/02/14 14:11:55.722 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x2C): 142EA010174C77FD21760216001C641D641EFF0000 11/02/14 14:11:55.782 Info (My-HM-CFG-LAN): Packet processing took 60 ms. 11/02/14 14:11:55.841 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "My-HM-CFG-LAN": Info: Sending (My-HM-CFG-LAN): 0B2FA001FD2176174C770103 11/02/14 14:11:56.239 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x2B): 0E2FA010174C77FD21760100000000 11/02/14 14:11:56.298 Info (My-HM-CFG-LAN): Packet processing took 59 ms. 11/02/14 14:11:56.357 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "My-HM-CFG-LAN": Info: Sending (My-HM-CFG-LAN): 1000B001FD2176174C7701050000000001 11/02/14 14:11:56.593 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51060 accepted. Client number: 23 11/02/14 14:11:56.595 RPC Server (Port 2001): Info: Client number 23 is calling RPC method: listBidcosInterfaces Parameters: 11/02/14 14:11:56.667 RPC Server (Port 2001): Info: Connection to client number 23 closed (3). 11/02/14 14:11:57.370 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x2B): 0E008002174C77FD2176003C0268DA 11/02/14 14:11:57.371 Info (My-HM-CFG-LAN): Packet processing took 1 ms. 11/02/14 14:11:57.429 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "My-HM-CFG-LAN": Info: Sending (My-HM-CFG-LAN): 0D01A001FD2176174C7701080801 11/02/14 14:11:57.455 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x3E): 0B3CA25819E348193D6D0000 11/02/14 14:11:57.455 Info (My-HM-CFG-LAN): Packet processing took 0 ms. 11/02/14 14:11:57.625 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x4A): 0E3C8202193D6D19E3480101000044 11/02/14 14:11:57.625 Info (My-HM-CFG-LAN): Packet processing took 0 ms. 11/02/14 14:11:58.020 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x2D): 0E018002174C77FD217602DD2F0A29 11/02/14 14:11:58.020 Info (My-HM-CFG-LAN): Packet processing took 0 ms. 11/02/14 14:11:58.080 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "My-HM-CFG-LAN": Info: Sending (My-HM-CFG-LAN): 0B02A001FD2176174C770106 11/02/14 14:11:58.130 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51069 accepted. Client number: 24 11/02/14 14:11:58.132 RPC Server (Port 2001): Info: Client number 24 is calling RPC method: getServiceMessages Parameters: 11/02/14 14:11:58.147 RPC Server (Port 2001): Info: Connection to client number 24 closed (3). 11/02/14 14:11:58.658 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x2A): 0E028002174C77FD217600B57810DF 11/02/14 14:11:58.659 Info (My-HM-CFG-LAN): Packet processing took 1 ms. 11/02/14 14:11:58.718 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "My-HM-CFG-LAN": Info: Sending (My-HM-CFG-LAN): 0B03A004FD2176174C770100 11/02/14 14:11:59.349 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x2B): 0E038002174C77FD217600A5BB9834 11/02/14 14:11:59.350 Info (My-HM-CFG-LAN): Packet processing took 0 ms. 11/02/14 14:11:59.409 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "My-HM-CFG-LAN": Info: Sending (My-HM-CFG-LAN): 0B04A004FD2176174C770101 11/02/14 14:11:59.980 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x2B): 0E048002174C77FD2176001047BC78 11/02/14 14:11:59.982 Module HomeMatic BidCoS: Info: Successfully changed AES key of peer 2. Key index now is: 1 11/02/14 14:11:59.984 Info (My-HM-CFG-LAN): Packet processing took 4 ms. 11/02/14 14:12:00.039 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "My-HM-CFG-LAN": Info: Sending (My-HM-CFG-LAN): 1005B001FD2176174C7702050000000001 11/02/14 14:12:01.712 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51072 accepted. Client number: 25 11/02/14 14:12:01.715 RPC Server (Port 2001): Info: Client number 25 is calling RPC method: listBidcosInterfaces Parameters: 11/02/14 14:12:01.787 RPC Server (Port 2001): Info: Connection to client number 25 closed (3). 11/02/14 14:12:02.039 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "My-HM-CFG-LAN": Info: No response to packet after 3 tries: 1005B001FD2176174C7702050000000001 11/02/14 14:12:02.040 Module HomeMatic BidCoS: Info: Queue is not finished (peer: 2). Retrying... 11/02/14 14:12:02.141 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "My-HM-CFG-LAN": Info: Sending (My-HM-CFG-LAN): 1005B001FD2176174C7702050000000001 11/02/14 14:12:03.123 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51079 accepted. Client number: 26 11/02/14 14:12:03.125 RPC Server (Port 2001): Info: Client number 26 is calling RPC method: getServiceMessages Parameters: 11/02/14 14:12:03.140 RPC Server (Port 2001): Info: Connection to client number 26 closed (3). 11/02/14 14:12:04.080 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "My-HM-CFG-LAN": Info: No response to packet after 3 tries: 1005B001FD2176174C7702050000000001 11/02/14 14:12:04.152 Module HomeMatic BidCoS: Info: Queue is not finished (peer: 2). Retrying... 11/02/14 14:12:04.253 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "My-HM-CFG-LAN": Info: Sending (My-HM-CFG-LAN): 1005B001FD2176174C7702050000000001 11/02/14 14:12:06.159 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "My-HM-CFG-LAN": Info: No response to packet after 3 tries: 1005B001FD2176174C7702050000000001 11/02/14 14:12:06.263 Module HomeMatic BidCoS: Info: Queue is not finished (peer: 2). Retrying... 11/02/14 14:12:06.364 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "My-HM-CFG-LAN": Info: Sending (My-HM-CFG-LAN): 1005B001FD2176174C7702050000000001 11/02/14 14:12:06.784 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51080 accepted. Client number: 27 11/02/14 14:12:06.786 RPC Server (Port 2001): Info: Client number 27 is calling RPC method: listBidcosInterfaces Parameters: 11/02/14 14:12:06.857 RPC Server (Port 2001): Info: Connection to client number 27 closed (3). 11/02/14 14:12:08.132 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51087 accepted. Client number: 28 11/02/14 14:12:08.135 RPC Server (Port 2001): Info: Client number 28 is calling RPC method: getServiceMessages Parameters: 11/02/14 14:12:08.149 RPC Server (Port 2001): Info: Connection to client number 28 closed (3). 11/02/14 14:12:08.270 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "My-HM-CFG-LAN": Info: No response to packet after 3 tries: 1005B001FD2176174C7702050000000001 11/02/14 14:12:08.375 Info: Peer 2 is unreachable. 11/02/14 14:12:11.872 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51088 accepted. Client number: 29 11/02/14 14:12:11.874 RPC Server (Port 2001): Info: Client number 29 is calling RPC method: listBidcosInterfaces Parameters: 11/02/14 14:12:11.947 RPC Server (Port 2001): Info: Connection to client number 29 closed (3). 11/02/14 14:12:13.172 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51095 accepted. Client number: 30 11/02/14 14:12:13.174 RPC Server (Port 2001): Info: Client number 30 is calling RPC method: getServiceMessages Parameters: 11/02/14 14:12:13.203 RPC Server (Port 2001): Info: Connection to client number 30 closed (3). 11/02/14 14:12:17.073 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51097 accepted. Client number: 31 11/02/14 14:12:17.078 RPC Server (Port 2001): Info: Client number 31 is calling RPC method: listBidcosInterfaces Parameters: 11/02/14 14:12:17.082 RPC Server (Port 2001): Info: Connection to client number 31 closed (3). 11/02/14 14:12:18.304 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51104 accepted. Client number: 32 11/02/14 14:12:18.305 RPC Server (Port 2001): Info: Client number 32 is calling RPC method: getServiceMessages Parameters: 11/02/14 14:12:18.321 RPC Server (Port 2001): Info: Connection to client number 32 closed (3). 11/02/14 14:12:22.195 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51105 accepted. Client number: 33 11/02/14 14:12:22.197 RPC Server (Port 2001): Info: Client number 33 is calling RPC method: listBidcosInterfaces Parameters: 11/02/14 14:12:22.270 RPC Server (Port 2001): Info: Connection to client number 33 closed (3). 11/02/14 14:12:23.312 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51112 accepted. Client number: 34 11/02/14 14:12:23.315 RPC Server (Port 2001): Info: Client number 34 is calling RPC method: getServiceMessages Parameters: 11/02/14 14:12:23.329 RPC Server (Port 2001): Info: Connection to client number 34 closed (3). 11/02/14 14:12:31.302 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51119 accepted. Client number: 35 11/02/14 14:12:31.305 RPC Server (Port 2001): Info: Client number 35 is calling RPC method: listBidcosInterfaces Parameters: 11/02/14 14:12:31.321 RPC Server (Port 2001): Info: Connection to client number 35 closed (3). 11/02/14 14:12:31.810 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x38): 0CE5867019386700000000DB37 11/02/14 14:12:31.811 Info (My-HM-CFG-LAN): Packet processing took 1 ms. 11/02/14 14:12:32.324 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51135 accepted. Client number: 36 11/02/14 14:12:32.324 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51136 accepted. Client number: 37 11/02/14 14:12:32.325 RPC Server (Port 2001): Info: Client number 37 is calling RPC method: listBidcosInterfaces Parameters: 11/02/14 14:12:32.325 RPC Server (Port 2001): Info: Client number 36 is calling RPC method: getServiceMessages Parameters: 11/02/14 14:12:32.328 RPC Server (Port 2001): Info: Client number 37 is calling RPC method: listDevices Parameters: (Boolean) 0 11/02/14 14:12:32.339 RPC Server (Port 2001): Info: Connection to client number 36 closed (3). 11/02/14 14:12:32.347 RPC Server (Port 2001): Info: Client number 37 is calling RPC method: getAllMetadata Parameters: (String) JEQ0054923 11/02/14 14:12:32.363 RPC Server (Port 2001): Info: Client number 37 is calling RPC method: getAllMetadata Parameters: (String) IEQ0505136 11/02/14 14:12:32.370 RPC Server (Port 2001): Info: Connection to client number 37 closed (3). 11/02/14 14:12:34.922 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51141 accepted. Client number: 38 11/02/14 14:12:34.924 RPC Server (Port 2001): Info: Client number 38 is calling RPC method: getParamset Parameters: (String) BidCoS-RF:0 (String) MASTER 11/02/14 14:12:34.932 RPC Server (Port 2001): Info: Connection to client number 38 closed (3). 11/02/14 14:12:36.332 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51142 accepted. Client number: 39 11/02/14 14:12:36.335 RPC Server (Port 2001): Info: Client number 39 is calling RPC method: listBidcosInterfaces Parameters: 11/02/14 14:12:36.408 RPC Server (Port 2001): Info: Connection to client number 39 closed (3). 11/02/14 14:12:37.492 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51148 accepted. Client number: 40 11/02/14 14:12:37.494 RPC Server (Port 2001): Info: Client number 40 is calling RPC method: getServiceMessages Parameters: 11/02/14 14:12:37.510 RPC Server (Port 2001): Info: Connection to client number 40 closed (3). 11/02/14 14:12:41.018 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51154 accepted. Client number: 41 11/02/14 14:12:41.019 RPC Server (Port 2001): Info: Client number 41 is calling RPC method: listBidcosInterfaces Parameters: 11/02/14 14:12:41.026 RPC Server (Port 2001): Info: Connection to client number 41 closed (3). 11/02/14 14:12:42.083 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51170 accepted. Client number: 42 11/02/14 14:12:42.083 RPC Server (Port 2001): Info: Client number 42 is calling RPC method: listBidcosInterfaces Parameters: 11/02/14 14:12:42.087 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51171 accepted. Client number: 43 11/02/14 14:12:42.089 RPC Server (Port 2001): Info: Client number 43 is calling RPC method: getServiceMessages Parameters: 11/02/14 14:12:42.094 RPC Server (Port 2001): Info: Client number 42 is calling RPC method: listDevices Parameters: (Boolean) 0 11/02/14 14:12:42.103 RPC Server (Port 2001): Info: Connection to client number 43 closed (3). 11/02/14 14:12:42.116 RPC Server (Port 2001): Info: Client number 42 is calling RPC method: getAllMetadata Parameters: (String) JEQ0054923 11/02/14 14:12:42.131 RPC Server (Port 2001): Info: Client number 42 is calling RPC method: getAllMetadata Parameters: (String) IEQ0505136 11/02/14 14:12:42.143 RPC Server (Port 2001): Info: Connection to client number 42 closed (3). 11/02/14 14:12:45.854 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51175 accepted. Client number: 44 11/02/14 14:12:45.855 RPC Server (Port 2001): Info: Client number 44 is calling RPC method: getServiceMessages Parameters: 11/02/14 14:12:45.874 RPC Server (Port 2001): Info: Client number 44 is calling RPC method: getDeviceDescription Parameters: (String) IEQ0505136:0 11/02/14 14:12:45.882 RPC Server (Port 2001): Info: Client number 44 is calling RPC method: getDeviceDescription Parameters: (String) IEQ0505136 11/02/14 14:12:45.888 RPC Server (Port 2001): Info: Client number 44 is calling RPC method: getAllMetadata Parameters: (String) IEQ0505136 11/02/14 14:12:45.894 RPC Server (Port 2001): Info: Client number 44 is calling RPC method: getParamsetDescription Parameters: (String) IEQ0505136:0 (String) VALUES 11/02/14 14:12:45.908 RPC Server (Port 2001): Info: Client number 44 is calling RPC method: getDeviceDescription Parameters: (String) IEQ0505136:0 11/02/14 14:12:45.914 RPC Server (Port 2001): Info: Client number 44 is calling RPC method: getDeviceDescription Parameters: (String) IEQ0505136 11/02/14 14:12:45.921 RPC Server (Port 2001): Info: Client number 44 is calling RPC method: getAllMetadata Parameters: (String) IEQ0505136 11/02/14 14:12:45.931 RPC Server (Port 2001): Info: Client number 44 is calling RPC method: getParamsetDescription Parameters: (String) IEQ0505136:0 (String) VALUES 11/02/14 14:12:45.938 RPC Server (Port 2001): Info: Client number 44 is calling RPC method: getDeviceDescription Parameters: (String) IEQ0505136:0 11/02/14 14:12:45.944 RPC Server (Port 2001): Info: Client number 44 is calling RPC method: getDeviceDescription Parameters: (String) IEQ0505136 11/02/14 14:12:45.950 RPC Server (Port 2001): Info: Client number 44 is calling RPC method: getAllMetadata Parameters: (String) IEQ0505136 11/02/14 14:12:45.955 RPC Server (Port 2001): Info: Client number 44 is calling RPC method: getParamsetDescription Parameters: (String) IEQ0505136:0 (String) VALUES 11/02/14 14:12:45.964 RPC Server (Port 2001): Info: Connection to client number 44 closed (3). 11/02/14 14:12:46.048 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51176 accepted. Client number: 45 11/02/14 14:12:46.051 RPC Server (Port 2001): Info: Client number 45 is calling RPC method: listBidcosInterfaces Parameters: 11/02/14 14:12:46.057 RPC Server (Port 2001): Info: Connection to client number 45 closed (3). 11/02/14 14:12:47.269 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51183 accepted. Client number: 46 11/02/14 14:12:47.272 RPC Server (Port 2001): Info: Client number 46 is calling RPC method: getServiceMessages Parameters: 11/02/14 14:12:47.349 RPC Server (Port 2001): Info: Connection to client number 46 closed (3). 11/02/14 14:12:51.064 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51184 accepted. Client number: 47 11/02/14 14:12:51.067 RPC Server (Port 2001): Info: Client number 47 is calling RPC method: listBidcosInterfaces Parameters: 11/02/14 14:12:51.075 RPC Server (Port 2001): Info: Connection to client number 47 closed (3). 11/02/14 14:12:51.701 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x37): 0BE5A25819386719DCB70000 11/02/14 14:12:51.701 Info (My-HM-CFG-LAN): Packet processing took 0 ms. 11/02/14 14:12:52.253 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51191 accepted. Client number: 48 11/02/14 14:12:52.254 RPC Server (Port 2001): Info: Client number 48 is calling RPC method: getServiceMessages Parameters: 11/02/14 14:12:52.269 RPC Server (Port 2001): Info: Connection to client number 48 closed (3). 11/02/14 14:12:56.094 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51192 accepted. Client number: 49 11/02/14 14:12:56.095 RPC Server (Port 2001): Info: Client number 49 is calling RPC method: listBidcosInterfaces Parameters: 11/02/14 14:12:56.099 RPC Server (Port 2001): Info: Connection to client number 49 closed (3). 11/02/14 14:12:57.285 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51199 accepted. Client number: 50 11/02/14 14:12:57.288 RPC Server (Port 2001): Info: Client number 50 is calling RPC method: getServiceMessages Parameters: 11/02/14 14:12:57.305 RPC Server (Port 2001): Info: Connection to client number 50 closed (3). 11/02/14 14:12:58.330 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x39): 0C0786701A25CE00000000E539 11/02/14 14:12:58.330 Info (My-HM-CFG-LAN): Packet processing took 0 ms. 11/02/14 14:13:01.112 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51200 accepted. Client number: 51 11/02/14 14:13:01.115 RPC Server (Port 2001): Info: Client number 51 is calling RPC method: listBidcosInterfaces Parameters: 11/02/14 14:13:01.199 RPC Server (Port 2001): Info: Connection to client number 51 closed (3). 11/02/14 14:13:02.272 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51207 accepted. Client number: 52 11/02/14 14:13:02.275 RPC Server (Port 2001): Info: Client number 52 is calling RPC method: getServiceMessages Parameters: 11/02/14 14:13:02.289 RPC Server (Port 2001): Info: Connection to client number 52 closed (3). 11/02/14 14:13:06.222 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51208 accepted. Client number: 53 11/02/14 14:13:06.225 RPC Server (Port 2001): Info: Client number 53 is calling RPC method: listBidcosInterfaces Parameters: 11/02/14 14:13:06.297 RPC Server (Port 2001): Info: Connection to client number 53 closed (3). 11/02/14 14:13:07.282 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51215 accepted. Client number: 54 11/02/14 14:13:07.285 RPC Server (Port 2001): Info: Client number 54 is calling RPC method: getServiceMessages Parameters: 11/02/14 14:13:07.299 RPC Server (Port 2001): Info: Connection to client number 54 closed (3). 11/02/14 14:13:11.313 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51216 accepted. Client number: 55 11/02/14 14:13:11.315 RPC Server (Port 2001): Info: Client number 55 is calling RPC method: listBidcosInterfaces Parameters: 11/02/14 14:13:11.364 RPC Server (Port 2001): Info: Connection to client number 55 closed (3). 11/02/14 14:13:12.293 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51223 accepted. Client number: 56 11/02/14 14:13:12.295 RPC Server (Port 2001): Info: Client number 56 is calling RPC method: getServiceMessages Parameters: 11/02/14 14:13:12.310 RPC Server (Port 2001): Info: Connection to client number 56 closed (3). 11/02/14 14:13:16.463 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51224 accepted. Client number: 57 11/02/14 14:13:16.466 RPC Server (Port 2001): Info: Client number 57 is calling RPC method: listBidcosInterfaces Parameters: 11/02/14 14:13:16.537 RPC Server (Port 2001): Info: Connection to client number 57 closed (3). 11/02/14 14:13:17.382 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51231 accepted. Client number: 58 11/02/14 14:13:17.385 RPC Server (Port 2001): Info: Client number 58 is calling RPC method: getServiceMessages Parameters: 11/02/14 14:13:17.400 RPC Server (Port 2001): Info: Connection to client number 58 closed (3). 11/02/14 14:13:18.400 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x3A): 0B07A2581A25CE13A2200024 11/02/14 14:13:18.401 Info (My-HM-CFG-LAN): Packet processing took 1 ms. 11/02/14 14:13:18.443 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x3F): 0E07820213A2201A25CE01011C0029 11/02/14 14:13:18.444 Info (My-HM-CFG-LAN): Packet processing took 0 ms. 11/02/14 14:13:21.581 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51232 accepted. Client number: 59 11/02/14 14:13:21.584 RPC Server (Port 2001): Info: Client number 59 is calling RPC method: listBidcosInterfaces Parameters: 11/02/14 14:13:21.658 RPC Server (Port 2001): Info: Connection to client number 59 closed (3). 11/02/14 14:13:22.403 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51239 accepted. Client number: 60 11/02/14 14:13:22.404 RPC Server (Port 2001): Info: Client number 60 is calling RPC method: getServiceMessages Parameters: 11/02/14 14:13:22.419 RPC Server (Port 2001): Info: Connection to client number 60 closed (3). 11/02/14 14:13:26.702 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51240 accepted. Client number: 61 11/02/14 14:13:26.704 RPC Server (Port 2001): Info: Client number 61 is calling RPC method: listBidcosInterfaces Parameters: 11/02/14 14:13:26.777 RPC Server (Port 2001): Info: Connection to client number 61 closed (3). 11/02/14 14:13:27.313 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51247 accepted. Client number: 62 11/02/14 14:13:27.315 RPC Server (Port 2001): Info: Client number 62 is calling RPC method: getServiceMessages Parameters: 11/02/14 14:13:27.330 RPC Server (Port 2001): Info: Connection to client number 62 closed (3). 11/02/14 14:13:31.822 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51248 accepted. Client number: 63 11/02/14 14:13:31.863 RPC Server (Port 2001): Info: Client number 63 is calling RPC method: listBidcosInterfaces Parameters: 11/02/14 14:13:31.935 RPC Server (Port 2001): Info: Connection to client number 63 closed (3). 11/02/14 14:13:32.342 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51255 accepted. Client number: 64 11/02/14 14:13:32.345 RPC Server (Port 2001): Info: Client number 64 is calling RPC method: getServiceMessages Parameters: 11/02/14 14:13:32.359 RPC Server (Port 2001): Info: Connection to client number 64 closed (3). 11/02/14 14:13:33.050 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x39): 0CD386701A273200000000E837 11/02/14 14:13:33.050 Info (My-HM-CFG-LAN): Packet processing took 0 ms. 11/02/14 14:13:36.942 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51259 accepted. Client number: 65 11/02/14 14:13:36.945 RPC Server (Port 2001): Info: Client number 65 is calling RPC method: listBidcosInterfaces Parameters: 11/02/14 14:13:36.948 RPC Server (Port 2001): Info: Connection to client number 65 closed (3). 11/02/14 14:13:37.354 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51263 accepted. Client number: 66 11/02/14 14:13:37.356 RPC Server (Port 2001): Info: Client number 66 is calling RPC method: getServiceMessages Parameters: 11/02/14 14:13:37.371 RPC Server (Port 2001): Info: Connection to client number 66 closed (3). 11/02/14 14:13:39.190 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x41): 0CCA86701A257800000000DA3C 11/02/14 14:13:39.191 Info (My-HM-CFG-LAN): Packet processing took 0 ms. 11/02/14 14:13:42.063 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51267 accepted. Client number: 67 11/02/14 14:13:42.065 RPC Server (Port 2001): Info: Client number 67 is calling RPC method: listBidcosInterfaces Parameters: 11/02/14 14:13:42.137 RPC Server (Port 2001): Info: Connection to client number 67 closed (3). 11/02/14 14:13:42.333 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51271 accepted. Client number: 68 11/02/14 14:13:42.335 RPC Server (Port 2001): Info: Client number 68 is calling RPC method: getServiceMessages Parameters: 11/02/14 14:13:42.350 RPC Server (Port 2001): Info: Connection to client number 68 closed (3). 11/02/14 14:13:47.183 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51275 accepted. Client number: 69 11/02/14 14:13:47.185 RPC Server (Port 2001): Info: Client number 69 is calling RPC method: listBidcosInterfaces Parameters: 11/02/14 14:13:47.328 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51279 accepted. Client number: 70 11/02/14 14:13:47.330 RPC Server (Port 2001): Info: Client number 70 is calling RPC method: getServiceMessages Parameters: 11/02/14 14:13:47.345 RPC Server (Port 2001): Info: Connection to client number 70 closed (3). 11/02/14 14:13:47.348 RPC Server (Port 2001): Info: Connection to client number 69 closed (3). 11/02/14 14:13:49.450 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x3C): 0C3D867019E34800000000D439 11/02/14 14:13:49.451 Info (My-HM-CFG-LAN): Packet processing took 1 ms. 11/02/14 14:13:52.272 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51286 accepted. Client number: 71 11/02/14 14:13:52.273 RPC Server (Port 2001): Info: Client number 71 is calling RPC method: listBidcosInterfaces Parameters: 11/02/14 14:13:52.317 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51287 accepted. Client number: 72 11/02/14 14:13:52.322 RPC Server (Port 2001): Info: Client number 72 is calling RPC method: getServiceMessages Parameters: 11/02/14 14:13:52.325 RPC Server (Port 2001): Info: Connection to client number 71 closed (3). 11/02/14 14:13:52.336 RPC Server (Port 2001): Info: Connection to client number 72 closed (3). 11/02/14 14:13:52.950 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x3A): 0BD3A2581A273213D31F001F 11/02/14 14:13:52.951 Info (My-HM-CFG-LAN): Packet processing took 1 ms. 11/02/14 14:13:53.079 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x30): 0ED3820213D31F1A27320101180038 11/02/14 14:13:53.080 Info (My-HM-CFG-LAN): Packet processing took 1 ms. 11/02/14 14:13:57.343 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51294 accepted. Client number: 73 11/02/14 14:13:57.344 RPC Server (Port 2001): Info: Client number 73 is calling RPC method: listBidcosInterfaces Parameters: 11/02/14 14:13:57.344 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51295 accepted. Client number: 74 11/02/14 14:13:57.400 RPC Server (Port 2001): Info: Client number 74 is calling RPC method: getServiceMessages Parameters: 11/02/14 14:13:57.416 RPC Server (Port 2001): Info: Connection to client number 73 closed (3). 11/02/14 14:13:57.418 RPC Server (Port 2001): Info: Connection to client number 74 closed (3). 11/02/14 14:13:59.160 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x41): 0BCAA2581A257813D2B80000 11/02/14 14:13:59.161 Info (My-HM-CFG-LAN): Packet processing took 1 ms. 11/02/14 14:13:59.265 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x3B): 0ECA820213D2B81A2578010100002B 11/02/14 14:13:59.266 Info (My-HM-CFG-LAN): Packet processing took 1 ms. 11/02/14 14:14:02.442 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51302 accepted. Client number: 76 11/02/14 14:14:02.443 RPC Server (Port 2001): Info: Client number 76 is calling RPC method: getServiceMessages Parameters: 11/02/14 14:14:02.448 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51303 accepted. Client number: 77 11/02/14 14:14:02.501 RPC Server (Port 2001): Info: Client number 77 is calling RPC method: listBidcosInterfaces Parameters: 11/02/14 14:14:02.564 RPC Server (Port 2001): Info: Connection to client number 77 closed (3). 11/02/14 14:14:02.565 RPC Server (Port 2001): Info: Connection to client number 76 closed (3). 11/02/14 14:14:07.358 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51310 accepted. Client number: 78 11/02/14 14:14:07.361 RPC Server (Port 2001): Info: Client number 78 is calling RPC method: getServiceMessages Parameters: 11/02/14 14:14:07.376 RPC Server (Port 2001): Info: Connection to client number 78 closed (3). 11/02/14 14:14:07.558 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51311 accepted. Client number: 79 11/02/14 14:14:07.560 RPC Server (Port 2001): Info: Client number 79 is calling RPC method: listBidcosInterfaces Parameters: 11/02/14 14:14:07.640 RPC Server (Port 2001): Info: Connection to client number 79 closed (3). 11/02/14 14:14:09.438 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x3E): 0B3DA25819E348193D6D0000 11/02/14 14:14:09.438 Info (My-HM-CFG-LAN): Packet processing took 0 ms. 11/02/14 14:14:09.577 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x44): 0E3D8202193D6D19E3480101000046 11/02/14 14:14:09.577 Info (My-HM-CFG-LAN): Packet processing took 0 ms. 11/02/14 14:14:11.380 (Shutdown) => Stopping Homegear (Signal: 15) 11/02/14 14:14:11.381 (Shutdown) => Stopping CLI server 11/02/14 14:14:11.652 (Shutdown) => Stopping RPC servers 11/02/14 14:14:12.360 RPC Server (Port 2001): Info: Connection from 192.168.200.35:51318 accepted. Client number: 80 11/02/14 14:14:15.308 (Shutdown) => Stopping Event handler 11/02/14 14:14:15.308 (Shutdown) => Stopping RPC client 11/02/14 14:14:15.308 (Shutdown) => Closing physical devices 11/02/14 14:14:19.637 (Shutdown) => Saving devices 11/02/14 14:14:19.637 (Shutdown) => Saving devices 11/02/14 14:14:19.637 (Shutdown) => Saving HomeMatic BidCoS device 1 11/02/14 14:14:19.641 Module HomeMatic BidCoS: (Shutdown) => Saving HomeMatic BidCoS peer 2 with address 0x174C77 11/02/14 14:14:19.644 Module HomeMatic BidCoS: (Shutdown) => Saving HomeMatic BidCoS peer 1 with address 0x199214 11/02/14 14:14:19.646 (Shutdown) => Saving HomeMatic BidCoS device 2 11/02/14 14:14:19.652 (Shutdown) => Disposing device families 11/02/14 14:14:21.171 Info: Disposing family module mod_philipshue.so 11/02/14 14:14:21.171 Info: Disposing family module mod_max.so 11/02/14 14:14:21.171 Info: Disposing family module mod_insteon.so 11/02/14 14:14:21.172 Info: Disposing family module mod_homematicwired.so 11/02/14 14:14:21.172 Info: Disposing family module mod_homematicbidcos.so 11/02/14 14:14:21.227 Closing database... 11/02/14 14:14:21.228 Can't execute "COMMIT": cannot commit - no transaction is active 11/02/14 14:14:21.228 (Shutdown) => Shutdown complete. root@ubilinux:/var/log/homegear#

Mfg
Stefan

[sathya]

Hallo Stefan,

nein, du brauchst keine Master-Fernbedienung - ich hatte von der KeyMatic auf die WinMatic geschlossen. Das Log sieht auch soweit gut aus. Das Anlernen klappt im Prinzip, nur klappt das Auslesen der Konfigurationsparameter von Kanal 2 nicht. Das Paket wird von der WinMatic nicht akzeptiert.
Mach mal folgendes:

[ul]
[li] Öffne das Homegear CLI mit “sudo homegear -r”[/li]
[li] Dann gib ein:

fs 0 ds c ps 2 queues clear [/li][/ul]

Damit werden die noch ausstehenden Konfigurationsparameter aus der Warteschlange gelöscht. Das ist ohnehin nur “AES_ACTIVE”, welches bereits aktiviert ist, also sind die Pakete ohnehin irrelevant.

Den Konfigurationssoftware-Fehler habe ich auch gefunden und in Version 0.5.10 ist er behoben. Damit du sie mit Version 0.5.9 siehst, mach folgendes:

[ul]
[li] Öffne die Datei “/etc/homegear/devices/0/rf_winmatic.xml”.[/li]
[li] Suche die Zeile “” und ändere sie in “”.[/li]
[li] Starte Homegear neu.[/li][/ul]

Jetzt sollten alle Konfigurationsparameter sichtbar sein.

Gib mir eine kurze Rückmeldung, ob’s funktioniert. Wenn ja, muss mich mir was mit dem zweiten Kanal überlegen. Danke für’s Helfen beim Debuggen .

Liebe Grüße

Sathya

[shb256]

danke,
die queue ist leer

For information about the device's commands type: "help" (Device)> ls ID │ Name │ Address │ Serial Number │ Type │ Type String │ Firmware │ Config Pending │ Unreach ────────────┼───────────────────────────┼──────────┼───────────────┼──────┼───────────────────────────┼──────────┼────────────────┼──────── │ │ │ │ │ │ │ │ 1 │ HM-LC-Sw1-Pl JEQ0054923 │ 199214 │ JEQ0054923 │ 0011 │ HM-LC-Sw1-Pl │ 1.9 │ No │ No 2 │ │ 174C77 │ IEQ0505136 │ 0028 │ HM-Sec-Win │ 1.5 │ No │ Yes ────────────┴───────────────────────────┴──────────┴───────────────┴──────┴───────────────────────────┴──────────┴────────────────┴──────── (Device)> queues clear Unknown command. (Device)> ps 2 Peer with id 2 and device type 0x28 selected. For information about the peer's commands type: "help" (Peer)> queues clear All pending BidCoSQueues were deleted. (Peer)> lx Unknown command. (Peer)> ls Unknown command. (Peer)> u Peer unselected. (Device)> ls ID │ Name │ Address │ Serial Number │ Type │ Type String │ Firmware │ Config Pending │ Unreach ────────────┼───────────────────────────┼──────────┼───────────────┼──────┼───────────────────────────┼──────────┼────────────────┼──────── │ │ │ │ │ │ │ │ 1 │ HM-LC-Sw1-Pl JEQ0054923 │ 199214 │ JEQ0054923 │ 0011 │ HM-LC-Sw1-Pl │ 1.9 │ No │ No 2 │ │ 174C77 │ IEQ0505136 │ 0028 │ HM-Sec-Win │ 1.5 │ No │ Yes ────────────┴───────────────────────────┴──────────┴───────────────┴──────┴───────────────────────────┴──────────┴────────────────┴──────── (Device)>

leider ist das gerät immer noch nicht erreichbar
homegear.err

11/02/14 17:16:49.060 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "My-HM-CFG-LAN": Info: No response to packet after 3 tries: 0B09B001FD2176174C770006 11/02/14 17:16:49.770 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "My-HM-CFG-LAN": Info: No response to packet after 3 tries: 0B09B001FD2176174C770006 11/02/14 17:16:51.210 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "My-HM-CFG-LAN": Info: No response to packet after 3 tries: 0B09B001FD2176174C770006 11/02/14 17:26:51.374 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "My-HM-CFG-LAN": Info: No response to packet after 3 tries: 0B0AB001FD2176174C770006 11/02/14 17:26:52.125 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "My-HM-CFG-LAN": Info: No response to packet after 3 tries: 0B0AB001FD2176174C770006 11/02/14 17:26:53.580 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "My-HM-CFG-LAN": Info: No response to packet after 3 tries: 0B0AB001FD2176174C770006 11/02/14 17:30:32.460 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "My-HM-CFG-LAN": Info: No response to packet after 3 tries: 0B08B001FD2176174C770006 11/02/14 17:30:33.130 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "My-HM-CFG-LAN": Info: No response to packet after 3 tries: 0B08B001FD2176174C770006 11/02/14 17:30:34.590 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "My-HM-CFG-LAN": Info: No response to packet after 3 tries: 0B08B001FD2176174C770006

homegear.log

11/02/14 17:23:03.530 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x3B): 0C30867019386700000000DE37
11/02/14 17:23:03.531 Info (My-HM-CFG-LAN): Packet processing took 1 ms.
11/02/14 17:23:23.600 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x3B): 0B30A25819386719DCB70000
11/02/14 17:23:23.601 Info (My-HM-CFG-LAN): Packet processing took 1 ms.
11/02/14 17:23:23.627 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x2B): 0E30820219DCB71938670101000031
11/02/14 17:23:23.628 Info (My-HM-CFG-LAN): Packet processing took 0 ms.
11/02/14 17:24:01.900 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x39): 0C88867019E34800000000D83C
11/02/14 17:24:01.901 Info (My-HM-CFG-LAN): Packet processing took 1 ms.
11/02/14 17:24:14.600 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x2F): 0C1E86701A273200000000E837
11/02/14 17:24:14.600 Info (My-HM-CFG-LAN): Packet processing took 0 ms.
11/02/14 17:24:21.870 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x38): 0B88A25819E348193D6D0000
11/02/14 17:24:21.871 Info (My-HM-CFG-LAN): Packet processing took 0 ms.
11/02/14 17:24:21.907 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x3E): 0E888202193D6D19E3480101000034
11/02/14 17:24:21.908 Info (My-HM-CFG-LAN): Packet processing took 1 ms.
11/02/14 17:24:34.670 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x30): 0B1EA2581A2732120627001E
11/02/14 17:24:34.671 Info (My-HM-CFG-LAN): Packet processing took 1 ms.
11/02/14 17:24:34.706 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x34): 0E1E82021206271A27320101180031
11/02/14 17:24:34.706 Info (My-HM-CFG-LAN): Packet processing took 0 ms.
11/02/14 17:24:42.450 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x3F): 0C5386701A25CE00000000DD3B
11/02/14 17:24:42.451 Info (My-HM-CFG-LAN): Packet processing took 1 ms.
11/02/14 17:25:02.420 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x43): 0B53A2581A25CE13A2200000
11/02/14 17:25:02.421 Info (My-HM-CFG-LAN): Packet processing took 1 ms.
11/02/14 17:25:02.449 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x3A): 0E53820213A2201A25CE0101000028
11/02/14 17:25:02.450 Info (My-HM-CFG-LAN): Packet processing took 0 ms.
11/02/14 17:25:25.150 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x3C): 0C1686701A257800000000DA3B
11/02/14 17:25:25.151 Info (My-HM-CFG-LAN): Packet processing took 1 ms.
11/02/14 17:25:40.610 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x3B): 0C31867019386700000000DE37
11/02/14 17:25:40.610 Info (My-HM-CFG-LAN): Packet processing took 0 ms.
11/02/14 17:25:45.120 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x3C): 0B16A2581A257813D2B80000
11/02/14 17:25:45.121 Info (My-HM-CFG-LAN): Packet processing took 1 ms.
11/02/14 17:25:45.215 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x38): 0E16820213D2B81A2578010100002C
11/02/14 17:25:45.216 Info (My-HM-CFG-LAN): Packet processing took 1 ms.
11/02/14 17:26:00.499 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x3B): 0B31A25819386719DCB70000
11/02/14 17:26:00.499 Info (My-HM-CFG-LAN): Packet processing took 0 ms.
11/02/14 17:26:05.600 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x35): 0C89867019E34800000000D83C
11/02/14 17:26:05.601 Info (My-HM-CFG-LAN): Packet processing took 1 ms.
11/02/14 17:26:24.850 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x2F): 0C1F86701A273200000000E837
11/02/14 17:26:24.851 Info (My-HM-CFG-LAN): Packet processing took 1 ms.
11/02/14 17:26:25.570 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x3B): 0B89A25819E348193D6D0000
11/02/14 17:26:25.570 Info (My-HM-CFG-LAN): Packet processing took 0 ms.
11/02/14 17:26:25.675 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x3E): 0E898202193D6D19E3480101000039
11/02/14 17:26:25.676 Info (My-HM-CFG-LAN): Packet processing took 1 ms.
11/02/14 17:26:44.920 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x2F): 0B1FA2581A273213D31F001E
11/02/14 17:26:44.921 Info (My-HM-CFG-LAN): Packet processing took 1 ms.
11/02/14 17:26:44.956 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x24): 0E1F820213D31F1A2732010118003C
11/02/14 17:26:44.956 Info (My-HM-CFG-LAN): Packet processing took 0 ms.
11/02/14 17:26:48.911 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "My-HM-CFG-LAN": Info: Sending (My-HM-CFG-LAN): 0B0AB001FD2176174C770006
11/02/14 17:26:49.914 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "My-HM-CFG-LAN": Info: Sending (My-HM-CFG-LAN): 0B0AB001FD2176174C770006
11/02/14 17:26:50.917 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "My-HM-CFG-LAN": Info: Sending (My-HM-CFG-LAN): 0B0AB001FD2176174C770006
11/02/14 17:26:51.373 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "My-HM-CFG-LAN": Info: No response to packet after 3 tries: 0B0AB001FD2176174C770006
11/02/14 17:26:52.026 Info: CLI connection accepted. Client number: 191
11/02/14 17:26:52.125 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "My-HM-CFG-LAN": Info: No response to packet after 3 tries: 0B0AB001FD2176174C770006
11/02/14 17:26:52.350 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x42): 0C5486701A25CE00000000DD3B
11/02/14 17:26:52.351 Info (My-HM-CFG-LAN): Packet processing took 1 ms.
11/02/14 17:26:53.580 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "My-HM-CFG-LAN": Info: No response to packet after 3 tries: 0B0AB001FD2176174C770006
11/02/14 17:27:07.016 (Shutdown) => Stopping Homegear (Signal: 15)
11/02/14 17:27:07.016 (Shutdown) => Stopping CLI server
11/02/14 17:27:07.048 (Shutdown) => Stopping RPC servers
11/02/14 17:27:12.322 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x3F): 0B54A2581A25CE13A2200000
11/02/14 17:27:12.323 Info (My-HM-CFG-LAN): Packet processing took 0 ms.
11/02/14 17:27:12.460 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x3E): 0E54820213A2201A25CE0101000028
11/02/14 17:27:12.461 Info (My-HM-CFG-LAN): Packet processing took 0 ms.
11/02/14 17:27:14.368 (Shutdown) => Stopping Event handler
11/02/14 17:27:14.368 (Shutdown) => Stopping RPC client
11/02/14 17:27:14.368 (Shutdown) => Closing physical devices
11/02/14 17:27:17.464 (Shutdown) => Saving devices
11/02/14 17:27:17.464 (Shutdown) => Saving devices
11/02/14 17:27:17.513 (Shutdown) => Saving HomeMatic BidCoS device 1
11/02/14 17:27:17.516 Module HomeMatic BidCoS: (Shutdown) => Saving HomeMatic BidCoS peer 2 with address 0x174C77
11/02/14 17:27:17.519 Module HomeMatic BidCoS: (Shutdown) => Saving HomeMatic BidCoS peer 1 with address 0x199214
11/02/14 17:27:17.522 (Shutdown) => Saving HomeMatic BidCoS device 2
11/02/14 17:27:17.527 (Shutdown) => Disposing device families
11/02/14 17:27:24.990 Info: Disposing family module mod_philipshue.so
11/02/14 17:27:24.991 Info: Disposing family module mod_max.so
11/02/14 17:27:24.991 Info: Disposing family module mod_insteon.so
11/02/14 17:27:24.991 Info: Disposing family module mod_homematicwired.so
11/02/14 17:27:24.992 Info: Disposing family module mod_homematicbidcos.so
11/02/14 17:27:25.055 Closing database...
11/02/14 17:27:25.056 Can't execute "COMMIT": cannot commit - no transaction is active
11/02/14 17:27:25.056 (Shutdown) => Shutdown complete.
11/02/14 17:27:27.709 Info: Loading family module mod_max.so
11/02/14 17:27:27.725 Info: Loading family module mod_homematicbidcos.so
11/02/14 17:27:27.744 Info: Loading family module mod_homematicwired.so
11/02/14 17:27:27.758 Info: Loading family module mod_insteon.so
11/02/14 17:27:27.774 Info: Loading family module mod_philipshue.so
11/02/14 17:27:27.844 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "My-HM-CFG-LAN": Info: Enabling AES encryption for communication with HM-CFG-LAN.
11/02/14 17:27:27.844 Initializing database...
11/02/14 17:27:27.855 Initializing family controller...
11/02/14 17:27:27.856 Module HomeMatic BidCoS: Loading XML RPC devices...
11/02/14 17:27:28.944 Info: Not initializing device family HomeMatic Wired, bacause no physical interface was found.
11/02/14 17:27:28.944 Info: Not initializing device family INSTEON, bacause no physical interface was found.
11/02/14 17:27:28.944 Info: Not initializing device family MAX!, bacause no physical interface was found.
11/02/14 17:27:28.945 Info: Not initializing device family Philips hue, bacause no physical interface was found.
11/02/14 17:27:28.945 Loading devices...
11/02/14 17:27:28.946 Module HomeMatic BidCoS: Loading HomeMatic BidCoS device 1
11/02/14 17:27:28.948 Module HomeMatic BidCoS: Loading peer 1
11/02/14 17:27:28.962 Module HomeMatic BidCoS: Loading peer 2
11/02/14 17:27:28.972 Module HomeMatic BidCoS: Loading HomeMatic BidCoS device 2
11/02/14 17:27:28.975 Start listening for packets...
11/02/14 17:27:28.976 Initializing RPC client...
11/02/14 17:27:28.976 Starting XML RPC server RPCServer1 listening on 0.0.0.0:2001...
11/02/14 17:27:28.976 Info: Connecting to host 192.168.200.3 on port 1000...
11/02/14 17:27:28.980 Starting XML RPC server RPCServer2 listening on 0.0.0.0:2002, SSL enabled...
11/02/14 17:27:28.980 RPC Server (Port 2001): Info: RPC Server started listening on address 0.0.0.0 and port 2001
11/02/14 17:27:28.994 Info: Connected to host 192.168.200.3 on port 1000. Client number is: 0
11/02/14 17:27:28.996 Starting XML RPC server RPCServer3 listening on 0.0.0.0:2003, SSL enabled, authentification enabled...
11/02/14 17:27:28.996 RPC Server (Port 2002): Info: RPC Server started listening on address 0.0.0.0 and port 2002
11/02/14 17:27:29.011 Starting CLI server...
11/02/14 17:27:29.012 Initializing event handler...
11/02/14 17:27:29.012 RPC Server (Port 2003): Info: RPC Server started listening on address 0.0.0.0 and port 2003
11/02/14 17:27:29.012 Loading events...
11/02/14 17:27:29.013 Startup complete.
11/02/14 17:27:30.014 All physical interfaces are connected now.
11/02/14 17:27:33.358 RPC Server (Port 2001): Info: Connection from 192.168.200.35:62865 accepted. Client number: 5
11/02/14 17:27:33.360 RPC Server (Port 2001): Info: Client number 5 is calling RPC method: listBidcosInterfaces Parameters:
11/02/14 17:27:33.364 RPC Server (Port 2001): Info: Connection to client number 5 closed (3).
11/02/14 17:27:34.213 Info: CLI connection accepted. Client number: 6
11/02/14 17:27:35.102 RPC Server (Port 2001): Info: Connection from 192.168.200.35:62859 accepted. Client number: 7
11/02/14 17:27:36.963 RPC Server (Port 2001): Info: Connection from 192.168.200.35:62875 accepted. Client number: 8
11/02/14 17:27:36.966 RPC Server (Port 2001): Info: Client number 8 is calling RPC method: getServiceMessages Parameters:
11/02/14 17:27:36.982 RPC Server (Port 2001): Info: Connection to client number 8 closed (3).
11/02/14 17:27:36.985 RPC Server (Port 2001): Info: Connection to client number 7 closed (3).
11/02/14 17:27:37.254 RPC Server (Port 2001): Info: Connection from 192.168.200.35:62891 accepted. Client number: 9
11/02/14 17:27:37.254 RPC Server (Port 2001): Info: Connection from 192.168.200.35:62892 accepted. Client number: 10
11/02/14 17:27:37.255 RPC Server (Port 2001): Info: Client number 9 is calling RPC method: getServiceMessages Parameters:
11/02/14 17:27:37.257 RPC Server (Port 2001): Info: Client number 10 is calling RPC method: getServiceMessages Parameters:
11/02/14 17:27:37.269 RPC Server (Port 2001): Info: Client number 9 is calling RPC method: getDeviceDescription Parameters:
(String) IEQ0505136:0
11/02/14 17:27:37.271 RPC Server (Port 2001): Info: Connection to client number 10 closed (3).
11/02/14 17:27:37.273 RPC Server (Port 2001): Info: Client number 9 is calling RPC method: getDeviceDescription Parameters:
(String) IEQ0505136
11/02/14 17:27:37.278 RPC Server (Port 2001): Info: Client number 9 is calling RPC method: getAllMetadata Parameters:
(String) IEQ0505136
11/02/14 17:27:37.281 RPC Server (Port 2001): Info: Client number 9 is calling RPC method: getParamsetDescription Parameters:
(String) IEQ0505136:0
(String) VALUES
11/02/14 17:27:37.287 RPC Server (Port 2001): Info: Client number 9 is calling RPC method: getDeviceDescription Parameters:
(String) IEQ0505136:0
11/02/14 17:27:37.291 RPC Server (Port 2001): Info: Client number 9 is calling RPC method: getDeviceDescription Parameters:
(String) IEQ0505136
11/02/14 17:27:37.294 RPC Server (Port 2001): Info: Client number 9 is calling RPC method: getAllMetadata Parameters:
(String) IEQ0505136
11/02/14 17:27:37.301 RPC Server (Port 2001): Info: Client number 9 is calling RPC method: getParamsetDescription Parameters:
(String) IEQ0505136:0
(String) VALUES
11/02/14 17:27:37.306 RPC Server (Port 2001): Info: Connection to client number 9 closed (3).
11/02/14 17:27:38.073 RPC Server (Port 2001): Info: Connection from 192.168.200.35:62851 accepted. Client number: 11
11/02/14 17:27:38.073 RPC Server (Port 2001): Info: Connection from 192.168.200.35:62858 accepted. Client number: 12
11/02/14 17:27:38.074 RPC Server (Port 2001): Info: Client number 12 is calling RPC method: getServiceMessages Parameters:
11/02/14 17:27:38.088 RPC Server (Port 2001): Info: Connection to client number 12 closed (3).
11/02/14 17:27:38.095 RPC Server (Port 2001): Info: Connection to client number 11 closed (3).
11/02/14 17:27:38.378 RPC Server (Port 2001): Info: Connection from 192.168.200.35:62896 accepted. Client number: 13
11/02/14 17:27:38.380 RPC Server (Port 2001): Info: Client number 13 is calling RPC method: listBidcosInterfaces Parameters:
11/02/14 17:27:38.383 RPC Server (Port 2001): Info: Connection to client number 13 closed (3).
11/02/14 17:27:42.240 RPC Server (Port 2001): Info: Connection from 192.168.200.35:62911 accepted. Client number: 14
11/02/14 17:27:42.242 RPC Server (Port 2001): Info: Client number 14 is calling RPC method: getServiceMessages Parameters:
11/02/14 17:27:42.327 RPC Server (Port 2001): Info: Connection to client number 14 closed (3).
11/02/14 17:27:43.492 RPC Server (Port 2001): Info: Connection from 192.168.200.35:62913 accepted. Client number: 15
11/02/14 17:27:43.495 RPC Server (Port 2001): Info: Client number 15 is calling RPC method: listBidcosInterfaces Parameters:
11/02/14 17:27:43.499 RPC Server (Port 2001): Info: Connection to client number 15 closed (3).
11/02/14 17:27:47.193 RPC Server (Port 2001): Info: Connection from 192.168.200.35:62923 accepted. Client number: 16
11/02/14 17:27:47.196 RPC Server (Port 2001): Info: Client number 16 is calling RPC method: getServiceMessages Parameters:
11/02/14 17:27:47.209 RPC Server (Port 2001): Info: Connection to client number 16 closed (3).
11/02/14 17:27:48.612 RPC Server (Port 2001): Info: Connection from 192.168.200.35:62925 accepted. Client number: 17
11/02/14 17:27:48.614 RPC Server (Port 2001): Info: Client number 17 is calling RPC method: listBidcosInterfaces Parameters:
11/02/14 17:27:48.617 RPC Server (Port 2001): Info: Connection to client number 17 closed (3).
11/02/14 17:27:52.232 RPC Server (Port 2001): Info: Connection from 192.168.200.35:62933 accepted. Client number: 18
11/02/14 17:27:52.235 RPC Server (Port 2001): Info: Client number 18 is calling RPC method: getServiceMessages Parameters:
11/02/14 17:27:52.252 RPC Server (Port 2001): Info: Connection to client number 18 closed (3).
11/02/14 17:27:53.642 RPC Server (Port 2001): Info: Connection from 192.168.200.35:62934 accepted. Client number: 19
11/02/14 17:27:53.644 RPC Server (Port 2001): Info: Client number 19 is calling RPC method: listBidcosInterfaces Parameters:
11/02/14 17:27:53.720 RPC Server (Port 2001): Info: Connection to client number 19 closed (3).
11/02/14 17:27:57.242 RPC Server (Port 2001): Info: Connection from 192.168.200.35:62941 accepted. Client number: 20
11/02/14 17:27:57.245 RPC Server (Port 2001): Info: Client number 20 is calling RPC method: getServiceMessages Parameters:
11/02/14 17:27:57.259 RPC Server (Port 2001): Info: Connection to client number 20 closed (3).
11/02/14 17:27:58.752 RPC Server (Port 2001): Info: Connection from 192.168.200.35:62942 accepted. Client number: 21
11/02/14 17:27:58.754 RPC Server (Port 2001): Info: Client number 21 is calling RPC method: listBidcosInterfaces Parameters:
11/02/14 17:27:58.827 RPC Server (Port 2001): Info: Connection to client number 21 closed (3).
11/02/14 17:28:00.850 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x3B): 0C1786701A257800000000DA3B
11/02/14 17:28:00.851 Info (My-HM-CFG-LAN): Packet processing took 1 ms.
11/02/14 17:28:02.242 RPC Server (Port 2001): Info: Connection from 192.168.200.35:62949 accepted. Client number: 22
11/02/14 17:28:02.244 RPC Server (Port 2001): Info: Client number 22 is calling RPC method: getServiceMessages Parameters:
11/02/14 17:28:02.258 RPC Server (Port 2001): Info: Connection to client number 22 closed (3).
11/02/14 17:28:03.250 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x3C): 0C32867019386700000000DE37
11/02/14 17:28:03.251 Info (My-HM-CFG-LAN): Packet processing took 1 ms.
11/02/14 17:28:03.847 RPC Server (Port 2001): Info: Connection from 192.168.200.35:62950 accepted. Client number: 23
11/02/14 17:28:03.848 RPC Server (Port 2001): Info: Client number 23 is calling RPC method: listBidcosInterfaces Parameters:
11/02/14 17:28:03.854 RPC Server (Port 2001): Info: Connection to client number 23 closed (3).
11/02/14 17:28:06.895 RPC Server (Port 2001): Info: Connection from 192.168.200.35:62959 accepted. Client number: 24
11/02/14 17:28:06.897 RPC Server (Port 2001): Info: Client number 24 is calling RPC method: listBidcosInterfaces Parameters:
11/02/14 17:28:06.902 RPC Server (Port 2001): Info: Connection to client number 24 closed (3).
11/02/14 17:28:07.986 RPC Server (Port 2001): Info: Connection from 192.168.200.35:62975 accepted. Client number: 25
11/02/14 17:28:07.989 RPC Server (Port 2001): Info: Client number 25 is calling RPC method: listBidcosInterfaces Parameters:
11/02/14 17:28:07.995 RPC Server (Port 2001): Info: Client number 25 is calling RPC method: listDevices Parameters:
(Boolean) 0
11/02/14 17:28:07.999 RPC Server (Port 2001): Info: Connection from 192.168.200.35:62976 accepted. Client number: 26
11/02/14 17:28:08.001 RPC Server (Port 2001): Info: Client number 26 is calling RPC method: getServiceMessages Parameters:
11/02/14 17:28:08.012 RPC Server (Port 2001): Info: Client number 25 is calling RPC method: getAllMetadata Parameters:
(String) JEQ0054923
11/02/14 17:28:08.014 RPC Server (Port 2001): Info: Connection to client number 26 closed (3).
11/02/14 17:28:08.024 RPC Server (Port 2001): Info: Client number 25 is calling RPC method: getAllMetadata Parameters:
(String) IEQ0505136
11/02/14 17:28:08.029 RPC Server (Port 2001): Info: Connection to client number 25 closed (3).
11/02/14 17:28:10.393 RPC Server (Port 2001): Info: Connection from 192.168.200.35:62980 accepted. Client number: 27
11/02/14 17:28:10.394 RPC Server (Port 2001): Info: Client number 27 is calling RPC method: getServiceMessages Parameters:
11/02/14 17:28:10.415 RPC Server (Port 2001): Info: Client number 27 is calling RPC method: getDeviceDescription Parameters:
(String) IEQ0505136:0
11/02/14 17:28:10.419 RPC Server (Port 2001): Info: Client number 27 is calling RPC method: getDeviceDescription Parameters:
(String) IEQ0505136
11/02/14 17:28:10.423 RPC Server (Port 2001): Info: Client number 27 is calling RPC method: getAllMetadata Parameters:
(String) IEQ0505136
11/02/14 17:28:10.427 RPC Server (Port 2001): Info: Client number 27 is calling RPC method: getParamsetDescription Parameters:
(String) IEQ0505136:0
(String) VALUES
11/02/14 17:28:10.431 RPC Server (Port 2001): Info: Client number 27 is calling RPC method: getDeviceDescription Parameters:
(String) IEQ0505136:0
11/02/14 17:28:10.434 RPC Server (Port 2001): Info: Client number 27 is calling RPC method: getDeviceDescription Parameters:
(String) IEQ0505136
11/02/14 17:28:10.438 RPC Server (Port 2001): Info: Client number 27 is calling RPC method: getAllMetadata Parameters:
(String) IEQ0505136
11/02/14 17:28:10.442 RPC Server (Port 2001): Info: Client number 27 is calling RPC method: getParamsetDescription Parameters:
(String) IEQ0505136:0
(String) VALUES
11/02/14 17:28:10.446 RPC Server (Port 2001): Info: Connection to client number 27 closed (3).
11/02/14 17:28:11.907 RPC Server (Port 2001): Info: Connection from 192.168.200.35:62981 accepted. Client number: 28
11/02/14 17:28:11.909 RPC Server (Port 2001): Info: Client number 28 is calling RPC method: listBidcosInterfaces Parameters:
11/02/14 17:28:11.913 RPC Server (Port 2001): Info: Connection to client number 28 closed (3).
11/02/14 17:28:13.143 RPC Server (Port 2001): Info: Connection from 192.168.200.35:62988 accepted. Client number: 29
11/02/14 17:28:13.144 RPC Server (Port 2001): Info: Client number 29 is calling RPC method: getServiceMessages Parameters:
11/02/14 17:28:13.159 RPC Server (Port 2001): Info: Connection to client number 29 closed (3).
11/02/14 17:28:14.933 RPC Server (Port 2001): Info: Connection from 192.168.200.35:62992 accepted. Client number: 30
11/02/14 17:28:14.935 RPC Server (Port 2001): Info: Client number 30 is calling RPC method: getParamsetDescription Parameters:
(String) IEQ0505136:0
(String) VALUES
11/02/14 17:28:14.943 RPC Server (Port 2001): Info: Client number 30 is calling RPC method: setValue Parameters:
(String) IEQ0505136:0
(String) STICKY_UNREACH
(Boolean) 0
11/02/14 17:28:14.948 RPC Server (Port 2001): Info: Connection to client number 30 closed (3).
11/02/14 17:28:16.988 RPC Server (Port 2001): Info: Connection from 192.168.200.35:62993 accepted. Client number: 31
11/02/14 17:28:16.990 RPC Server (Port 2001): Info: Client number 31 is calling RPC method: listBidcosInterfaces Parameters:
11/02/14 17:28:16.993 RPC Server (Port 2001): Info: Connection to client number 31 closed (3).
11/02/14 17:28:18.213 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63000 accepted. Client number: 32
11/02/14 17:28:18.215 RPC Server (Port 2001): Info: Client number 32 is calling RPC method: getServiceMessages Parameters:
11/02/14 17:28:18.230 RPC Server (Port 2001): Info: Connection to client number 32 closed (3).
11/02/14 17:28:18.348 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63004 accepted. Client number: 33
11/02/14 17:28:18.351 RPC Server (Port 2001): Info: Client number 33 is calling RPC method: getServiceMessages Parameters:
11/02/14 17:28:18.365 RPC Server (Port 2001): Info: Client number 33 is calling RPC method: getDeviceDescription Parameters:
(String) IEQ0505136:0
11/02/14 17:28:18.369 RPC Server (Port 2001): Info: Client number 33 is calling RPC method: getDeviceDescription Parameters:
(String) IEQ0505136
11/02/14 17:28:18.375 RPC Server (Port 2001): Info: Client number 33 is calling RPC method: getAllMetadata Parameters:
(String) IEQ0505136
11/02/14 17:28:18.379 RPC Server (Port 2001): Info: Client number 33 is calling RPC method: getParamsetDescription Parameters:
(String) IEQ0505136:0
(String) VALUES
11/02/14 17:28:18.384 RPC Server (Port 2001): Info: Connection to client number 33 closed (3).
11/02/14 17:28:20.870 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x3A): 0B17A2581A257813D2B80000
11/02/14 17:28:20.871 Info (My-HM-CFG-LAN): Packet processing took 1 ms.
11/02/14 17:28:20.975 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x38): 0E17820213D2B81A2578010100002C
11/02/14 17:28:20.976 Info (My-HM-CFG-LAN): Packet processing took 1 ms.
11/02/14 17:28:22.102 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63005 accepted. Client number: 34
11/02/14 17:28:22.104 RPC Server (Port 2001): Info: Client number 34 is calling RPC method: listBidcosInterfaces Parameters:
11/02/14 17:28:22.177 RPC Server (Port 2001): Info: Connection to client number 34 closed (3).
11/02/14 17:28:23.233 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63012 accepted. Client number: 35
11/02/14 17:28:23.234 RPC Server (Port 2001): Info: Client number 35 is calling RPC method: getServiceMessages Parameters:
11/02/14 17:28:23.235 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x3A): 0B32A25819386719DCB70000
11/02/14 17:28:23.235 Info (My-HM-CFG-LAN): Packet processing took 0 ms.
11/02/14 17:28:23.248 RPC Server (Port 2001): Info: Connection to client number 35 closed (3).
11/02/14 17:28:23.381 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x2C): 0E32820219DCB71938670101000031
11/02/14 17:28:23.381 Info (My-HM-CFG-LAN): Packet processing took 0 ms.
11/02/14 17:28:27.223 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63013 accepted. Client number: 36
11/02/14 17:28:27.225 RPC Server (Port 2001): Info: Client number 36 is calling RPC method: listBidcosInterfaces Parameters:
11/02/14 17:28:27.297 RPC Server (Port 2001): Info: Connection to client number 36 closed (3).
11/02/14 17:28:28.242 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63020 accepted. Client number: 37
11/02/14 17:28:28.244 RPC Server (Port 2001): Info: Client number 37 is calling RPC method: getServiceMessages Parameters:
11/02/14 17:28:28.258 RPC Server (Port 2001): Info: Connection to client number 37 closed (3).
11/02/14 17:28:32.342 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63021 accepted. Client number: 38
11/02/14 17:28:32.344 RPC Server (Port 2001): Info: Client number 38 is calling RPC method: listBidcosInterfaces Parameters:
11/02/14 17:28:32.416 RPC Server (Port 2001): Info: Connection to client number 38 closed (3).
11/02/14 17:28:33.262 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63028 accepted. Client number: 39
11/02/14 17:28:33.265 RPC Server (Port 2001): Info: Client number 39 is calling RPC method: getServiceMessages Parameters:
11/02/14 17:28:33.279 RPC Server (Port 2001): Info: Connection to client number 39 closed (3).
11/02/14 17:28:37.514 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63029 accepted. Client number: 40
11/02/14 17:28:37.514 RPC Server (Port 2001): Info: Client number 40 is calling RPC method: listBidcosInterfaces Parameters:
11/02/14 17:28:37.587 RPC Server (Port 2001): Info: Connection to client number 40 closed (3).
11/02/14 17:28:38.282 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63036 accepted. Client number: 41
11/02/14 17:28:38.285 RPC Server (Port 2001): Info: Client number 41 is calling RPC method: getServiceMessages Parameters:
11/02/14 17:28:38.300 RPC Server (Port 2001): Info: Connection to client number 41 closed (3).
11/02/14 17:28:42.682 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63037 accepted. Client number: 42
11/02/14 17:28:42.685 RPC Server (Port 2001): Info: Client number 42 is calling RPC method: listBidcosInterfaces Parameters:
11/02/14 17:28:42.794 RPC Server (Port 2001): Info: Connection to client number 42 closed (3).
11/02/14 17:28:43.303 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63044 accepted. Client number: 43
11/02/14 17:28:43.305 RPC Server (Port 2001): Info: Client number 43 is calling RPC method: getServiceMessages Parameters:
11/02/14 17:28:43.318 RPC Server (Port 2001): Info: Connection to client number 43 closed (3).
11/02/14 17:28:47.787 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63048 accepted. Client number: 44
11/02/14 17:28:47.789 RPC Server (Port 2001): Info: Client number 44 is calling RPC method: listBidcosInterfaces Parameters:
11/02/14 17:28:47.866 RPC Server (Port 2001): Info: Connection to client number 44 closed (3).
11/02/14 17:28:48.195 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63052 accepted. Client number: 45
11/02/14 17:28:48.197 RPC Server (Port 2001): Info: Client number 45 is calling RPC method: getServiceMessages Parameters:
11/02/14 17:28:48.211 RPC Server (Port 2001): Info: Connection to client number 45 closed (3).
11/02/14 17:28:52.882 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63056 accepted. Client number: 46
11/02/14 17:28:52.884 RPC Server (Port 2001): Info: Client number 46 is calling RPC method: listBidcosInterfaces Parameters:
11/02/14 17:28:52.957 RPC Server (Port 2001): Info: Connection to client number 46 closed (3).
11/02/14 17:28:53.203 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63060 accepted. Client number: 47
11/02/14 17:28:53.206 RPC Server (Port 2001): Info: Client number 47 is calling RPC method: getServiceMessages Parameters:
11/02/14 17:28:53.220 RPC Server (Port 2001): Info: Connection to client number 47 closed (3).
11/02/14 17:28:58.042 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63064 accepted. Client number: 48
11/02/14 17:28:58.044 RPC Server (Port 2001): Info: Client number 48 is calling RPC method: listBidcosInterfaces Parameters:
11/02/14 17:28:58.047 RPC Server (Port 2001): Info: Connection to client number 48 closed (3).
11/02/14 17:28:58.193 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63068 accepted. Client number: 49
11/02/14 17:28:58.196 RPC Server (Port 2001): Info: Client number 49 is calling RPC method: getServiceMessages Parameters:
11/02/14 17:28:58.210 RPC Server (Port 2001): Info: Connection to client number 49 closed (3).
11/02/14 17:28:58.800 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x3C): 0C8A867019E34800000000DA3C
11/02/14 17:28:58.801 Info (My-HM-CFG-LAN): Packet processing took 1 ms.
11/02/14 17:29:03.163 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63072 accepted. Client number: 50
11/02/14 17:29:03.166 RPC Server (Port 2001): Info: Client number 50 is calling RPC method: listBidcosInterfaces Parameters:
11/02/14 17:29:03.197 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63076 accepted. Client number: 51
11/02/14 17:29:03.213 RPC Server (Port 2001): Info: Client number 51 is calling RPC method: getServiceMessages Parameters:
11/02/14 17:29:03.226 RPC Server (Port 2001): Info: Connection to client number 51 closed (3).
11/02/14 17:29:03.229 RPC Server (Port 2001): Info: Connection to client number 50 closed (3).
11/02/14 17:29:08.282 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63083 accepted. Client number: 52
11/02/14 17:29:08.283 RPC Server (Port 2001): Info: Client number 52 is calling RPC method: listBidcosInterfaces Parameters:
11/02/14 17:29:08.284 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63084 accepted. Client number: 53
11/02/14 17:29:08.285 RPC Server (Port 2001): Info: Client number 53 is calling RPC method: getServiceMessages Parameters:
11/02/14 17:29:08.286 RPC Server (Port 2001): Info: Connection to client number 52 closed (3).
11/02/14 17:29:08.297 RPC Server (Port 2001): Info: Connection to client number 53 closed (3).
11/02/14 17:29:13.303 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63091 accepted. Client number: 54
11/02/14 17:29:13.303 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63092 accepted. Client number: 55
11/02/14 17:29:13.304 RPC Server (Port 2001): Info: Client number 55 is calling RPC method: listBidcosInterfaces Parameters:
11/02/14 17:29:13.305 RPC Server (Port 2001): Info: Client number 54 is calling RPC method: getServiceMessages Parameters:
11/02/14 17:29:13.307 RPC Server (Port 2001): Info: Connection to client number 55 closed (3).
11/02/14 17:29:13.317 RPC Server (Port 2001): Info: Connection to client number 54 closed (3).
11/02/14 17:29:18.323 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63099 accepted. Client number: 56
11/02/14 17:29:18.328 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63100 accepted. Client number: 57
11/02/14 17:29:18.328 RPC Server (Port 2001): Info: Client number 56 is calling RPC method: getServiceMessages Parameters:
11/02/14 17:29:18.330 RPC Server (Port 2001): Info: Client number 57 is calling RPC method: listBidcosInterfaces Parameters:
11/02/14 17:29:18.334 RPC Server (Port 2001): Info: Connection to client number 57 closed (3).
11/02/14 17:29:18.344 RPC Server (Port 2001): Info: Connection to client number 56 closed (3).
11/02/14 17:29:18.790 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x3C): 0B8AA25819E348193D6D0000
11/02/14 17:29:18.791 Info (My-HM-CFG-LAN): Packet processing took 1 ms.
11/02/14 17:29:18.920 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x3E): 0E8A8202193D6D19E3480101000034
11/02/14 17:29:18.921 Info (My-HM-CFG-LAN): Packet processing took 1 ms.
11/02/14 17:29:23.242 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63107 accepted. Client number: 58
11/02/14 17:29:23.245 RPC Server (Port 2001): Info: Client number 58 is calling RPC method: getServiceMessages Parameters:
11/02/14 17:29:23.259 RPC Server (Port 2001): Info: Connection to client number 58 closed (3).
11/02/14 17:29:23.348 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63108 accepted. Client number: 59
11/02/14 17:29:23.350 RPC Server (Port 2001): Info: Client number 59 is calling RPC method: listBidcosInterfaces Parameters:
11/02/14 17:29:23.427 RPC Server (Port 2001): Info: Connection to client number 59 closed (3).
11/02/14 17:29:24.590 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x30): 0C2086701A273200000000E737
11/02/14 17:29:24.591 Info (My-HM-CFG-LAN): Packet processing took 1 ms.
11/02/14 17:29:28.242 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63115 accepted. Client number: 60
11/02/14 17:29:28.245 RPC Server (Port 2001): Info: Client number 60 is calling RPC method: getServiceMessages Parameters:
11/02/14 17:29:28.259 RPC Server (Port 2001): Info: Connection to client number 60 closed (3).
11/02/14 17:29:28.452 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63116 accepted. Client number: 61
11/02/14 17:29:28.455 RPC Server (Port 2001): Info: Client number 61 is calling RPC method: listBidcosInterfaces Parameters:
11/02/14 17:29:28.527 RPC Server (Port 2001): Info: Connection to client number 61 closed (3).
11/02/14 17:29:33.272 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63123 accepted. Client number: 62
11/02/14 17:29:33.275 RPC Server (Port 2001): Info: Client number 62 is calling RPC method: getServiceMessages Parameters:
11/02/14 17:29:33.290 RPC Server (Port 2001): Info: Connection to client number 62 closed (3).
11/02/14 17:29:33.542 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63124 accepted. Client number: 63
11/02/14 17:29:33.544 RPC Server (Port 2001): Info: Client number 63 is calling RPC method: listBidcosInterfaces Parameters:
11/02/14 17:29:33.617 RPC Server (Port 2001): Info: Connection to client number 63 closed (3).
11/02/14 17:29:38.253 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63132 accepted. Client number: 64
11/02/14 17:29:38.255 RPC Server (Port 2001): Info: Client number 64 is calling RPC method: getServiceMessages Parameters:
11/02/14 17:29:38.270 RPC Server (Port 2001): Info: Connection to client number 64 closed (3).
11/02/14 17:29:38.632 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63133 accepted. Client number: 65
11/02/14 17:29:38.635 RPC Server (Port 2001): Info: Client number 65 is calling RPC method: listBidcosInterfaces Parameters:
11/02/14 17:29:38.707 RPC Server (Port 2001): Info: Connection to client number 65 closed (3).
11/02/14 17:29:43.303 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63140 accepted. Client number: 66
11/02/14 17:29:43.305 RPC Server (Port 2001): Info: Client number 66 is calling RPC method: getServiceMessages Parameters:
11/02/14 17:29:43.319 RPC Server (Port 2001): Info: Connection to client number 66 closed (3).
11/02/14 17:29:43.723 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63141 accepted. Client number: 67
11/02/14 17:29:43.724 RPC Server (Port 2001): Info: Client number 67 is calling RPC method: listBidcosInterfaces Parameters:
11/02/14 17:29:43.798 RPC Server (Port 2001): Info: Connection to client number 67 closed (3).
11/02/14 17:29:44.590 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x2F): 0B20A2581A2732120627031D
11/02/14 17:29:44.591 Info (My-HM-CFG-LAN): Packet processing took 1 ms.
11/02/14 17:29:44.710 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x34): 0E2082021206271A27320101182032
11/02/14 17:29:44.711 Info (My-HM-CFG-LAN): Packet processing took 0 ms.
11/02/14 17:29:48.318 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63148 accepted. Client number: 68
11/02/14 17:29:48.320 RPC Server (Port 2001): Info: Client number 68 is calling RPC method: getServiceMessages Parameters:
11/02/14 17:29:48.334 RPC Server (Port 2001): Info: Connection to client number 68 closed (3).
11/02/14 17:29:48.833 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63149 accepted. Client number: 69
11/02/14 17:29:48.835 RPC Server (Port 2001): Info: Client number 69 is calling RPC method: listBidcosInterfaces Parameters:
11/02/14 17:29:48.907 RPC Server (Port 2001): Info: Connection to client number 69 closed (3).
11/02/14 17:29:51.900 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x47): 0C5586701A25CE00000000DD3B
11/02/14 17:29:51.900 Info (My-HM-CFG-LAN): Packet processing took 0 ms.
11/02/14 17:29:53.353 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63156 accepted. Client number: 70
11/02/14 17:29:53.355 RPC Server (Port 2001): Info: Client number 70 is calling RPC method: getServiceMessages Parameters:
11/02/14 17:29:53.369 RPC Server (Port 2001): Info: Connection to client number 70 closed (3).
11/02/14 17:29:53.921 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63157 accepted. Client number: 71
11/02/14 17:29:53.968 RPC Server (Port 2001): Info: Client number 71 is calling RPC method: listBidcosInterfaces Parameters:
11/02/14 17:29:54.000 RPC Server (Port 2001): Info: Connection to client number 71 closed (3).
11/02/14 17:29:58.375 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63164 accepted. Client number: 72
11/02/14 17:29:58.378 RPC Server (Port 2001): Info: Client number 72 is calling RPC method: getServiceMessages Parameters:
11/02/14 17:29:58.392 RPC Server (Port 2001): Info: Connection to client number 72 closed (3).
11/02/14 17:29:59.072 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63165 accepted. Client number: 73
11/02/14 17:29:59.075 RPC Server (Port 2001): Info: Client number 73 is calling RPC method: listBidcosInterfaces Parameters:
11/02/14 17:29:59.147 RPC Server (Port 2001): Info: Connection to client number 73 closed (3).
11/02/14 17:30:03.373 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63172 accepted. Client number: 74
11/02/14 17:30:03.376 RPC Server (Port 2001): Info: Client number 74 is calling RPC method: getServiceMessages Parameters:
11/02/14 17:30:03.390 RPC Server (Port 2001): Info: Connection to client number 74 closed (3).
11/02/14 17:30:04.162 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63173 accepted. Client number: 75
11/02/14 17:30:04.165 RPC Server (Port 2001): Info: Client number 75 is calling RPC method: listBidcosInterfaces Parameters:
11/02/14 17:30:04.237 RPC Server (Port 2001): Info: Connection to client number 75 closed (3).
11/02/14 17:30:08.303 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63180 accepted. Client number: 76
11/02/14 17:30:08.305 RPC Server (Port 2001): Info: Client number 76 is calling RPC method: getServiceMessages Parameters:
11/02/14 17:30:08.319 RPC Server (Port 2001): Info: Connection to client number 76 closed (3).
11/02/14 17:30:09.252 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63181 accepted. Client number: 77
11/02/14 17:30:09.254 RPC Server (Port 2001): Info: Client number 77 is calling RPC method: listBidcosInterfaces Parameters:
11/02/14 17:30:09.327 RPC Server (Port 2001): Info: Connection to client number 77 closed (3).
11/02/14 17:30:11.510 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x39): 0C33867019386700000000DE37
11/02/14 17:30:11.510 Info (My-HM-CFG-LAN): Packet processing took 0 ms.
11/02/14 17:30:11.840 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x47): 0B55A2581A25CE13A2200000
11/02/14 17:30:11.841 Info (My-HM-CFG-LAN): Packet processing took 1 ms.
11/02/14 17:30:11.970 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x3F): 0E55820213A2201A25CE0101000027
11/02/14 17:30:11.970 Info (My-HM-CFG-LAN): Packet processing took 0 ms.
11/02/14 17:30:13.412 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63188 accepted. Client number: 78
11/02/14 17:30:13.415 RPC Server (Port 2001): Info: Client number 78 is calling RPC method: getServiceMessages Parameters:
11/02/14 17:30:13.429 RPC Server (Port 2001): Info: Connection to client number 78 closed (3).
11/02/14 17:30:14.433 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63189 accepted. Client number: 79
11/02/14 17:30:14.434 RPC Server (Port 2001): Info: Client number 79 is calling RPC method: listBidcosInterfaces Parameters:
11/02/14 17:30:14.507 RPC Server (Port 2001): Info: Connection to client number 79 closed (3).
11/02/14 17:30:18.333 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63196 accepted. Client number: 80
11/02/14 17:30:18.336 RPC Server (Port 2001): Info: Client number 80 is calling RPC method: getServiceMessages Parameters:
11/02/14 17:30:18.385 RPC Server (Port 2001): Info: Connection to client number 80 closed (3).
11/02/14 17:30:19.553 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63197 accepted. Client number: 81
11/02/14 17:30:19.555 RPC Server (Port 2001): Info: Client number 81 is calling RPC method: listBidcosInterfaces Parameters:
11/02/14 17:30:19.627 RPC Server (Port 2001): Info: Connection to client number 81 closed (3).
11/02/14 17:30:22.110 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x3B): 0C1886701A257800000000DA3B
11/02/14 17:30:22.111 Info (My-HM-CFG-LAN): Packet processing took 1 ms.
11/02/14 17:30:23.343 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63204 accepted. Client number: 82
11/02/14 17:30:23.345 RPC Server (Port 2001): Info: Client number 82 is calling RPC method: getServiceMessages Parameters:
11/02/14 17:30:23.360 RPC Server (Port 2001): Info: Connection to client number 82 closed (3).
11/02/14 17:30:24.643 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63205 accepted. Client number: 83
11/02/14 17:30:24.645 RPC Server (Port 2001): Info: Client number 83 is calling RPC method: listBidcosInterfaces Parameters:
11/02/14 17:30:24.717 RPC Server (Port 2001): Info: Connection to client number 83 closed (3).
11/02/14 17:30:28.363 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63212 accepted. Client number: 84
11/02/14 17:30:28.366 RPC Server (Port 2001): Info: Client number 84 is calling RPC method: getServiceMessages Parameters:
11/02/14 17:30:28.380 RPC Server (Port 2001): Info: Connection to client number 84 closed (3).
11/02/14 17:30:29.804 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63213 accepted. Client number: 85
11/02/14 17:30:29.806 RPC Server (Port 2001): Info: Client number 85 is calling RPC method: listBidcosInterfaces Parameters:
11/02/14 17:30:29.878 RPC Server (Port 2001): Info: Connection to client number 85 closed (3).
11/02/14 17:30:29.915 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "My-HM-CFG-LAN": Info: Sending (My-HM-CFG-LAN): 0B08B001FD2176174C770006
11/02/14 17:30:30.918 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "My-HM-CFG-LAN": Info: Sending (My-HM-CFG-LAN): 0B08B001FD2176174C770006
11/02/14 17:30:31.920 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "My-HM-CFG-LAN": Info: Sending (My-HM-CFG-LAN): 0B08B001FD2176174C770006
11/02/14 17:30:32.460 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "My-HM-CFG-LAN": Info: No response to packet after 3 tries: 0B08B001FD2176174C770006
11/02/14 17:30:33.130 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "My-HM-CFG-LAN": Info: No response to packet after 3 tries: 0B08B001FD2176174C770006
11/02/14 17:30:33.322 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63220 accepted. Client number: 86
11/02/14 17:30:33.325 RPC Server (Port 2001): Info: Client number 86 is calling RPC method: getServiceMessages Parameters:
11/02/14 17:30:33.340 RPC Server (Port 2001): Info: Connection to client number 86 closed (3).
11/02/14 17:30:34.590 Module HomeMatic BidCoS: LAN-Konfigurationsadapter "My-HM-CFG-LAN": Info: No response to packet after 3 tries: 0B08B001FD2176174C770006
11/02/14 17:30:34.896 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63221 accepted. Client number: 87
11/02/14 17:30:34.897 RPC Server (Port 2001): Info: Client number 87 is calling RPC method: listBidcosInterfaces Parameters:
11/02/14 17:30:34.967 RPC Server (Port 2001): Info: Connection to client number 87 closed (3).
11/02/14 17:30:38.332 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63228 accepted. Client number: 88
11/02/14 17:30:38.334 RPC Server (Port 2001): Info: Client number 88 is calling RPC method: getServiceMessages Parameters:
11/02/14 17:30:38.349 RPC Server (Port 2001): Info: Connection to client number 88 closed (3).
11/02/14 17:30:39.985 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63229 accepted. Client number: 89
11/02/14 17:30:39.988 RPC Server (Port 2001): Info: Client number 89 is calling RPC method: listBidcosInterfaces Parameters:
11/02/14 17:30:39.991 RPC Server (Port 2001): Info: Connection to client number 89 closed (3).
11/02/14 17:30:42.100 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x3C): 0B18A2581A257813D2B80000
11/02/14 17:30:42.100 Info (My-HM-CFG-LAN): Packet processing took 0 ms.
11/02/14 17:30:42.221 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x38): 0E18820213D2B81A2578010100002C
11/02/14 17:30:42.221 Info (My-HM-CFG-LAN): Packet processing took 0 ms.
11/02/14 17:30:43.413 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63236 accepted. Client number: 90
11/02/14 17:30:43.414 RPC Server (Port 2001): Info: Client number 90 is calling RPC method: getServiceMessages Parameters:
11/02/14 17:30:43.429 RPC Server (Port 2001): Info: Connection to client number 90 closed (3).
11/02/14 17:30:45.053 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63237 accepted. Client number: 91
11/02/14 17:30:45.054 RPC Server (Port 2001): Info: Client number 91 is calling RPC method: listBidcosInterfaces Parameters:
11/02/14 17:30:45.127 RPC Server (Port 2001): Info: Connection to client number 91 closed (3).
11/02/14 17:30:48.433 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63244 accepted. Client number: 92
11/02/14 17:30:48.435 RPC Server (Port 2001): Info: Client number 92 is calling RPC method: getServiceMessages Parameters:
11/02/14 17:30:48.449 RPC Server (Port 2001): Info: Connection to client number 92 closed (3).
11/02/14 17:30:50.173 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63245 accepted. Client number: 93
11/02/14 17:30:50.175 RPC Server (Port 2001): Info: Client number 93 is calling RPC method: listBidcosInterfaces Parameters:
11/02/14 17:30:50.247 RPC Server (Port 2001): Info: Connection to client number 93 closed (3).
11/02/14 17:30:53.343 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63252 accepted. Client number: 95
11/02/14 17:30:53.345 RPC Server (Port 2001): Info: Client number 95 is calling RPC method: getServiceMessages Parameters:
11/02/14 17:30:53.359 RPC Server (Port 2001): Info: Connection to client number 95 closed (3).
11/02/14 17:30:55.263 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63253 accepted. Client number: 96
11/02/14 17:30:55.265 RPC Server (Port 2001): Info: Client number 96 is calling RPC method: listBidcosInterfaces Parameters:
11/02/14 17:30:55.337 RPC Server (Port 2001): Info: Connection to client number 96 closed (3).
11/02/14 17:30:58.462 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63260 accepted. Client number: 97
11/02/14 17:30:58.466 RPC Server (Port 2001): Info: Client number 97 is calling RPC method: getServiceMessages Parameters:
11/02/14 17:30:58.481 RPC Server (Port 2001): Info: Connection to client number 97 closed (3).
11/02/14 17:31:00.414 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63261 accepted. Client number: 98
11/02/14 17:31:00.415 RPC Server (Port 2001): Info: Client number 98 is calling RPC method: listBidcosInterfaces Parameters:
11/02/14 17:31:00.487 RPC Server (Port 2001): Info: Connection to client number 98 closed (3).
11/02/14 17:31:03.383 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63268 accepted. Client number: 99
11/02/14 17:31:03.385 RPC Server (Port 2001): Info: Client number 99 is calling RPC method: getServiceMessages Parameters:
11/02/14 17:31:03.400 RPC Server (Port 2001): Info: Connection to client number 99 closed (3).
11/02/14 17:31:05.503 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63269 accepted. Client number: 100
11/02/14 17:31:05.504 RPC Server (Port 2001): Info: Client number 100 is calling RPC method: listBidcosInterfaces Parameters:
11/02/14 17:31:05.577 RPC Server (Port 2001): Info: Connection to client number 100 closed (3).
11/02/14 17:31:08.373 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63276 accepted. Client number: 101
11/02/14 17:31:08.376 RPC Server (Port 2001): Info: Client number 101 is calling RPC method: getServiceMessages Parameters:
11/02/14 17:31:08.390 RPC Server (Port 2001): Info: Connection to client number 101 closed (3).
11/02/14 17:31:10.592 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63277 accepted. Client number: 102
11/02/14 17:31:10.594 RPC Server (Port 2001): Info: Client number 102 is calling RPC method: listBidcosInterfaces Parameters:
11/02/14 17:31:10.667 RPC Server (Port 2001): Info: Connection to client number 102 closed (3).
11/02/14 17:31:13.423 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63284 accepted. Client number: 103
11/02/14 17:31:13.425 RPC Server (Port 2001): Info: Client number 103 is calling RPC method: getServiceMessages Parameters:
11/02/14 17:31:13.440 RPC Server (Port 2001): Info: Connection to client number 103 closed (3).
11/02/14 17:31:15.693 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63285 accepted. Client number: 104
11/02/14 17:31:15.695 RPC Server (Port 2001): Info: Client number 104 is calling RPC method: listBidcosInterfaces Parameters:
11/02/14 17:31:15.767 RPC Server (Port 2001): Info: Connection to client number 104 closed (3).
11/02/14 17:31:18.403 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63292 accepted. Client number: 105
11/02/14 17:31:18.406 RPC Server (Port 2001): Info: Client number 105 is calling RPC method: getServiceMessages Parameters:
11/02/14 17:31:18.421 RPC Server (Port 2001): Info: Connection to client number 105 closed (3).
11/02/14 17:31:20.783 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63293 accepted. Client number: 106
11/02/14 17:31:20.785 RPC Server (Port 2001): Info: Client number 106 is calling RPC method: listBidcosInterfaces Parameters:
11/02/14 17:31:20.857 RPC Server (Port 2001): Info: Connection to client number 106 closed (3).
11/02/14 17:31:23.392 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63300 accepted. Client number: 107
11/02/14 17:31:23.394 RPC Server (Port 2001): Info: Client number 107 is calling RPC method: getServiceMessages Parameters:
11/02/14 17:31:23.408 RPC Server (Port 2001): Info: Connection to client number 107 closed (3).
11/02/14 17:31:25.872 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63301 accepted. Client number: 108
11/02/14 17:31:25.875 RPC Server (Port 2001): Info: Client number 108 is calling RPC method: listBidcosInterfaces Parameters:
11/02/14 17:31:25.947 RPC Server (Port 2001): Info: Connection to client number 108 closed (3).
11/02/14 17:31:28.472 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63308 accepted. Client number: 109
11/02/14 17:31:28.475 RPC Server (Port 2001): Info: Client number 109 is calling RPC method: getServiceMessages Parameters:
11/02/14 17:31:28.490 RPC Server (Port 2001): Info: Connection to client number 109 closed (3).
11/02/14 17:31:30.962 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63309 accepted. Client number: 110
11/02/14 17:31:30.969 RPC Server (Port 2001): Info: Client number 110 is calling RPC method: listBidcosInterfaces Parameters:
11/02/14 17:31:30.973 RPC Server (Port 2001): Info: Connection to client number 110 closed (3).
11/02/14 17:31:33.412 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63316 accepted. Client number: 111
11/02/14 17:31:33.415 RPC Server (Port 2001): Info: Client number 111 is calling RPC method: getServiceMessages Parameters:
11/02/14 17:31:33.430 RPC Server (Port 2001): Info: Connection to client number 111 closed (3).
11/02/14 17:31:35.992 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63317 accepted. Client number: 112
11/02/14 17:31:35.994 RPC Server (Port 2001): Info: Client number 112 is calling RPC method: listBidcosInterfaces Parameters:
11/02/14 17:31:36.070 RPC Server (Port 2001): Info: Connection to client number 112 closed (3).
11/02/14 17:31:37.790 HomeMatic BidCoS packet received (My-HM-CFG-LAN, RSSI: 0x3D): 0C8B867019E34800000000DA3C
11/02/14 17:31:37.791 Info (My-HM-CFG-LAN): Packet processing took 0 ms.
11/02/14 17:31:38.422 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63324 accepted. Client number: 113
11/02/14 17:31:38.424 RPC Server (Port 2001): Info: Client number 113 is calling RPC method: getServiceMessages Parameters:
11/02/14 17:31:38.438 RPC Server (Port 2001): Info: Connection to client number 113 closed (3).
11/02/14 17:31:41.092 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63325 accepted. Client number: 114
11/02/14 17:31:41.095 RPC Server (Port 2001): Info: Client number 114 is calling RPC method: listBidcosInterfaces Parameters:
11/02/14 17:31:41.167 RPC Server (Port 2001): Info: Connection to client number 114 closed (3).
11/02/14 17:31:43.415 RPC Server (Port 2001): Info: Connection from 192.168.200.35:63332 accepted. Client number: 115
11/02/14 17:31:43.417 RPC Server (Port 2001): Info: Client number 115 is calling RPC method: getServiceMessages Parameters:
11/02/14 17:31:43.435 RPC Server (Port 2001): Info: Connection to client number 115 closed (3).

die winmatic.xml
hab ich geändert.

mfg

sefan

[shb256]

Nachdem ich aus openhab, den befehl gesendet hab, hat er die verbindung wieder gefunden

danke.

mfg stefan

[sathya]

Hey Stefan,

es kann sein, dass die “Ping-Pakete” (wie “0B0AB001FD2176174C770006”) von der WinMatic nicht unterstützt werden. Daher können wir das erst einmal ignorieren.

Heißt das, jetzt funktioniert die WinMatic? Dann passe ich Homegear entsprechend an .

Liebe Grüße

Sathya

[shb256]

Also der letzte Test verlief positiv.
Falls es doch nochmal Probleme gibt, melde ich mich einfach.
Wenn ich am Wochenende dazu komme werde ich von der CCU auf homegear umziehen.

lg stefan

[sathya]

Hallo Stafan,

das ist ja schön . Ich habe die Änderungen bereits in Version 0.5.10 von Homegear eingebaut. Jetzt sollte die WinMatic also auf Anhieb funktionieren. Über eine kurze Rückmeldung würde ich mich freuen .

Liebe Grüße

Sathya

[gerrieg]

Hallo Sathya!

Kann es sein, dass wir beide ein Kommunikationsproblem habe? Ich meine natürlich bei BinRpc.

Stefan hat mit der Winmatic noch immer Probleme, siehe: knx-user-forum.de/openhab/38297- … nicht.html
Ich habe mich jetzt ein wenig gespielt und folgendes entdeckt:
Openhab Testitem:

Number TestDouble			"TD"   {homematic="address=KEQ0553698,channel=1,parameter=ON_TIME"}

Wenn ich via openhab den Wert auf -0.005 setze (openhab send TestDouble -0.005), sehe ich in Homegear im Logfile:

11/08/14 12:40:17.220 RPC Server (Port 2001): Debug: Packet received: 42696E000000003F0000000873657456616C756500000003000000030000000C4B4551303535333639383A3100000003000000074F4E5F54494D450000000400AE147B00000000
11/08/14 12:40:17.220 RPC Server (Port 2001): Info: Client number 78 is calling RPC method: setValue Parameters:
(String) KEQ0553698:1
(String) ON_TIME
(Float) 0.010625

Der Float Wert stimmt meiner Meinung nach nicht. Nun habe ich meine Mantisse/Exponent Berechnung geändert und habe die von Deiner Homepage verwendet, dann kommt folgendes heraus:

11/08/14 12:38:28.508 RPC Server (Port 2001): Debug: Packet received: 42696E000000003F0000000873657456616C756500000003000000030000000C4B4551303535333639383A3100000003000000074F4E5F54494D4500000004D70A3D71000000F9
11/08/14 12:38:28.508 RPC Server (Port 2001): Info: Client number 71 is calling RPC method: setValue Parameters:
(String) KEQ0553698:1
(String) ON_TIME
(Float) -5.7896e+74

Das Problem dabei, es funktioniert dann mit der CCU nicht mehr. ‘Meine’ Berechnung allerdings schon: github.com/openhab/openhab/blob … t.java#L94

Eine Idee?

LG
Gerhard

[sathya]

Hallo Gerhard,

ich habe gerade mal etwas rumgespielt. Der Float

ergibt 0x00AE147B / 0x40000000 = 0,010625. Da stimmt also tatsächlich was mit der Berechnung nicht. Komisch, dass die CCU den Wert akzeptiert… Da wäre es mal interessant zu testen, wie das Ereignis-Paket nach dem Setzen kodiert ist? Vielleicht schaut sie bei Werten außerhalb des Wertebereichs, ob Spezialwerte vorliegen und nimmt dann den Bestpassendsten? Was passiert, wenn du “-0,006” sendest?

Bei der zweiten Berechnung ist das Ergebnis fast richtig. Du hast berechnet:

Das ergibt:

Rauskommen muss aber:

Probe:

Du scheinst aus Versehen den Exponenten “-7” mit einer ein Byte großen Variablen berechnet zu haben?

Liebe Grüße

Sathya

[gerrieg]

Hallo Sathya!

Danke für den Tip mit dem Exponenten, hatte hier einen Bug bei negativen Werten. Komisch dass das bis jetzt noch nie aufgefallen ist
Stelle jetzt eine neue Version in den KNX Forum Thread.

LG
Gerhard