[martenjacobs]

While the work on the GT-7000 is all very great, OP was actually asking about the GT-1000, which is as far as I know not compatible with the GT-7000 protocol. More info on this is found in this thread

[wo_rasp]

I operate about a dozen GT-FSI-04a and 7008AD switches and 6 GT-7000 remote handhelds in my home.

Due to the long footer duration, the main problem with the quigg_switch/quigg_screen protocol is the receiving part, there are no limitations on the transmit part.

With quigg_switch you should be able to turn the GT-FSI-04a and the 7008AD on/off.
With quigg_screen, you should be able to dimm the output voltage of the 7008AD up/down.

A) CONFIGURATION
I am wondering a little bit that the id used is 512 (the GT-7000 should start after insertion of batteries with id 2816).
When you press the learning button on the 7008AD while transmitting a command, the 7008AD will accept the new id and the new unit code.

B) PROTOCOL
Check the number of repeated telegrams, and ensure that it is set to 4 as a minimum.

C) HARDWARE
Can you check if the pulses are present at the GPIO pin ?

[gunbaum]

I got a simple multimeter at hand, so i go against ground and gpio17 (pin11) (which is defined in wiringpi as port0) right?
i'll give it a try. OK DONE

A) yes, i cycled the ID to just test if another ID will work - but it didn't.

B) repetition is on 12 - i set it up from 10

C) i got my multimeter on "DC measure" between DATA and GROUND - while i am sending commands there is a voltage around 0,6V.

[wo_rasp]

I have tested "commit v5.0-122-g2d0354b" and it is working on my machine.

Normally, when the quigg switches are without power for an extended time, they do loose their configuration and fall back to the initial value (id=2816, Unit=0). Same with the handheld, when you remove the battery and reinsert them.

Thus "pilight-send -p quigg_switch -i 2816 -u 0 -t" should turn it on.
(And the id reported by pilight-receive by the handheld should be 2816).

[gunbaum]

thanks for the help wo_rasp. i did everything correct.
the sender was just defective, i could have gone mad with this.
thanks a lot for your help

now i'm happily switching with "pilight-send -p quigg_switch -i 576 -u 0 -t"

and the receiver does work simultaneously too.

thanks alot!

[wo_rasp]

Thanks for the feedback.

As you have the 7008AD, you should be able to use the dimmer functionality with the quigg_screen protocol as well.

[wo_rasp]

While the work on the GT-7000 is all very great, OP was actually asking about the GT-1000, which is as far as I know not compatible with the GT-7000 protocol. More info on this is found in this thread

You are right, i will consolidate the current status for the GT-1000 in the wiki.

[Luppie]

I have tested "commit v5.0-122-g2d0354b" and it is working on my machine.

Normally, when the quigg switches are without power for an extended time, they do loose their configuration and fall back to the initial value (id=2816, Unit=0). Same with the handheld, when you remove the battery and reinsert them.

Thus "pilight-send -p quigg_switch -i 2816 -u 0 -t" should turn it on.
(And the id reported by pilight-receive by the handheld should be 2816).

I found one DMV-7009S (Quigg) switch in my attic, but couldn't find my remote. Because I can perfectly use it with my pilight, I tried the default ID 2816, but no reaction. I then tought of a way to send a lot ID's to it to find out what ID it was lissening to. I used this commandline:

Code:

for NUM in `seq 2500 1 3000`; do sudo /usr/local/bin/pilight-send -p quigg_switch -i $NUM -a -t; echo $NUM; done

I chose to scan between 2500 & 3000, because the default ID (2816) is in this range. After a few minutes my switch turned on at ID 2800
Then I manualy tried the unitnumbers to find my switch was unit 5

[curlymo]

Nice! Small bash tip

Code:

for NUM in {2500..3000}; do

The bash programming language is more powerfull then you might think.

[wo_rasp]

Yes, but the assumption to search in the range of 2500 to 3000 is wrong, it is actually based on an assumption that is a bug in the driver..
I think i should rewrite the protocol, so that the default id of 12 is used and we have an consecutive set if ids: 12, 13, 14, .... 4095
As that would break all existing installations i did not do it and made that bug a feature.
2800 is actually 2292.