Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
HTTP Get driver not working
#1
I am working on a remote system.  Just adding a simple IFTTT command for the HTTp Get driver.

I use the url

http://192.168.0.xxx:45821/IFTTT?cmd=xcxcxc

It learns OK and the commands are


System::GetNthToken
    P1=%(LVar:CQCActParm_2)
    P2=
    P3=1
    P4=LVar:Test

System::LogMsg
    P1=fsfsf
    P2=0
    P3=IFTTT : %(LVar:Test)....
    P4=Status


Just something really simple, get the calue assigned to cmd and put it into the logs.

For some reason it does not work.  All I get is
IFTTT : ....


For some reason its not getting the token and assigning it to the local variable.

So I tried it on my system - just copied and pasted everything - only changing the IP address for my server and it works fine and I get the value assigned to cmd in the log file.

Both systems are at version 5.3.2.

Any ideas on whats going on - what I missed?
Mykel Koblenz
Illawarra Smart Home
Reply
#2
Just log %(LVar:CQCActParm_2) itself and see what is there.
Dean Roddey
Software Geek Extraordinaire
Reply
#3
it comes up blank as well. That was one of the early tests I ran.

For some reason its not picking up the token. If i were just testing on the one system I would have put it don to user error but it work on mine so it got me confused

There is another instance of this driver on the server (different port) for Blue Iris to send commands to and its working fine
Mykel Koblenz
Illawarra Smart Home
Reply
#4
How are you sending the commands? Are you sure it's not removing or changing the query parameters in some way?
Dean Roddey
Software Geek Extraordinaire
Reply
#5
from chrome on server and firefox on my system. Sending the URL to the Blue iris driver instance is working fine so I do not have reason to believe that the query parameters are being modified in any way.

The only difference so far is that one was created on an older version and one on this version.

but that does not gel either as it works fine on my server on the same version
Mykel Koblenz
Illawarra Smart Home
Reply
#6
Put it into verbose logging and hit it again and see what shows up in the logs. It logs the incoming info. Or at least it logs what it ends up with after massaging the URL.
Dean Roddey
Software Geek Extraordinaire
Reply
#7
http://192.168.0.250:13522/IFTTT?cmd=xcxcxc&cmd2=Jhjhd

Returns

08/25 07:43:14-CQC-Server, CQCServer, CQCDrv_TestThread249
{
GenHTTPTrigS, GenHTTPTrigS_DriverImpl.cpp.519, Status/App Status
Rewritten URL is/IFTTT#xcxcxc Jhjhd
}
08/25 07:43:14-CQC-Server, CQCServer, CQCDrv_TestThread249
{
CQCIR, CQCIR_DriverBase.cpp.1105, Status/Not Found
IR receive event '/IFTTT#xcxcxc Jhjhd' was received, queuing it up for processing
}
08/25 07:43:14-CQC-Server, CQCServer, CQCDrv_TestThread249
{
CQCIR, CQCIR_DriverBase.cpp.1141, Status/Not Found
No IR receiver action was matched to incoming key '/IFTTT#xcxcxc Jhjhd'. Driver=Test
}
08/25 07:43:14-CQC-Server, CQCServer, CQCDrv_TestThread249
{
GenHTTPTrigS, GenHTTPTrigS_DriverImpl.cpp.519, Status/App Status
Rewritten URL is/favicon.ico
}
08/25 07:43:14-CQC-Server, CQCServer, CQCDrv_TestThread249
{
CQCIR, CQCIR_DriverBase.cpp.1105, Status/Not Found
IR receive event '/favicon.ico' was received, queuing it up for processing
}
08/25 07:43:14-CQC-Server, CQCServer, CQCDrv_TestThread249
{
CQCIR, CQCIR_ActionsThread.cpp.133, Status/App Status
Device Test has queued IR event 'Test' for processing
}
08/25 07:43:14-CQC-Server, CQCServer, CQCIRActThread_Test
{
CQCIR, CQCIR_ActionsThread.cpp.240, Status/App Status
Device Test is invoking IR event 'Test'
}
08/25 07:43:14-CQC-Server, CQCServer, CQCIRActThread_Test
{
CQCAct, IFTTT.0, Status/App Status
Trigger from IFTTT - CMD: . Cmd1: : 07:43:14
}
08/25 07:43:14-CQC-Server, CQCServer, CQCIRActThread_Test
{
CQCIR, CQCIR_ActionsThread.cpp.298, Status/App Status
Device Test is has completed IR event 'Test'
}
Mykel Koblenz
Illawarra Smart Home
Reply
#8
That looks correct. I'll play with it here soon and see what is going on. It was rewritten to:

/IFTTT#xcxcxc Jhjhd

The driver sets # as the divider character, so /IFTTT should be the key and then the parameters is the rest.
Dean Roddey
Software Geek Extraordinaire
Reply
#9
(08-24-2018, 02:53 PM)Dean Roddey Wrote: That looks correct. I'll play with it here soon and see what is going on. It was rewritten to:

/IFTTT#xcxcxc Jhjhd

The driver sets # as the divider character, so /IFTTT should be the key and then the parameters is the rest.

Any progress.  I have been trying ll sorts of things and just cant get the driver to pull out the parameters
Mykel Koblenz
Illawarra Smart Home
Reply
#10
I'll try to look at it today.
Dean Roddey
Software Geek Extraordinaire
Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
  "Client Side Driver Directory Could Not be Cleaned Out" TurboSam 12 233 09-20-2018, 06:08 PM
Last Post: Dean Roddey
  CML Driver IDE docs - where? rbroders 1 60 09-18-2018, 05:41 PM
Last Post: Dean Roddey
  Timer Driver Question kblagron 5 137 09-14-2018, 02:43 AM
Last Post: znelbok
  reset driver statistics? rbroders 9 349 09-11-2018, 07:50 PM
Last Post: Dean Roddey
  Driver Configuration w/8 prompts rbroders 1 264 09-03-2018, 09:28 PM
Last Post: Dean Roddey
  Driver info/stats rbroders 6 375 09-02-2018, 08:34 PM
Last Post: Dean Roddey
  Sonos Driver zra 3 208 09-01-2018, 03:09 PM
Last Post: Dean Roddey
  Can't add fields to ElkDev driver rbroders 4 307 08-07-2018, 06:24 PM
Last Post: Dean Roddey
  Http Post zra 17 857 08-05-2018, 01:55 PM
Last Post: zra
  Alexa not working Ron Haley 4 307 07-24-2018, 03:47 PM
Last Post: Dean Roddey

Forum Jump:


Users browsing this thread: 1 Guest(s)