[maartenh]

Hi All,

I bought a Quigg GT-1000 set with 5 GT-FSI-08 receivers. I've been trying to get them in a module for a few hours now, but can't get it too work. Switching them on and of with raw code works fine though.

I am not really a C-coders, but tried to alter the quigg switch and get that to compile and run as a module just fine. However, I can't really calculate an ID, since (grouping by two) the first digits are not always similar. I also thought that the pulse variable should be "high" pulse divided by "low" pulse, but in my case, I always get two low pulses adding up to the high pulse (1065=639+426).
Anyway, trying to make sense of it all, but I am not really succeeding :-(. Can anyone offer some advice?

Code:

QUIGG 1 ON:
time:           Sun Nov  2 10:21:02 2014
hardware:       433lirc
pulse:          14
rawlen:         50
binlen:         12
pulselen:       213

Raw code:
1065 639 426 1065 426 1065 1065 639 426 1065 1065 639 1065 639 426 1065 852 639 1065 639 852 639 426 1065 1065 639 1065 639 1065 639 426 1065 426 1065 1065 639 1065 639 1065 639 426 1065 426 1065 426 1065 426 1065 2982 7242
Binary code:
000000000000
--[RESULTS]--


QUIGG 1 OFF:
time:           Sun Nov  2 10:21:30 2014
hardware:       433lirc
pulse:          14
rawlen:         50
binlen:         12
pulselen:       214

Raw code:
1070 642 428 1070 428 1070 1070 642 1070 642 856 642 428 1070 428 1070 428 1070 428 1070 428 1070 428 1070 1070 642 428 1070 1070 642 428 1070 428 1070 428 1070 856 642 428 1070 428 1070 428 1070 428 1070 428 1070 2996 7276
Binary code:
000000000000

QUIGG 2 ON
time:           Sun Nov  2 10:32:09 2014
hardware:       433lirc
pulse:          14
rawlen:         50
binlen:         12
pulselen:       213

Raw code:
1065 639 426 1065 426 1065 1065 639 426 1065 1065 639 1065 639 426 1065 1065 639 1065 639 1065 639 426 1065 1065 639 1065 639 1065 639 426 1065 426 1065 1065 639 1065 639 1065 639 426 1065 1065 639 426 1065 426 1065 2982 7242
Binary code:
000000000000
--[RESULTS]--


QUIGG 2 OFF
time:           Sun Nov  2 10:32:49 2014
hardware:       433lirc
pulse:          14
rawlen:         50
binlen:         12
pulselen:       213

Raw code:
1065 639 426 1065 426 1065 1065 639 1065 639 1065 639 426 1065 426 1065 426 1065 426 1065 426 1065 426 1065 1065 639 426 1065 1065 639 426 1065 426 1065 426 1065 1065 639 426 1065 426 1065 1065 639 426 1065 426 1065 2982 7242
Binary code:
000000000000
--[RESULTS]--

QUIGG 3 ON
time:           Sun Nov  2 10:38:33 2014
hardware:       433lirc
pulse:          14
rawlen:         50
binlen:         12
pulselen:       213

Raw code:
1065 639 426 1065 426 1065 1065 639 426 1065 426 1065 426 1065 426 1065 426 1065 426 1065 1065 639 426 1065 1065 639 1065 639 1065 639 1065 639 1065 639 426 1065 1065 639 1065 639 1065 639 1065 639 426 1065 426 1065 2982 7242
Binary code:
000000000000
--[RESULTS]--

QUIGG 3 OFF
time:           Sun Nov  2 10:38:46 2014
hardware:       433lirc
pulse:          14
rawlen:         50
binlen:         12
pulselen:       213

Raw code:
1065 639 426 1065 426 1065 1065 639 426 1065 426 1065 426 1065 1065 639 1065 639 426 1065 1065 639 1065 639 426 1065 426 1065 426 1065 1065 639 1065 639 426 1065 1065 639 426 1065 1065 639 1065 639 426 1065 426 1065 2982 7242
Binary code:
000000000000


QUIGG 4 ON
time:           Sun Nov  2 10:42:32 2014
hardware:       433lirc
pulse:          14
rawlen:         50
binlen:         12
pulselen:       214

Raw code:
856 642 428 1070 428 1070 856 642 428 1070 428 1070 428 1070 856 642 856 642 428 1070 856 642 856 642 428 1070 428 1070 428 1070 856 642 856 642 428 1070 856 642 428 1070 428 1070 428 1070 856 642 428 1070 2996 7276
Binary code:
000000000000
--[RESULTS]--

QUIGG 4 OFF
time:           Sun Nov  2 10:42:37 2014
hardware:       433lirc
pulse:          14
rawlen:         50
binlen:         12
pulselen:       214

Raw code:
856 642 428 1070 428 1070 856 642 428 1070 856 642 856 642 428 1070 856 642 856 642 856 642 428 1070 856 642 856 642 856 642 428 1070 428 1070 856 642 856 642 856 642 428 1070 428 1070 856 642 428 1070 2996 7276
Binary code:
000000000000



QUIGG ALL ON
--[RESULTS]--

time:           Sun Nov  2 10:25:15 2014
hardware:       433lirc
pulse:          14
rawlen:         50
binlen:         12
pulselen:       214

Raw code:
856 642 428 1070 428 1070 1070 642 428 1070 1070 642 856 642 1070 642 428 1070 856 642 428 1070 1070 642 856 642 856 642 428 1070 428 1070 428 1070 428 1070 428 1070 1070 642 1070 642 428 1070 1070 642 428 1070 2996 7276
Binary code:
000000000000
--[RESULTS]--

QUIGG ALL OFF
time:           Sun Nov  2 10:25:42 2014
hardware:       433lirc
pulse:          14
rawlen:         50
binlen:         12
pulselen:       214

Raw code:
856 642 428 1070 428 1070 856 642 428 1070 856 642 856 642 428 1070 856 642 856 642 856 642 428 1070 856 642 856 642 856 642 428 1070 428 1070 856 642 856 642 856 642 856 642 428 1070 856 642 428 1070 2996 7276
Binary code:
000000000000

[curlymo]

@wo_rasp, can you look into this one?

[wo_rasp]

@wo_rasp, can you look into this one?

I will, however can only do so in early January.
Currently to me it seems to be a variant of rev_v1, it has definitely nothing in common with the QUIGG GT-7000 protocol.

[martenjacobs]

I've done some work on this device, but I can't really work it out either.
What I've found:

• Short pulses are around 500, long pulses 1000
  
• Footer is 3000 followed by 7000
  
• Only 1000,500 (1 bit) or 500,1000 (0 bit) pairs exists
  
• All commands start with 0001 on my remote, 1001 on maartenh's remote. This seems to be the System ID
  
• The last 4 bits make up the unit ID. When using the first as LSB, I find that group 1 sends int 0, groups 2 thru 4 send 2 thru 4 and 'all' sends 5
  
• This defines the first four and last four bits of 24. I was unable to find any structure in the other 16.
  
• This protocol looks very similar to the one used by a Brennenstuhl type sold by Lidl, which is covered in this thread.
  
• This is an older thread about the GT-1000
  

Here are my result set and maartenh's as well:

my result set:

Code:

1 ON    0 0 0 1 1 0 0 0 0 1 1 1 1 0 0 1 0 1 0 0 0 0 0 0
1 OFF   0 0 0 1 1 0 1 1 0 0 1 0 1 0 1 1 0 0 1 0 0 0 0 0
2 ON    0 0 0 1 0 0 1 0 1 1 0 0 1 1 0 0 1 0 1 1 0 1 0 0
2 OFF   0 0 0 1 1 0 1 1 0 0 1 0 1 0 1 1 0 0 1 0 0 1 0 0
3 ON    0 0 0 1 0 1 1 0 0 1 0 1 1 0 0 0 0 1 1 1 1 1 0 0
3 OFF   0 0 0 1 1 1 1 0 1 1 0 1 0 1 0 0 1 0 1 0 1 1 0 0
4 ON    0 0 0 1 1 0 1 1 0 0 1 0 1 0 1 1 0 0 1 0 0 0 1 0
4 OFF   0 0 0 1 0 0 1 0 1 1 0 0 1 1 0 0 1 0 1 1 0 0 1 0
ALL ON  0 0 0 1 0 1 0 0 1 0 1 0 1 1 1 1 0 0 0 1 1 0 1 0
ALL OFF 0 0 0 1 1 0 0 1 0 1 0 0 1 1 0 1 0 0 1 1 1 0 1 0

maartenh's result set:

Code:

1 ON    1 0 0 1 0 1 1 0 1 1 1 0 1 1 1 0 0 1 1 1 0 0 0 0
1 OFF   1 0 0 1 1 1 0 0 0 0 0 0 1 0 1 0 0 0 1 0 0 0 0 0
2 ON    1 0 0 1 0 1 1 0 1 1 1 0 1 1 1 0 0 1 1 1 0 1 0 0
2 OFF   1 0 0 1 1 1 0 0 0 0 0 0 1 0 1 0 0 0 1 0 0 1 0 0
3 ON    1 0 0 1 0 0 0 0 0 0 1 0 1 1 1 1 1 0 1 1 1 1 0 0
3 OFF   1 0 0 1 0 0 0 1 1 0 1 1 0 0 0 1 1 0 1 0 1 1 0 0
4 ON    1 0 0 1 0 0 0 1 1 0 1 1 0 0 0 1 1 0 1 0 0 0 1 0
4 OFF   1 0 0 1 0 1 1 0 1 1 1 0 1 1 1 0 0 1 1 1 0 0 1 0
ALL ON  1 0 0 1 0 1 1 1 0 1 0 1 1 1 0 0 0 0 0 1 1 0 1 0
ALL OFF 1 0 0 1 0 1 1 0 1 1 1 0 1 1 1 0 0 1 1 1 1 0 1 0

Marten

EDIT: posted result sets
EDIT2: added link to Brennenstuhl protocol
EDIT3: added link to older thread about GT-1000

[Niek]

As others already reported, the GT-1000 produces a rolling set of four codes for each switch. However the switches are responding to any of the their four codes in any order. In other words, the you can use just one of the four "ON" codes for a given switch to switch it on and one of the four "OFF" codes to switch it off.
I tested this using the raw protocol, but I found out that it didn't work with the raw code from pilight-debug. After experimenting with different pulslengths I found a combination that works very well: I changed all short pulses to 500, all long pulses to 1000 and the footer to 3000/7000.
Now all of my switches can be switched on and off using the raw protocol.

Of course I like to be able to control my switches from pilight, so it would be great to have a real protocol for them, but it may be very difficult, if not impossible, to find the secret for the codes of the GT-1000.

As long as we don't know the secret and thus cannot generate the codes, I am regarding the codes as device adresses, where each device has two adresses: one for ON and one for OFF.
Wouldn't it be possible to create a protocol that takes two parameters for the "id" like this?

Code:

"voorkamer": {
                        "name": "Voorkamer Lamp",
                        "protocol": [ "GT-1000_switch" ],
                        "id": [{
                                  "address_on": "F2636E"
                                  "address_off": "F9B1BE"
                        }],
                        "state": "off"
                }

where the values in the address fields are HEX representations of the 24 bits of the ON and OFF codes?
The protocol then should use the appropriate address code when processing the ON- and OFF commands.
Instead of the HEX representation it would also be possible to use the binary codes, but HEX strings are a lot shorter and a bit more readable.

[curlymo]

Can you post all codes you currently use and are working?

[Niek]

These are my working codes:

Code:

1 ON
pilight-send -p raw -c "1000 500 1000 500 1000 500 1000 500 500 1000 500 1000 1000 500 500 1000 500 1000 1000 500 1000 500 500 1000 500 1000 500 1000 1000 500 1000 500 500 1000 1000 500 1000 500 500 1000 1000 500 1000 500 500 1000 500 1000 3000 7000"
1 OFF
pilight-send -p raw -c "1000 500 1000 500 1000 500 1000 500 1000 500 500 1000 500 1000 1000 500 1000 500 500 1000 1000 500 1000 500 500 1000 500 1000 500 1000 1000 500 1000 500 500 1000 1000 500 1000 500 1000 500 1000 500 500 1000 500 1000 3000 7000"

2 ON
pilight-send -p raw -c "1000 500 1000 500 1000 500 1000 500 1000 500 500 1000 1000 500 500 1000 1000 500 500 1000 500 1000 500 1000 500 1000 1000 500 500 1000 1000 500 1000 500 1000 500 1000 500 1000 500 500 1000 1000 500 500 1000 1000 500 3000 7000"
2 OFF
pilight-send -p raw -c "1000 500 1000 500 1000 500 1000 500 500 1000 1000 500 500 1000 1000 500 500 1000 1000 500 500 1000 500 1000 1000 500 1000 500 500 1000 500 1000 1000 500 1000 500 500 1000 500 1000 500 1000 1000 500 500 1000 1000 500 3000 7000"

3 ON
pilight-send -p raw -c "1000 500 1000 500 1000 500 1000 500 500 1000 500 1000 500 1000 1000 500 500 1000 500 1000 500 1000 500 1000 500 1000 1000 500 1000 500 500 1000 500 1000 1000 500 1000 500 1000 500 1000 500 1000 500 1000 500 500 1000 3000 7000"
3 OFF
pilight-send -p raw -c "1000 500 1000 500 1000 500 1000 500 1000 500 1000 500 1000 500 500 1000 500 1000 1000 500 500 1000 1000 500 1000 500 500 1000 1000 500 1000 500 500 1000 1000 500 500 1000 1000 500 1000 500 1000 500 1000 500 500 1000 3000 7000"

4 ON
pilight-send -p raw -c "1000 500 1000 500 1000 500 1000 500 1000 500 1000 500 500 1000 500 1000 500 1000 1000 500 1000 500 1000 500 1000 500 1000 500 500 1000 1000 500 500 1000 1000 500 500 1000 500 1000 500 1000 1000 500 1000 500 1000 500 3000 7000"
4 OFF
pilight-send -p raw -c "1000 500 1000 500 1000 500 1000 500 500 1000 1000 500 1000 500 1000 500 500 1000 500 1000 1000 500 500 1000 1000 500 500 1000 500 1000 1000 500 500 1000 500 1000 500 1000 500 1000 500 1000 1000 500 1000 500 1000 500 3000 7000"

Edit: code tags added

[wo_rasp]

@Niek,

I think your proposal is something that can be implemented.
Can you please post more manufactureres details on the exact product you use (for both the switch and the remote handheld) ?

[Niek]

@wo_rasp,

The brand of the switches and remote is QUIGG, manufacured by Globaltronics GmbH.
The model of the switches is GT-FSI-08.
The model of the remote is GT-1000.

FYI, over the past few days I tried to build a protocol myself and just yesterday I got it working for my switches. Since I'm not a C programmer and a newbee with pilight, I probably have done some awful things, but I can now control my switches both from the command line and via the web GUI.
To keep it simple for myself, I implemented it with decimal "addresses" instead of hexadecimal, but the concept is working for all of my switches (I own two sets of these, with different system codes).

Code:

"huiskamer1": {
                        "protocol": [ "quigg_gt1000" ],
                        "id": [{
                                "id": 1,
                                "address_on": 15885164,
                                "address_off": 16363964
                         }],
                        "state": "off"
                }

Although the id setting in fact does nothing, I put it in as a kind of reference to the physical device.

[wo_rasp]

May be this will also be an interim solution for some other protocols (flamingo)
send from tapatalk