travisc wrote:Raneil, what happens if you try to arm your alarm while a zone is still open?
The system's status is indicated in the smaller table to the right of the zone status grid. The script parses the System Status (e.g., "Ready", "Not Read", "Away", "Error", "In Alarm", perhaps a few others I don't recall at the moment) as well as the individual zone statuses and allows arming/disarming only as appropriate. That is, the system can only be armed when the system status is "Ready", and can only be disarmed when the system status is "Away" or "In Alarm".
There is no provision to "Arm Stay"; only "Arm Away". And no detail as to the nature of any "Error" status. These are limitations of the TL-150.
Incidentally, the TL-150 also reports (individually for each zone) the number of minutes (up to 1 hour, I think) that have elapsed since the zone's status changed. I find that to be very handy. This is not shown in the screen shot since that information is only displayed as a tooltip if you hover the cursor over a zone in the grid (can't capture that in a screenshot). But, since the information
is in the HTML, it's easily parsed and can therefore be made available to Indigo via the plugin.
travisc wrote:Hopefully we can abstract out the routines for each interface so if they use interface x we call routine x, interface y we call routine y. The serial interface will respond in real-time, the ethernet one would likely have to be constantly polled.
First, I think we'll need to clearly define exactly what we want the plugin to do. Personally, I'm of the Keep It Simple philosophy. I would propose a plugin that simply updates a collection of user-named Indigo variables that represent the current System Status, the status of each zone, and optionally, the elapsed time since the most recent status chagne for each zone. The user could then decide what to do with those variables.
Yes, the TL-150 would need to be polled (or queried in response to real-time events generated by additional hardware, but that's well beyond the scope of this proposed plugin). Perhaps allow the user to establish a polling frequency (withing a permitted reasonable range, of course), as well as the ability to update the variables on demand.
travisc wrote:Once the interface plugin is done it'd be nice to make a web plugin that can dynamically create a control page for any setup.
Now that's an ambitious project!
travisc wrote:Mine looks like this at the moment:
Looks good! So, you can arm/disarm the system from your phone without entering an access code? I debated myself endlessly about that, and finally decided to require the code. It shouldn't be hard to make that part optional, though; let the user decide.