Re: [misterhouse-users] Bill Sobel's DSC alarm code; serial.pm methods in general

[chris w. <cw...@xm...>]

Danal/Bill,

Can the DSC interface report all activity on its attached sensors, or
only those that fire when the alarm is armed?

I'd like to install an alarm, such that the motion sensors can interface
with MH when i'm home (turning lights on/off as appropriate), and
trigger an alarm condition (preferably without requiring any action from
MH) if the system is armed.

Will DSC be of any help for that?

chris.

> Danal Estes wrote:
> 
> Well Bill, I broke down a purchased a DSC printer interface.  Got it,
> hooked it up (to a DSC PC1555 alarm system), added the appropriate
> parms to mh.private.ini to use your DSC_Alarm.pm and now see things
> from the DSC in the mh logs.
> 
> A couple of questions:
> 
> Have you taken this code any further? (than the 1.1 version currently
> on CVS, which logs as described above)
> 
> If not, mind if I do?
> 
> If I do, I'd like to discuss somewhat the philosophy of what should be
> in the '.pm' vs. what should be in user scripts.
> 
> That is, should DSC_Alarm.pm just return the whole line as received?
> All parsing and/or state tracking would be user script
> responsibility...
> 
> -or-
> 
> Should DSC_Alarm.pm track "states" of the alarm system and only expose
> methods like "Get_DSC_Status" which returns "Open, Closed,
> Alarm(ing?)", "Get_DSC_UserCode" which returns the last user id that
> open/closed the system (usually 40), "Get_DSC_Trouble" which returns
> trouble status, etc.
> 
> Bill and/or Bruce, thoughts?
> 
> Danal
>