Winmatic in combination with cul and AES

English Forums Devices
#1

Hello,
I tried to acitivate my Winmatic with the CUL devices using the latest nightly build of version 0.6 which should allow the CUL to use AES handshake. It seems to work somehow. On top of homegear I run homematic-manager to the events and also openhab to control devices. However I can not control the windows :frowning: I checked the events in homematic-manager and realized that the Parameter LEVEL for Channel 1 is never mentioned. When I open or close the windows I can see the LEVEL of the battery on channel 2 and also the STATUS=1 (charging) which was also correct, but even if I open or close windows I can not see any LEVEL of channel 1 which should be the level of the window. This also might be the reason why I can not set the LEVEL from OpenHAB. Might this be a BUG? I deactivated the AES-Handshake in Homematic-Manager for the window also to check, but this does not work ether. The configuration however seems to be send. Any help will be appreciated :slight_smile:

#2

Hey,

I never tested the WinMatic, so there might be a bug. Can you post the log of a try to set LEVEL and opening/closing the window manually? That should help figuring out, why it doesn’t work.

Cheers,

Sathya

#3

Thanks for your quick replay. I guess I found the part in the log you are looking for. FEQ0067298 is the WInmatic:

03/01/16 14:38:01.550 RPC Server (Port 2001): Info: Connection from 127.0.0.1:52017 accepted. Client number: 64 03/01/16 14:38:01.550 RPC Server (Port 2001): Info: RPC server client id for client number 64 is: 11 03/01/16 14:38:01.551 RPC Server (Port 2001): Info: Client number 64 is calling RPC method: setValue Parameters: (String) FEQ0067298:1 (String) LEVEL (Float) 0 03/01/16 14:38:01.551 Module HomeMatic BidCoS: CUL "My-CUL": Info: Sending (My-CUL): 101FB001FD18DC11542F02040000000001 03/01/16 14:38:02.111 Module HomeMatic BidCoS: CUL "My-CUL": Info: Sending (My-CUL): 101FB001FD18DC11542F02040000000001 03/01/16 14:38:02.671 Module HomeMatic BidCoS: CUL "My-CUL": Info: Sending (My-CUL): 101FB001FD18DC11542F02040000000001 03/01/16 14:38:04.107 RPC Server (Port 2001): Info: Connection to client number 64 closed (3). 03/01/16 14:38:04.114 RPC Server (Port 2001): Info: Connection from 127.0.0.1:52019 accepted. Client number: 65 03/01/16 14:38:04.114 RPC Server (Port 2001): Info: RPC server client id for client number 65 is: 12 03/01/16 14:38:04.114 RPC Server (Port 2001): Info: Client number 65 is calling RPC method: getAllValues Parameters: 03/01/16 14:38:04.218 RPC Server (Port 2001): Info: Connection from 127.0.0.1:52020 accepted. Client number: 66 03/01/16 14:38:04.218 RPC Server (Port 2001): Info: RPC server client id for client number 66 is: 13 03/01/16 14:38:04.219 RPC Server (Port 2001): Info: Client number 66 is calling RPC method: getAllSystemVariables Parameters: 03/01/16 14:38:04.217 RPC Server (Port 2001): Info: Connection to client number 65 closed (3). 03/01/16 14:38:04.221 RPC Server (Port 2001): Info: Connection to client number 66 closed (3). 03/01/16 14:38:05.968 HomeMatic BidCoS packet received (My-CUL, RSSI: -50 dBm): 0D57A641119C15FD18DC01426580 03/01/16 14:38:05.969 RPC client: Info: Calling RPC method "system.multicall" on server localhost.

For me it looks a bit as if the devices does not react on the call, but I also get some data from the dev

03/01/16 14:40:47.246 Module HomeMatic BidCoS: Info: DIRECTION on channel 1 of HomeMatic BidCoS peer 26 with serial number FEQ0067298 was set to 0x02. 03/01/16 14:40:47.246 Module HomeMatic BidCoS: Info: ERROR on channel 1 of HomeMatic BidCoS peer 26 with serial number FEQ0067298 was set to 0x00.

and also the battery device is responding on channel 2

Hope this helps a bit. Otherwise I have a very big log-file. If you can give me more detailed information I will search for it, or send it by mail. By the way. I recognized a lot “Moin ok” in the err-log. So I would expect you nearby. I’m from Oldenburg :wink:

#4

The pairing doesn’t seem to be complete. CONFIG_PENDING is set to “true” right? Try pressing the pairing button again until CONFIG_PENDING is set to false. If that doesn’t help, open Homegear’s CLI and post me the output of:

homegear -r
fs 0
ps 26
queues info

Additionally it would be great if you could send me the log of the pairing process to identify the problem. Then type

and try setting “LEVEL” again. Does that help?

Cheers,

Sathya

#5

Hy Sathya,
there is no config pending in homegear. Here is the queues info.

Number of Pending queues: 4 Queue 1: Number of packets: 2 Packet 1 (Type: Packet): 101FB001FD18DC11542F02040000000001 Packet 2 (Type: Message): Type: 10 Queue 2: Number of packets: 4 Packet 1 (Type: Packet): 0B00A004FD18DC11542F0100 Packet 2 (Type: Message): Type: 02 Packet 3 (Type: Packet): 0B01A004FD18DC11542F0101 Packet 4 (Type: Message): Type: 02 Queue 3: Number of packets: 2 Packet 1 (Type: Packet): 0B13B011FD18DC11542F0301 Packet 2 (Type: Message): Type: 02 Queue 4: Number of packets: 2 Packet 1 (Type: Packet): 0E14B011FD18DC11542F810100FF01 Packet 2 (Type: Message): Type: 02

I will send you the missing information asap, but this might take some time.

Thanks a lot for your help!

#6

Hey,

there were pending queues. Did the “queues clear” help? The transmission of the new AES key was not successful. If you already entered “queues clear”, factory reset your WinMatic and pair it again. If not, try pressing the pairing button. Does that change the output of “queues info”? The list should be empty.

Cheers,

Sathya