Devices direkt per addLink() verknüpfen

rbott · October 2, 2016, 5:19pm

Hi,

ich habe einige HM-CC-RT-DN und HM-WDS40-TH-I-2 mit meiner homegear Instanz verknüpft - das tuts auch soweit. Jetzt würde ich allerdings gerne die integrierten Temperatur-Sensoren in einem der Thermostate gegen einen der Temperatur-Fühler ersetzen. Soweit ich das sehe, müsste ich mittels addLink() eine Verküpfung zwischen den beiden Peers herstellen können.

Allerdings ist mir die Sache mit den Channels nicht ganz klar - gibt es dazu irgendwo Doku bzw. kann mir das jemand in wenigen Sätzen erklären? Woher weiss ich, welchen Channel ich mit welchem Channel verheiraten muss? Auf Sender-Seite sehe ich, dass die Temperatur im Channel 1 “steckt” - aber wo muss sie hin?

Freue mich über jeden Hinweis!

sathya · October 2, 2016, 5:19pm

Hey rbott,

aktuell ist das leider noch nicht wirklich dokumentiert. Über den HomeMatic Konfigurator geht es graphisch. Ansonsten musst du dir die XML-Datei der zu verknüpfenden Geräte anschauen. In Homegear 0.6 gibt es im “Kanal” (das XML-Element heißt “Funktion”) die XML-Elemente “linkSenderFunctionTypes” und “linkReceiverFunctionTypes”. Die Elemente enthalten ID-Strings. Wenn linkSenderFunctionTypes von Gerät 1 und linkReiceiverFunctionTypes von Gerät 2 den gleichen String enthalten (z. B. WEATHER_T), lassen sich die Kanäle verknüpfen.

Viele Grüße

Sathya

avanc · October 2, 2016, 5:20pm

Hallo,

hier möchte ich nochmal nachhaken, da ich Probleme beim Linken/Peeren meines Handsenders mit der KeyMatic habe.
Der Handsender hat ja die 4 Channels für die einzelnen Tasten. Die Keymatic besitzt aber leider nur zwei Channels.

Folgender Versuch bleibt hängen:

Grüße
Sven

sathya · October 2, 2016, 5:20pm

Hallo Sven,

schick mir mal das Log zu dem Versuch.

Viele Grüße

Sathya

avanc · October 2, 2016, 5:20pm

Hm, scheint jetzt geklappt zu haben. Beim letzten Mal kam der Aufruf nie wieder zurück zu Shell

08/04/16 22:04:52.212 Info: CLI connection accepted. Client number: 15720
08/04/16 22:04:52.212 Script Engine Server: Info: Spawning new script engine process.
08/04/16 22:04:52.247 Script Engine Server: Info: Connection accepted. Client number: 15721
08/04/16 22:04:52.248 Script Engine Server: Info: Script engine process successfully spawned. Process id is 28899. Client id is: 0.
08/04/16 22:04:52.248 Script Engine Server: Info: Starting script "/var/lib/homegear/scripts/inline.php" with id 1.
08/04/16 22:04:52.250 Script Engine Server: Info: Client number 0 is calling RPC method: addLink Parameters:
(Integer) 14
(Integer) 1
(Integer) 13
(Integer) 1
08/04/16 22:04:52.250 RPC client: Info: Calling RPC method "system.multicall" on server 192.168.178.28.
08/04/16 22:04:52.251 Module HomeMatic BidCoS: Info: Parameter EXPECT_AES of peer 14 and channel 1 was set to 0x00.
08/04/16 22:04:52.251 Module HomeMatic BidCoS: Info: Parameter PEER_NEEDS_BURST of peer 14 and channel 1 was set to 0x00.
08/04/16 22:04:52.251 Module HomeMatic BidCoS: Info: Parameter EXPECT_AES of peer 14 and channel 1 was set to 0x00.
08/04/16 22:04:52.251 Module HomeMatic BidCoS: Info: Parameter PEER_NEEDS_BURST of peer 14 and channel 1 was set to 0x01.
08/04/16 22:04:52.251 Module HomeMatic BidCoS: HM-LGW "My-HM-LGW": Info: Sending (My-HM-LGW): 1055A001DEAD793AB82F00040000000000
08/04/16 22:04:53.023 Module HomeMatic BidCoS: HM-LGW "My-HM-LGW": Info: No answer to packet 1055A001DEAD793AB82F00040000000000
08/04/16 22:04:55.328 HomeMatic BidCoS packet received (My-HM-LGW, RSSI: -85 dBm): 0F728610227F350000000A30D30A0058
08/04/16 22:04:55.328 Devlog (My-HM-LGW): Getting peer for packet 0F728610227F350000000A30D30A0058.
08/04/16 22:04:55.328 Devlog (My-HM-LGW): Packet 0F728610227F350000000A30D30A0058 is now passed to _receivedPackets.set.
08/04/16 22:04:55.328 Devlog (My-HM-LGW): _receivedPackets.set finished.
08/04/16 22:04:57.259 RPC client: Info: Calling RPC method "system.multicall" on server 192.168.178.28.
08/04/16 22:04:57.259 Module HomeMatic BidCoS: Info: Parameter LONG_COND_VALUE_HI of peer 13 and channel 1 was set to 0x00.
08/04/16 22:04:57.260 Module HomeMatic BidCoS: Info: Parameter LONG_COND_VALUE_LO of peer 13 and channel 1 was set to 0x00.
08/04/16 22:04:57.260 Module HomeMatic BidCoS: Info: Parameter LONG_CT_OFF of peer 13 and channel 1 was set to 0x00.
08/04/16 22:04:57.260 Module HomeMatic BidCoS: Info: Parameter LONG_CT_ON of peer 13 and channel 1 was set to 0x00.
08/04/16 22:04:57.260 Module HomeMatic BidCoS: Info: Parameter LONG_JT_OFF of peer 13 and channel 1 was set to 0x60.
08/04/16 22:04:57.260 Module HomeMatic BidCoS: Info: Parameter LONG_JT_ON of peer 13 and channel 1 was set to 0x66.
08/04/16 22:04:57.260 Module HomeMatic BidCoS: Info: Parameter LONG_ON_TIME of peer 13 and channel 1 was set to 0xFF.
08/04/16 22:04:57.260 Module HomeMatic BidCoS: Info: Parameter SHORT_COND_VALUE_HI of peer 13 and channel 1 was set to 0x00.
08/04/16 22:04:57.260 Module HomeMatic BidCoS: Info: Parameter SHORT_COND_VALUE_LO of peer 13 and channel 1 was set to 0x00.
08/04/16 22:04:57.260 Module HomeMatic BidCoS: Info: Parameter SHORT_CT_OFF of peer 13 and channel 1 was set to 0x00.
08/04/16 22:04:57.260 Module HomeMatic BidCoS: Info: Parameter SHORT_CT_ON of peer 13 and channel 1 was set to 0x00.
08/04/16 22:04:57.260 Module HomeMatic BidCoS: Info: Parameter SHORT_JT_OFF of peer 13 and channel 1 was set to 0x60.
08/04/16 22:04:57.260 Module HomeMatic BidCoS: Info: Parameter SHORT_JT_ON of peer 13 and channel 1 was set to 0x66.
08/04/16 22:04:57.260 Module HomeMatic BidCoS: Info: Parameter SHORT_ON_TIME of peer 13 and channel 1 was set to 0xFF.
08/04/16 22:04:57.260 Module HomeMatic BidCoS: Info: Parameter UI_HINT of peer 13 and channel 1 was set to 0x00.
08/04/16 22:04:57.261 Module HomeMatic BidCoS: HM-LGW "My-HM-LGW": Info: Sending (My-HM-LGW): 1053B001DEAD793E814501013AB82F0100
08/04/16 22:04:58.032 HomeMatic BidCoS packet received (My-HM-LGW, RSSI: -41 dBm): 0E5380023E8145DEAD790007C0FA90
08/04/16 22:04:58.032 Devlog (My-HM-LGW): Getting peer for packet 0E5380023E8145DEAD790007C0FA90.
08/04/16 22:04:58.032 Devlog (My-HM-LGW): Packet 0E5380023E8145DEAD790007C0FA90 is now passed to _receivedPackets.set.
08/04/16 22:04:58.033 Devlog (My-HM-LGW): _receivedPackets.set finished.
08/04/16 22:04:58.033 RPC client: Info: Calling RPC method "system.multicall" on server 192.168.178.28.
08/04/16 22:04:58.091 Module HomeMatic BidCoS: HM-LGW "My-HM-LGW": Info: Sending (My-HM-LGW): 102AB001DEAD793E814501053AB82F0103
08/04/16 22:04:58.910 HomeMatic BidCoS packet received (My-HM-LGW, RSSI: -41 dBm): 0E2A80023E8145DEAD7900CF44C414
08/04/16 22:04:58.910 Devlog (My-HM-LGW): Getting peer for packet 0E2A80023E8145DEAD7900CF44C414.
08/04/16 22:04:58.910 Devlog (My-HM-LGW): Packet 0E2A80023E8145DEAD7900CF44C414 is now passed to _receivedPackets.set.
08/04/16 22:04:58.910 Devlog (My-HM-LGW): _receivedPackets.set finished.
08/04/16 22:04:58.969 Module HomeMatic BidCoS: HM-LGW "My-HM-LGW": Info: Sending (My-HM-LGW): 192BA001DEAD793E8145010803000400050007FF0B6683008400
08/04/16 22:04:59.431 HomeMatic BidCoS packet received (My-HM-LGW, RSSI: -41 dBm): 0E2B80023E8145DEAD790027002341
08/04/16 22:04:59.432 Devlog (My-HM-LGW): Getting peer for packet 0E2B80023E8145DEAD790027002341.
08/04/16 22:04:59.432 Devlog (My-HM-LGW): Packet 0E2B80023E8145DEAD790027002341 is now passed to _receivedPackets.set.
08/04/16 22:04:59.432 Devlog (My-HM-LGW): _receivedPackets.set finished.
08/04/16 22:04:59.490 Module HomeMatic BidCoS: HM-LGW "My-HM-LGW": Info: Sending (My-HM-LGW): 112CA001DEAD793E81450108850087FF8B66
08/04/16 22:04:59.952 HomeMatic BidCoS packet received (My-HM-LGW, RSSI: -41 dBm): 0E2C80023E8145DEAD790030EA46CA
08/04/16 22:04:59.952 Devlog (My-HM-LGW): Getting peer for packet 0E2C80023E8145DEAD790030EA46CA.
08/04/16 22:04:59.952 Devlog (My-HM-LGW): Packet 0E2C80023E8145DEAD790030EA46CA is now passed to _receivedPackets.set.
08/04/16 22:04:59.953 Devlog (My-HM-LGW): _receivedPackets.set finished.
08/04/16 22:05:00.011 Module HomeMatic BidCoS: HM-LGW "My-HM-LGW": Info: Sending (My-HM-LGW): 0B2DA001DEAD793E81450106
08/04/16 22:05:00.473 HomeMatic BidCoS packet received (My-HM-LGW, RSSI: -41 dBm): 0E2D80023E8145DEAD7900C5EDD114
08/04/16 22:05:00.473 Devlog (My-HM-LGW): Getting peer for packet 0E2D80023E8145DEAD7900C5EDD114.
08/04/16 22:05:00.473 Devlog (My-HM-LGW): Packet 0E2D80023E8145DEAD7900C5EDD114 is now passed to _receivedPackets.set.
08/04/16 22:05:00.473 Module HomeMatic BidCoS: Info: Queue 5133 is empty and there are no pending queues.
08/04/16 22:05:00.473 Devlog (My-HM-LGW): _receivedPackets.set finished.
08/04/16 22:05:01.812 RPC client: Info: Calling RPC method "system.multicall" on server 192.168.178.28.
08/04/16 22:05:02.269 Module HomeMatic BidCoS: Info: Parameter EXPECT_AES of peer 14 and channel 2 was set to 0x00.
08/04/16 22:05:02.269 Module HomeMatic BidCoS: Info: Parameter PEER_NEEDS_BURST of peer 14 and channel 2 was set to 0x00.
08/04/16 22:05:02.270 Module HomeMatic BidCoS: Info: Parameter EXPECT_AES of peer 14 and channel 2 was set to 0x00.
08/04/16 22:05:02.270 Module HomeMatic BidCoS: Info: Parameter PEER_NEEDS_BURST of peer 14 and channel 2 was set to 0x01.
08/04/16 22:05:02.271 Module HomeMatic BidCoS: HM-LGW "My-HM-LGW": Info: Sending (My-HM-LGW): 1055A001DEAD793AB82F00040000000000
08/04/16 22:05:03.044 Module HomeMatic BidCoS: HM-LGW "My-HM-LGW": Info: No answer to packet 1055A001DEAD793AB82F00040000000000
08/04/16 22:05:03.821 HomeMatic BidCoS packet received (My-HM-LGW, RSSI: -85 dBm): 0F2B8610224D9C0000000A30E80A0058
08/04/16 22:05:03.821 Devlog (My-HM-LGW): Getting peer for packet 0F2B8610224D9C0000000A30E80A0058.
08/04/16 22:05:03.821 Devlog (My-HM-LGW): Packet 0F2B8610224D9C0000000A30E80A0058 is now passed to _receivedPackets.set.
08/04/16 22:05:03.821 Devlog (My-HM-LGW): _receivedPackets.set finished.
08/04/16 22:05:07.279 RPC client: Info: Calling RPC method "system.multicall" on server 192.168.178.28.
08/04/16 22:05:07.280 Module HomeMatic BidCoS: Info: Parameter LONG_COND_VALUE_HI of peer 13 and channel 1 was set to 0x00.
08/04/16 22:05:07.280 Module HomeMatic BidCoS: Info: Parameter LONG_COND_VALUE_LO of peer 13 and channel 1 was set to 0x00.
08/04/16 22:05:07.280 Module HomeMatic BidCoS: Info: Parameter LONG_CT_OFF of peer 13 and channel 1 was set to 0x00.
08/04/16 22:05:07.280 Module HomeMatic BidCoS: Info: Parameter LONG_CT_ON of peer 13 and channel 1 was set to 0x00.
08/04/16 22:05:07.280 Module HomeMatic BidCoS: Info: Parameter LONG_JT_OFF of peer 13 and channel 1 was set to 0x60.
08/04/16 22:05:07.280 Module HomeMatic BidCoS: Info: Parameter LONG_JT_ON of peer 13 and channel 1 was set to 0x66.
08/04/16 22:05:07.280 Module HomeMatic BidCoS: Info: Parameter LONG_ON_TIME of peer 13 and channel 1 was set to 0xFF.
08/04/16 22:05:07.280 Module HomeMatic BidCoS: Info: Parameter SHORT_COND_VALUE_HI of peer 13 and channel 1 was set to 0x00.
08/04/16 22:05:07.280 Module HomeMatic BidCoS: Info: Parameter SHORT_COND_VALUE_LO of peer 13 and channel 1 was set to 0x00.
08/04/16 22:05:07.280 Module HomeMatic BidCoS: Info: Parameter SHORT_CT_OFF of peer 13 and channel 1 was set to 0x00.
08/04/16 22:05:07.280 Module HomeMatic BidCoS: Info: Parameter SHORT_CT_ON of peer 13 and channel 1 was set to 0x00.
08/04/16 22:05:07.280 Module HomeMatic BidCoS: Info: Parameter SHORT_JT_OFF of peer 13 and channel 1 was set to 0x60.
08/04/16 22:05:07.280 Module HomeMatic BidCoS: Info: Parameter SHORT_JT_ON of peer 13 and channel 1 was set to 0x66.
08/04/16 22:05:07.280 Module HomeMatic BidCoS: Info: Parameter SHORT_ON_TIME of peer 13 and channel 1 was set to 0xFF.
08/04/16 22:05:07.280 Module HomeMatic BidCoS: Info: Parameter UI_HINT of peer 13 and channel 1 was set to 0x00.
08/04/16 22:05:07.281 Module HomeMatic BidCoS: HM-LGW "My-HM-LGW": Info: Sending (My-HM-LGW): 1056B001DEAD793E814501013AB82F0200
08/04/16 22:05:08.052 HomeMatic BidCoS packet received (My-HM-LGW, RSSI: -41 dBm): 0E5680023E8145DEAD7900B8A37DC1
08/04/16 22:05:08.052 Devlog (My-HM-LGW): Getting peer for packet 0E5680023E8145DEAD7900B8A37DC1.
08/04/16 22:05:08.052 Devlog (My-HM-LGW): Packet 0E5680023E8145DEAD7900B8A37DC1 is now passed to _receivedPackets.set.
08/04/16 22:05:08.052 Devlog (My-HM-LGW): _receivedPackets.set finished.
08/04/16 22:05:08.111 Module HomeMatic BidCoS: HM-LGW "My-HM-LGW": Info: Sending (My-HM-LGW): 102EB001DEAD793E814501053AB82F0203
08/04/16 22:05:08.929 HomeMatic BidCoS packet received (My-HM-LGW, RSSI: -41 dBm): 0E2E80023E8145DEAD79004D6E8672
08/04/16 22:05:08.929 Devlog (My-HM-LGW): Getting peer for packet 0E2E80023E8145DEAD79004D6E8672.
08/04/16 22:05:08.929 Devlog (My-HM-LGW): Packet 0E2E80023E8145DEAD79004D6E8672 is now passed to _receivedPackets.set.
08/04/16 22:05:08.929 Devlog (My-HM-LGW): _receivedPackets.set finished.
08/04/16 22:05:08.988 Module HomeMatic BidCoS: HM-LGW "My-HM-LGW": Info: Sending (My-HM-LGW): 192FA001DEAD793E8145010803000400050007FF0B6683008400
08/04/16 22:05:09.450 HomeMatic BidCoS packet received (My-HM-LGW, RSSI: -41 dBm): 0E2F80023E8145DEAD7900489322AB
08/04/16 22:05:09.450 Devlog (My-HM-LGW): Getting peer for packet 0E2F80023E8145DEAD7900489322AB.
08/04/16 22:05:09.450 Devlog (My-HM-LGW): Packet 0E2F80023E8145DEAD7900489322AB is now passed to _receivedPackets.set.
08/04/16 22:05:09.450 Devlog (My-HM-LGW): _receivedPackets.set finished.
08/04/16 22:05:09.451 RPC client: Info: Calling RPC method "system.multicall" on server 192.168.178.28.
08/04/16 22:05:09.509 Module HomeMatic BidCoS: HM-LGW "My-HM-LGW": Info: Sending (My-HM-LGW): 1130A001DEAD793E81450108850087FF8B66
08/04/16 22:05:09.817 HomeMatic BidCoS packet received (My-HM-LGW, RSSI: -77 dBm): 0F168610227F270000000A30E2E50058
08/04/16 22:05:09.817 Devlog (My-HM-LGW): Getting peer for packet 0F168610227F270000000A30E2E50058.
08/04/16 22:05:09.817 Devlog (My-HM-LGW): Packet 0F168610227F270000000A30E2E50058 is now passed to _receivedPackets.set.
08/04/16 22:05:09.817 Devlog (My-HM-LGW): _receivedPackets.set finished.
08/04/16 22:05:09.970 HomeMatic BidCoS packet received (My-HM-LGW, RSSI: -41 dBm): 0E3080023E8145DEAD790045E0D27D
08/04/16 22:05:09.970 Devlog (My-HM-LGW): Getting peer for packet 0E3080023E8145DEAD790045E0D27D.
08/04/16 22:05:09.970 Devlog (My-HM-LGW): Packet 0E3080023E8145DEAD790045E0D27D is now passed to _receivedPackets.set.
08/04/16 22:05:09.970 Devlog (My-HM-LGW): _receivedPackets.set finished.
08/04/16 22:05:10.029 Module HomeMatic BidCoS: HM-LGW "My-HM-LGW": Info: Sending (My-HM-LGW): 0B31A001DEAD793E81450106
08/04/16 22:05:10.490 HomeMatic BidCoS packet received (My-HM-LGW, RSSI: -41 dBm): 0E3180023E8145DEAD79003AA7FB62
08/04/16 22:05:10.491 Devlog (My-HM-LGW): Getting peer for packet 0E3180023E8145DEAD79003AA7FB62.
08/04/16 22:05:10.491 Devlog (My-HM-LGW): Packet 0E3180023E8145DEAD79003AA7FB62 is now passed to _receivedPackets.set.
08/04/16 22:05:10.491 Module HomeMatic BidCoS: Info: Queue 5135 is empty and there are no pending queues.
08/04/16 22:05:10.491 Devlog (My-HM-LGW): _receivedPackets.set finished.
08/04/16 22:05:10.746 RPC client: Info: Calling RPC method "system.multicall" on server 192.168.178.28.
08/04/16 22:05:12.289 Info: Script with id 1 finished with exit code 0
08/04/16 22:05:26.390 HomeMatic BidCoS packet received (My-HM-LGW, RSSI: -65 dBm): 0F408610224E030000000A30DA0A0063
08/04/16 22:05:26.390 Devlog (My-HM-LGW): Getting peer for packet 0F408610224E030000000A30DA0A0063.
08/04/16 22:05:26.390 Devlog (My-HM-LGW): Packet 0F408610224E030000000A30DA0A0063 is now passed to _receivedPackets.set.
08/04/16 22:05:26.390 Devlog (My-HM-LGW): _receivedPackets.set finished.
08/04/16 22:05:32.151 HomeMatic BidCoS packet received (My-HM-LGW, RSSI: -49 dBm): 0F3886103A8AE80000000A88E70E0000
08/04/16 22:05:32.151 Devlog (My-HM-LGW): Getting peer for packet 0F3886103A8AE80000000A88E70E0000.
08/04/16 22:05:32.151 Devlog (My-HM-LGW): Packet 0F3886103A8AE80000000A88E70E0000 is now passed to checkForBestInterface.
08/04/16 22:05:32.151 Devlog (My-HM-LGW): checkForBestInterface finished.
08/04/16 22:05:32.151 Devlog (My-HM-LGW): Packet 0F3886103A8AE80000000A88E70E0000 is now passed to _receivedPackets.set.
08/04/16 22:05:32.151 Devlog (My-HM-LGW): _receivedPackets.set finished.
08/04/16 22:05:32.151 Devlog (My-HM-LGW): Packet 0F3886103A8AE80000000A88E70E0000 is now passed to the peer.
08/04/16 22:05:32.151 RPC client: Info: Calling RPC method "system.multicall" on server 192.168.178.28.
08/04/16 22:05:32.152 Module HomeMatic BidCoS: Info: ACTUAL_TEMPERATURE on channel 4 of HomeMatic BidCoS peer 7 with serial number MEQ0527581 was set to 0x00E7.
08/04/16 22:05:32.152 Module HomeMatic BidCoS: Info: BATTERY_STATE on channel 4 of HomeMatic BidCoS peer 7 with serial number MEQ0527581 was set to 0x0E.
08/04/16 22:05:32.152 Module HomeMatic BidCoS: Info: BOOST_STATE on channel 4 of HomeMatic BidCoS peer 7 with serial number MEQ0527581 was set to 0x00.
08/04/16 22:05:32.152 Module HomeMatic BidCoS: Info: CONTROL_MODE on channel 4 of HomeMatic BidCoS peer 7 with serial number MEQ0527581 was set to 0x00.
08/04/16 22:05:32.152 Module HomeMatic BidCoS: Info: FAULT_REPORTING on channel 4 of HomeMatic BidCoS peer 7 with serial number MEQ0527581 was set to 0x00.
08/04/16 22:05:32.152 Module HomeMatic BidCoS: Info: PARTY_START_TIME on channel 4 of HomeMatic BidCoS peer 7 with serial number MEQ0527581 was set to 0x00.
08/04/16 22:05:32.152 Module HomeMatic BidCoS: Info: SET_TEMPERATURE on channel 4 of HomeMatic BidCoS peer 7 with serial number MEQ0527581 was set to 0x22.
08/04/16 22:05:32.152 Module HomeMatic BidCoS: Info: VALVE_STATE on channel 4 of HomeMatic BidCoS peer 7 with serial number MEQ0527581 was set to 0x00.
08/04/16 22:05:32.153 RPC client: Info: Calling RPC method "system.multicall" on server 192.168.178.28.
08/04/16 22:05:32.374 HomeMatic BidCoS packet received (My-HM-LGW, RSSI: -24 dBm): 0CE186703194B800000000EB3B
08/04/16 22:05:32.375 Devlog (My-HM-LGW): Getting peer for packet 0CE186703194B800000000EB3B.
08/04/16 22:05:32.375 Devlog (My-HM-LGW): Packet 0CE186703194B800000000EB3B is now passed to checkForBestInterface.
08/04/16 22:05:32.375 Devlog (My-HM-LGW): checkForBestInterface finished.
08/04/16 22:05:32.375 Devlog (My-HM-LGW): Packet 0CE186703194B800000000EB3B is now passed to _receivedPackets.set.
08/04/16 22:05:32.375 Devlog (My-HM-LGW): _receivedPackets.set finished.
08/04/16 22:05:32.375 Devlog (My-HM-LGW): Packet 0CE186703194B800000000EB3B is now passed to the peer.
08/04/16 22:05:32.375 RPC client: Info: Calling RPC method "system.multicall" on server 192.168.178.28.
08/04/16 22:05:32.375 Module HomeMatic BidCoS: Info: HUMIDITY on channel 1 of HomeMatic BidCoS peer 1 with serial number LEQ1069092 was set to 0x3B.
08/04/16 22:05:32.375 Module HomeMatic BidCoS: Info: TEMPERATURE on channel 1 of HomeMatic BidCoS peer 1 with serial number LEQ1069092 was set to 0x00EB.
08/04/16 22:05:32.376 RPC client: Info: Calling RPC method "system.multicall" on server 192.168.178.28.
08/04/16 22:05:32.928 HomeMatic BidCoS packet received (My-HM-LGW, RSSI: -85 dBm): 0F3886102280F40000000A30E10B0063
08/04/16 22:05:32.928 Devlog (My-HM-LGW): Getting peer for packet 0F3886102280F40000000A30E10B0063.
08/04/16 22:05:32.928 Devlog (My-HM-LGW): Packet 0F3886102280F40000000A30E10B0063 is now passed to _receivedPackets.set.
08/04/16 22:05:32.928 Devlog (My-HM-LGW): _receivedPackets.set finished.
08/04/16 22:05:35.651 HomeMatic BidCoS packet received (My-HM-LGW, RSSI: -85 dBm): 0FD6861022834A0000000A30E80B0058
08/04/16 22:05:35.651 Devlog (My-HM-LGW): Getting peer for packet 0FD6861022834A0000000A30E80B0058.
08/04/16 22:05:35.651 Devlog (My-HM-LGW): Packet 0FD6861022834A0000000A30E80B0058 is now passed to _receivedPackets.set.
08/04/16 22:05:35.651 Devlog (My-HM-LGW): _receivedPackets.set finished.

Aber woher weiß ich denn, was der Taster jetzt macht? Muss ich Taster 2 auch wieder mit Kanal 1 pairen?

Ich hänge noch beim Verständnis, wie ich Taster 1 mit Verschließen verbinden kann, Taster 2 mit Aufschließen und Taster 3 mit Öffnen?

avanc · October 2, 2016, 5:20pm

Jetzt muss ich hier doch noch nachfragen.

Wie gesagt hat das Verlinken eines Kanals geklappt:

Eine Verlinkung von Kanal 2 mit Kanal 2 klappt aber nicht.

Eine Verlinkung von Kanal 2 Fernbedienung mit Kanal 1 Keymatic funktioniert aber wieder:

Aber jetzt habe ich ja eine unsinnige Verknüpfung, da ich nun mit zwei Tasten die Tür abschließen kann…

Wie mache ich es richtig? Oder ist die Reihenfolge wichtig, als Keymativ mit Fernbedienung verlinken, statt Fernbedienung mit Keymatic?

sathya · October 2, 2016, 5:20pm

Hallo,

tut mir leid für die späte Antwort - ich war im Urlaub und bin gerade wieder zurück . Kanal 2 der Fernbedienung mit Kanal 1 der KeyMatic zu verbinden ist schon richtig. Was beim Tastendruck passiert, wird über die Link-Konfigurationsparameter festgelegt. Am einfachsten verwendest du an dieser Stelle den HomeMatic-Konfigurator, um die richtigen Parameterwerte zu setzen.

Viele Grüße

Sathya

andio · June 24, 2018, 6:54pm

Nur mal an Rande gefragt (ich habe gerade die gleiche Herausforderung):

Gibt es keine andere Möglichkeit, außer HomeMatic-Konfigurator? Wenn ich das richtig sehe, gibt es das nur für ein Betriebssystem, und aus meiner Sicht “das falsche”. Wie macht man es auf der Shell bzw. mit Homegear Scripts?

pmayer · June 24, 2018, 8:11pm

https://ref.homegear.eu/rpc.html#addLink

Wetterstation HM-WDS100-C6-O-2

der HomeMatic-Konfigurator wird nicht mehr wirklich weiterentwickelt. Es kann durchaus sein, dass dort nicht alle Geräte unterstützt werden. Es wird sehr bald ein Homegear-Admininterface geben, mit welchem du Geräte konfigurieren kannst.

Aktuell ist das Einfachste - wie Patrik schreibt - tatsächlich die Benutzung der RPC-Funktionen. Diese kannst du direkt in der Konsole ausführen. Also für addLink z. B.:

homegear -e rc ‘$hg->addLink(<senderPeerId>, <senderKanal>, <empfängerPeerId>, <empfängerKanal>);’

Die Kanäle kannst du über die Gerätereferenz ermitteln:

https://ref.homegear.eu/device.html?directory=HomeMatic+BidCoS&file=rf_hm-wds100-c6-o-2.xml&familyLink=homematicbidcos&name=HM-WDS100-C6-O-2

Für jeden Kanal stehen unter der Überschrift die unterstützten Linktypen. Dieser Text muss für beide Kanäle der gleiche sein (einmal Sender, einmal Empfänger). Dann lassen sich die Kanäle verknüpfen. Bei Unklarheit kannst du mir auch einfach die Gerätetypen schicken und ich poste dir die Kanäle ;-).

Oder war die Frage anders gemeint @andio?

andio · June 25, 2018, 5:22am

Ja, die Frage war anders gemeint und bezog sich auf die Aussage: “Was beim Tastendruck passiert, wird über die Link-Konfigurationsparameter festgelegt.”.
Das klingt so, als ob man addLink() weitere Parameter mitgeben könnten, als nur die Channels. Damit hatte ich ja schon keinen Erfolg beim Versuch die Fernbedienung direkt mit den Rollladenaktoren zu verbinden (die Tasten waren vertauscht).
Ich hatte das o.g. Zutat so verstanden, dass man mit Homematic-Konfigurator dieses Verhalten beeinflussen kann. Wenn die Alternative addLink() ist, es aber keine anderen Parameter gibt, führt das allerdings auch zu keinem Ergebnis.