[quote=“TimAlls, post:19, topic:167894”]Now I am really curious!
Guessed, please tell us what the system is you are working on. I had no idea there were more options.
There are issues with the DSC plugin as you know.
Paradox System: Does it still work with SQ Remote? Is it still event based? EG with DSC the zones can be out of sync with the Vera if communication is lost…it just waits for an incoming serial event.
Tell us more!
Regards
Tim Alls
AllSeas Yachts[/quote]
I’ve hyperlinked the ones I know about in the table above to help folks.
In my house, I have a Paradox Security “DGP-848”, with ~20 zones or so. It’s compatible with the newer “EVO” models, and uses the same interface board (PRT3, per the table above)
This has been running for some time now (search forums history to get a sense) and since it’s the one I run in my house, it’s typically the one that gets fixed… mostly because I “live” with whatever issues it has, and so I get a sense of what needs to be fixed (etc)
http://forum.micasaverde.com/index.php?topic=2492.msg9997#msg9997
On my bench (if you can call it that) I have a DSC, that @strangely loaned me, that I’ve been using to prove out the Interface standardization effort, as well as generally re-write the code to [hopefully] provide better stability & functionality than the current version (from the MiOS Marketplace), since that developer no longer works for MiCasaVerde.
If there are problems with that, then please request an account (from @mcvovidiu) and file them specifically using the Bug tracking tool in:
http://code.mios.com/trac/mios_dscalarmpanel
This tool is only available to people that login, so you won’t see it usually. I will try to fix as many core issues as possible, but at some point I do have to return the Panel to @strangely (as he bought it for a friend of his, I’m just borrowing it, and it’s probably like to get his $$ back). Right now, the folks “testing” this code are the real eyes-and-ears for problems in the DSC as I only have a “test” rig. Not the optimum way to develop, since I often cannot “feel” the problems that only occur in the real-world.
The DSC does read it’s Zone inputs at Startup, so could probably be convinced to re-read them when certain events occur (like long term IO disconnect, or even just a timed-event). To my knowledge, none of the other panels currently do that (including my Paradox) but it’s not out of the question if that is a REAL-World, frequent occurrence - although, then I’d be asking “why?” since I haven’t seen comms problems on mine in yrs, and it would seem that any comms path problem should be fixed first (although agree the code could be more resilient)
Part of the larger effort is to standardize the [MiOS] Interface used by all these panels. This thread is the background for that:
http://forum.micasaverde.com/index.php?topic=3713.0
The goal there is to make all the panels “look” the same to MiOS, such that the Control Point owners (SQRemote, Home Buddy, iVera, Automater.app etc, etc) have a consistent way of working with these Panels, no matter what the vendor.
We take for granted that this normalization/API standardization has taken place for Light Switches, Thermostats etc. In this case, we’ve done a first-cut at this for Alarm units so we can start to have the CP folks provide “standardized” (and complex) UI’s to cover these, display current state, permit Key-Pad entry of PIN’s for Disarming, along with other more interesting interactions.
In the meantime, yes, you can use things like SQRemote (I do) to show Zone status’s as well as Scene-Buttons for Arm/Stay/Disarm type events. Note that I don’t use it for Disarm, as that would require you to ‘store’ the PIN codes in Vera (in it’s Scene defn) so it could disarm the Panel, which I don’t tend to like. Typically Arming/Stay Arming modes don’t require that so these are easy.