• 10 dec 2017: forum version update. In case of issues use this topic.
  • 30 nov 2017: pilight moved servers. In case of issues use this topic.
Hello There, Guest! Login Register


Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
pilight detect wrong protocol quigg_gt9000 is not quigg_gt1000
#1
Exclamation 
Hello,

I use a Raspberry Pi 3 with 433,92MHz receiver and sender modul.
With pilight I received codes, but the 433,92MHz socket dont switch on/off over Raspberry Pi 3.

So I search in this forum and see, that pilight get the wrong protokoll. pilight says my remote use "quigg_gt9000", but it used definitly "guigg_gt1000".

Here is a link to the thread:
Code:
forum.pilight.org/showthread.php?tid=3203&highlight=quigg_gt1000


This is one code I got with "pilight-receive" command:
Code:
{
      "message": {
              "binary": "100001000100111110110000",
              "id": 526275,
              "unit": 0,
              "state": "on"
      },
      "origin": "receiver",
      "protocol": "quigg_gt9000",
      "uuid": "0000-b8-27-eb-f4dd1e",
      "repeats": 1
}

With this code my 433,92MHz all socket's switch on:
Code:
sudo pilight-send -p quigg_gt1000 -u 0 -s -t

And with this code all socket's switch off:
Code:
sudo pilight-send -p quigg_gt1000 -u 0 -s -f

The problem is, that all sockets react to this code and in pilight with the pilight-receive command I dont get the correct "id" or/and "unit".

So I tried all "combinations" of the protocoll, but then I see maybe a BUG in pilight.
In the helpfile I see, that I can use 0 to 15 ids with the -i command. But by the id 2 or other ids I get every time the ERROR "no random code avaiable". But I dont use the "-n" command. So I dont know, what is going wrong.
Code:
pi@PCT-Pi-Test:~ $ sudo pilight-send -p quigg_gt1000 --help
Usage: pilight-send -p quigg_gt1000 [options]
        -H --help                      display this message
        -V --version                   display version
        -p --protocol=protocol         the protocol that you want to control
        -S --server=x.x.x.x            connect to server address
        -P --port=xxxx                 connect to server port
        -C --config                    config file
        -U --uuid=xxx-xx-xx-xx-xxxxxx  UUID

       [quigg_gt1000]
        -t --on        send an on signal
        -f --off       send an off signal
        -u --unit=unit control a device with this unit code [0..3]
        -i --id=id     control a device with this id [0..15]
        -a --all       control all devices with this id
        -s --super     control all devices regardless of id
        -n --num       optional use random (super)code sequence num 0..3 (7)
pi@PCT-Pi-Test:~ $ sudo pilight-send -p quigg_gt1000 -t -u 0 -i 0 -a
pi@PCT-Pi-Test:~ $ sudo pilight-send -p quigg_gt1000 -f -u 0 -i 0 -a
pi@PCT-Pi-Test:~ $ sudo pilight-send -p quigg_gt1000 -t -u 0 -i 0 -a
pi@PCT-Pi-Test:~ $ sudo pilight-send -p quigg_gt1000 -t -u 1 -i 0 -a
pi@PCT-Pi-Test:~ $ sudo pilight-send -p quigg_gt1000 -f -u 1 -i 0 -a
pi@PCT-Pi-Test:~ $ sudo pilight-send -p quigg_gt1000 -t -u 1 -i 0 -a
pi@PCT-Pi-Test:~ $ sudo pilight-send -p quigg_gt1000 -t -u 2 -i 0 -a
pi@PCT-Pi-Test:~ $ sudo pilight-send -p quigg_gt1000 -t -u 3 -i 0 -a
pi@PCT-Pi-Test:~ $ sudo pilight-send -p quigg_gt1000 -t -u 4 -i 0 -a
pi@PCT-Pi-Test:~ $ sudo pilight-send -p quigg_gt1000 -t -u 0 -i 1 -a
pi@PCT-Pi-Test:~ $ sudo pilight-send -p quigg_gt1000 -t -u 0 -i 2 -a
[Aug 12 08:31:52:822454] pilight-send: ERROR: quiggGT1000: no random code available for this switch action
pi@PCT-Pi-Test:~ $ sudo pilight-send -p quigg_gt1000 -u 0 -s -t
pi@PCT-Pi-Test:~ $ sudo pilight-send -p quigg_gt1000 -u 0 -s -f

Maybe somebody have the same problem or know a solution for my problem.

Thank you in advance!

Best regards
Pascal
 
Reply
#2
The GT-1000 protocol doesn't have receiving capabilities, so your remote will never be detected as a GT-1000 remote. Apparently, the GT-1000 protocol looks similar to the GT-9000 protocol, that does have receiving capabilities, so pilight-receive will show it as GT-9000, though in fact it isn't.

I have several GT-1000 units myself working perfectly well. The point is that, because pilight-receive cannot tell what the real id and the unit are, you have to create GT-1000 devices with an id and codes chosen by yourself (within the specified limits) end then let the sockets learn.

After successfull learning, the sockets will listen to both your remote and to pilight.  
But, because the GT-1000 protocol doesn't have receiving capabilities, pilight will never know if you have switched a socket with your remote.

This is not a bug, but is due to the fact that no one has been able to fully decode the rolling codes of the GT-1000.
 
Reply
  


Possibly Related Threads...
Thread Author Replies Views Last Post
  [Fixed] RaspberryPi4 pilight 8.1.5 - Send isn't working DominikB1993 4 68 10-18-2019, 10:25 PM
Last Post: DominikB1993
  Real 433Mhz Remote is disturbed by pilight service henne111 2 167 10-06-2019, 06:18 PM
Last Post: wo_rasp
Tongue (solved) pilight 8.1.5-1-gc0a175e0 Chrashes fleisch 5 600 10-03-2019, 01:15 PM
Last Post: fleisch
  Starting pilight on boot: "cannot bind to the SSDP multicast network" pilino1234 4 358 09-29-2019, 02:08 PM
Last Post: tomk
  pilight for Raspbian Buster (raspberry pi 4) ? starob 29 2,492 07-15-2019, 08:45 PM
Last Post: curlymo
  pilight-receive Filteroption not working Alex 2 573 07-14-2019, 08:35 AM
Last Post: Alex
  pilight usb nano format conversion ettman8 2 458 07-14-2019, 08:32 AM
Last Post: curlymo
  pilight 8.1.4 crashes after some hours Ulrich.Arnold 47 2,715 06-29-2019, 08:58 PM
Last Post: curlymo
  Raspberry PI, gpio-ir-tx and pilight not starting lordslash 5 872 06-11-2019, 05:19 PM
Last Post: curlymo
  pilight fails starting on boot Alex 5 769 06-09-2019, 06:02 PM
Last Post: curlymo

Forum Jump:


Browsing: 1 Guest(s)