Blue Iris and HTTPGet

[Dean Roddey]

Stipe was having an issue using System::HTTPGet to send a URL to his Blue Iris camera's web server to send commands to it. I looked at it and I cannot figure out why it doesn't work. CQC is clearly doing the right thing, and it's sending essentially the same things as a browser does (which does work) as proven by using F12 on the brower to look at what's sending and at the final sent message of the CQC HTTP client stuff.

We connect to the server sucessfully, and send the message. But it never response and his BI system acts as though it never saw the request, no errors in its logs or anything like that.

Has anyone successfully send HTTP commands from CQC to a Blue Iris system?

The only thing I see that's different in any substantial way is that the browser takes a cookie from the BI web server, and presumably passes it back in later. Is this maybe a requirement for it to work?

[Stipe]

I was just about to post a thread as well lol. Thanks

[pinballmark]

Stipe was having an issue using System::HTTPGet to send a URL to his Blue Iris camera's web server to send commands to it. I looked at it and I cannot figure out why it doesn't work. CQC is clearly doing the right thing, and it's sending essentially the same things as a browser does (which does work) as proven by using F12 on the brower to look at what's sending and at the final sent message of the CQC HTTP client stuff.

We connect to the server sucessfully, and send the message. But it never response and his BI system acts as though it never saw the request, no errors in its logs or anything like that.

Has anyone successfully send HTTP commands from CQC to a Blue Iris system?

The only thing I see that's different in any substantial way is that the browser takes a cookie from the BI web server, and presumably passes it back in later. Is this maybe a requirement for it to work?

I purchased BI but not using actively. I'd like to test this but not familiar with the HTTP commands. If you can point me in the right direction I'll give it a try. This could help me with other devices as well.

Mark

[wuench]

Sounds like a session cookie, it is probably required to stay authenticated. That's pretty typical for GUI applications. You login, get a cookie and return that to submit further commands.

Here is the JSON API, it behaves similarly, you have to maintain a session token...

https://www.houselogix.com/docs/blue-iri...s/json.htm

[Stipe]

I purchased BI but not using actively. I'd like to test this but not familiar with the HTTP commands. If you can point me in the right direction I'll give it a try. This could help me with other devices as well.

Mark

You need to have the webserver active, then you can send it triggers, and other stuff.

The format is (without the space):
http:// yourip:blueiriswebserverport/admin?camera=Cam1&trigger&user=xxx&pw=xxx

Give that a try using System::HTTPGet and see if you can get a result. Thanks

[Stipe]

Still trying to find a solution to this. Any Blue Iris users have this working?

I have a workaround now via Tasker, but that isn't really ideal for the long term.

Thanks

[Dean Roddey]

If it really does require a session cookie, then it would likely really require a driver to work, so that the driver could maintain that type of info.