Unable to pair HM-SEC-SCo

English Forums Hardware
#1

Hey Sathya,

I just got a package containing some new HM devices. Unfortunatly I see to be unable to pair the “new” HM-SEC-SCo with my Homegear Setup.

Should this be possible or is HM-SEC-SCo currenty incompatible?

Do reduce some possible problems I have disconnected my HM-CFG-LAN devices and tried it using the COC only.

Here is some logfile output that I think happened during the time I pressed the “Teach In” button.

12/11/14 17:49:50.355 HomeMatic BidCoS packet received (COC, RSSI: 0x4D): 11A1A00230A765FD09F704B2B0D16C2DB700
12/11/14 17:49:50.450 Module HomeMatic BidCoS: COC “COC”: Info: Sending (COC): 13A2A001FD09F730A765000802010AFD0B090CF7
12/11/14 17:49:50.652 Module HomeMatic BidCoS: COC “COC”: Info: Sending (COC): 13A2A001FD09F730A765000802010AFD0B090CF7
12/11/14 17:49:50.854 Module HomeMatic BidCoS: COC “COC”: Info: Sending (COC): 13A2A001FD09F730A765000802010AFD0B090CF7
12/11/14 17:49:50.933 RPC Server (Port 2001): Info: Connection from 192.168.1.111:14710 accepted. Client number: 26
12/11/14 17:49:50.935 RPC Server (Port 2001): Info: Client number 26 is calling RPC method: getServiceMessages Parameters:
12/11/14 17:49:51.056 Module HomeMatic BidCoS: COC “COC”: Info: Sending (COC): 13A2A001FD09F730A765000802010AFD0B090CF7
12/11/14 17:49:51.077 RPC Server (Port 2001): Info: Connection to client number 26 closed (3).
12/11/14 17:49:53.196 RPC Server (Port 2001): Info: Connection from 192.168.1.111:14714 accepted. Client number: 28
12/11/14 17:49:53.198 RPC Server (Port 2001): Info: Client number 28 is calling RPC method: listDevices Parameters:

The HM-SEC-SCo’s LED went yellow and then green, but the Configurator still says “No new device”.

Cheers,
Chris

#2

I have solved it myself. It seems as if eq3 configures the HM-SEC-SCo with AES on by default.

I had to pair it with my CCU2 change the AES setting to disabled. Unpair it (without factory resetting the device) and then pair it with Homegear successfully.

#3

Hey Chris,

yes AES handshakes are mandatory for the HM-Sec-SCo to work (see [1]). Actually I’m surprised it worked the way you did it, because I thought it’s always necessary for pairing :wink:. You could’ve paired it through your HM-CFG-LAN’s, too.

Regards,

Sathya

[1] https://www.homegear.eu/index.php/HomeMatic_BidCoS_Device_Support_List#Contact_Sensors

#4

I do have the same problem with paring HM-SEC-SCo.

It can be paired with the HM-CFG-LAN, but not with the CUL.

I found in this thread the hint, that it is neccessary to change from secure mode to standard.
I tried this several times, on the HM-CFG-LAN, it is now to Standard.
But if I delete there and try to register with the Homemeatic config tool on the remote RPC it is still not registering.
I have the feeling,that if I bring the device in register mode, it always default to the secure mode.

I have also an HM-SEC-SC, this is registering fine with the CUL, but I prefer the other device.
It has a standard battery and is smaller. I do need about 15 of this devices, so currently I’m just in the testing phase.

Any other proposals how to get the device registered?

#5

Hey,

if you delete it, you need AES handshakes to pair it again. To get it to work with the CUL you need to pair it using the HM-CFG-LAN, disable AES and then use the RPC function “setInterface” [1] (without unpairing it!!!) to switch to the CUL.

Cheers,

Sathya

[1] https://www.homegear.eu/index.php/SetInterface