Ok no worries.
I have worked out a workaround for now which works for my needs.
I checked the source html of the envisalink control page for the form information that is used when you arm or disarm the second partition:
- Code: Select all
<TR><TD>Partition 02</TD><TD BGCOLOR="LIME">Ready </TD>
<TD BGCOLOR="YELLOW"> Trouble</TD>
<TD WIDTH=200px>
<P><FORM ACTION=2 METHOD=GET>
<INPUT TYPE=HIDDEN NAME=A VALUE=3>
<INPUT TYPE=SUBMIT VALUE=ARM>
<input type=hidden name=p value=2>
<SPAN CLASS=LITTLE>USER CODE</SPAN>
<INPUT TYPE=PASSWORD MAXLENGTH=6 SIZE=6 NAME=X>
</FORM>
Therefore I can bypass using the page to arm or disarm the partition by crafting the http request using the form information above:
http://
ip_address_of_envis3/2?A=3&p=2&X=
pincode_to_armas an example:
http://10.105.10.249/2?A=3&p=2&X=4599I put this my browser but I was prompted to authenticate, you can get past this too without manual intervention:
http://user:password@10.105.10.249/2?A=3&p=2&X=4599Hey ho! The alarm system armed!
A quick deconstruction of the disarm page and I can see that the A data changes to a 4 so to disarm:
http://user:password@10.105.10.249/2?A=4&p=2&X=4599And this worked too!
So all I needed to do was create 2 scripts and put these calls into them so they can be called from Indigo:
arm_p2.sh
- Code: Select all
#!/bin/bash
curl "http://user:password@10.105.10.249/2?A=3&p=2&X=4599"
disarm_p2.sh
- Code: Select all
#!/bin/bash
curl "http://user:password@10.105.10.249/2?A=4&p=2&X=4599"
I can now call these from within Indigo and the alarm arms and disarms!
Seeing as all the other information about the second partition is already obtained by the plugin, this should be all you need!