EyezOn Forum

I have successfully written a Socket Comm program to disarm my Alarm System, but for the life of me I cannot figure out how to get a Status report back from the EnvisaLink! :-( I assume I need to send a message of the form ^CC,DATA$ I am currently getting Status by scraping the device web page but ...

K-Man (or should I say Super-Man?) - You can henceforth be quoted on that! Sending http://user:user@192.168.1.81 logs in, and followed by http://192.168.1.81/2?A=4&p=1&X=1234 successfully Disarms the system. Awesome! Thanks so very much ! I wasn't looking forward to having to dust off my socket comm ...

K-Man

I just noticed that you indicated exactly what I was curious about, and that is that the CGI does support login/pw parameters.

How is that done?

Also can Status be fetched via the CGI?

Even better, is there a CGI document for the interface? Then I can answer my own questions!

Thanks. I was confused because I hadn't referred to anything I did as "canned". All is clear now, and the GCI works, kinda. The problem is when "http://192.168.1.81/2?A=4&p=1&X=1234" is sent, the response is a request for login/pw entry which is a form entry not easily submitted by automation. As ...

... you just "can" the HTTP GET your browser sends to the Envisalink to arm/disarm the panel. Considering that your application is so simple, you might find this easier. That sounds intriguing, but not sure what you mean by "can the HTTP GET" The only prior post in this thread I saw that might ...

I think I'm getting closer. You were correct, the local EnvisaLink pw is "user" I believe the reason I am not having success is (reading the TPI guide closely) is that the Socket connection must be persistent! The socket utility I'm using, to try and take the easy course, closes the connection with ...

K-Man Didn't work. I did discover that the pw= "user" definately doesn't work. That was the initial default, but I changed it upon installation. I get a FAIL when I try that but when I "Login" and then send my current pw terminated with a CR I get a "Login:" response back. Can't seem to get past ...

K-Man You ARE da man indeed. Thanks very, very much. I was pulling my hair out over this (and I'm pretty much bald so I really didn't need any more losses!) I'll give your feedback a try. The doco is really BAD in this one. It does not indicate the need for a record terminator, and it says that the ...

OK. The TPI interface looks like the perfect way to go, BUT I'm missing something as I can't get past the login. When I open a socket to the EnvisaLink I get the expected response of "Login:" but when I then send my password string (eg, 00werty) I either get another... Login: or, I get a Login ...

Thanks all for the helpfull feedback. I had discovered the TPI manual last night, but downloaded the incorrect one. Thanks to your feedback today I realized my error and got the Ademco guide (which is significantly different) I was busy coding up a Checksum routine, and see that I don't need that ...