Re: [mh] AD2USB event states

Yes, you will need to figure out what zone each sensor is mapped to. You
can do that by looking at the programming, walking past them and pushing *
on the key pad, or on the serial console if your using the AD2USB (if you
have the AD2USB you will also get the rf id for the sensor). There are 2
ways to monitor the sensor status, 1 using the normal zone faults, but the
down fall is that when the system is armed you cant see it. 2. using the
raw messages (*!REL, !RFX)*. If your system is all wireless or your using a
zone expander, you don't have to do any programming to get the messages
(while armed). If your using the on board wired zones 1-8 then you will
have to program the AD2USB virtual relays to the zones if you want to get
on board zone status while the system is armed.


You will get messages like this from the AD2USB:
[01000001000---------],0e5,[f707000600e5800c0c020000],"ARMED ***AWAY*****
ALL SECURE **"
[001000010000--------],010,[f70700060010808c08020000],"ARMED ***STAY** ZONE
BYPASSED "

This is what the wireless (RF) messages look like:
!RFX:0180036,80


Check out:
http://www.nutech.com/index.php?option=com_fireboard&Itemid=74&func=view&id=5&catid=4#5



On Mon, Sep 30, 2013 at 10:50 PM, H Plato <hp...@gm...> wrote:

> OK, I'm going to order one and get it shipped up here.
>
> So to find out the RFIDs (I have a bunch of motion sensors which I'm
> assuming are RF), I have to monitor the output when I walk past them? I
> didn't program the alarm system, and don't quite know how it works.
>
> On 2013-09-30, at 9:45 PM, Wayne Gatlin <wa...@ra...> wrote:
>
> Yes, the names in the .ini are just a better name than the short name you
> assign in the alarm. The zone numbers, rfid, and relay numbers are mappings
> and are matched to the panel messages. The AD2USB works very well and is
> worth it if to want to integrate with the alarm panel.
>
> -Wayne
>  On Sep 30, 2013 10:30 PM, "H Plato" <hp...@gm...> wrote:
>
>> Neat. As I got this alarm system with the house, I don't have any
>> documentation. Does the panel provide the zone numbers, names, and RF IDs?
>>
>>
>> On 2013-09-30, at 7:19 PM, Wayne Gatlin <wa...@ra...> wrote:
>>
>>  I got my hands on an AD2USB misterhouse interface that was written by Kirk
>> Friedenberger. The interface is pretty much done so I trashed what I was
>> working on and started working with his code. The only thing missing is
>> relay support and I'm almost done with that. Once I'm done with the relay
>> part I'm going to start working on ser2sock support so the AD2USB
>> doesn't have to be directly connected to the misterhouse server. In his
>> code each zone is a different object. This is how the zones are defined in
>> the mh.ini.
>>
>>
>> # Names for partitions
>> AD2USB_part_1=House
>> AD2USB_part_2=Internal
>>
>> # Names for zones
>> AD2USB_zone_001=Zone 1
>> AD2USB_zone_002=Zone 2
>> AD2USB_zone_003=Front Door
>> AD2USB_zone_004=Living Room Windows Back Door
>> AD2USB_zone_005=Zone 6
>> AD2USB_zone_006=Living Room Motion
>> AD2USB_zone_007=Garage Door
>> #AD2USB_zone_008=Bedroom Windows
>> #AD2USB_zone_010=South Kitchen Window
>> #AD2USB_zone_011=East Kitchen Window
>> #AD2USB_zone_020=New1
>> #AD2USB_zone_021=New2
>> #AD2USB_zone_022=New3
>>
>> # Wireless IDs for wireless zone devices
>> #    format: AD2USB_wireless<RF_ID>=<zone_number>
>> #       where <RF_ID> is the RF ID of the device
>> #       where <zone_number> is the zone configured in the panel
>> #AD2USB_wireless_1045714=010
>> #AD2USB_wireless_0014936=011
>>
>> # Relay mapping to zones for the AD2USB
>> #   format: AD2USB_relay_<Relay_board_idRelay_number>=<Zone_number>
>> AD2USB_relay_1301=001
>> AD2USB_relay_1302=002
>> AD2USB_relay_1303=003
>> AD2USB_relay_1304=004
>> AD2USB_relay_1401=005
>> AD2USB_relay_1402=006
>> AD2USB_relay_1403=007
>> AD2USB_relay_1404=008
>>
>>
>> -Wayne
>>
>>
>> On Mon, Sep 30, 2013 at 12:59 PM, H Plato <hp...@gm...> wrote:
>>
>>> I think this might have answered my earlier question about integrating
>>> an adt alarm panel. i think a safewatch pro 3000 is a rebranded vista
>>> 20p, which is compatible with the ad2usb. I think it makes sense to
>>> have the sensors as separate objects as this would be a 'drop in',
>>> type replacement for ms13s and ds10s. I'll try and find a ad2usb and
>>> can help test, develop later on.
>>>
>>> Sent from my mobile device.
>>>
>>> > On Sep 24, 2013, at 10:56 PM, Wayne Gatlin <wa...@ra...> wrote:
>>> >
>>> > Hello,
>>> >
>>> > I am new to misterhouse, this is my first time using it and writing
>>> code for it. I have completed the code to watch and track serial messages
>>> from the AD2USB interface (from my Vista 21 alarm system). I really don't
>>> know the best way to design the interface to interact with misterhouse so I
>>> will explain what I have in mind and maybe someone can give me some
>>> suggestions on the best way to do it.
>>> >
>>> > What I have completed:
>>> > - My current code watches the alarm messages, keeps track of the
>>> states of the any zones you configure in the mh.private.ini
>>> > (This can be used to watch motion detectors and trigger lights, etc.)
>>> > - it also keeps track of the alarm system state
>>> (armed/disarmed/alarmed)
>>> >
>>> > Currently my code just puts the zone states in a comma separated list
>>> containing the faulted zones.
>>> >
>>> > from my mh.private.ini:
>>> > ad2usb_relay_zone_map=14-02-006-Livingroom_motion,14-03-007-Garage_Open
>>> >
>>> > so if the Livingroom_motion and the Garage_Open zone is faulted the
>>> list will be "Livingroom_motion-R,Garage_Open-R" and when the zone is no
>>> longer faulted, that zone is removed from the list.
>>> >
>>> > I put the faulted zone list in a var called $faultedzonecnt
>>> > The alarm system state is in a var called $alarmstate
>>> >
>>> >
>>> >
>>> > The first thing I would like to do is be able to set times to alert me
>>> that the Garage_Open zone is faulted via the web interface. Maybe a
>>> calendar item or something.
>>> >
>>> > Next I want to watch the system alarm state and run a voice command
>>> when it changes to alarmed and run another one when it changes back. This
>>> will start my cameras recording. I would like to do this in a separate
>>> script from the one I have already written to keep this one generic so
>>> others can use it.
>>> >
>>> > Last (for now) I want to be able to send commands to the alarm system,
>>> but to do this I need to be able to see the response. I've played with the
>>>  Voice_Cmd and got it working to trigger my zoneminder cameras, but when I
>>> send a command via telnet, I cant figure out how to send a response back to
>>> the terminal.
>>> >
>>> >
>>> >
>>> > -Wayne
>>> >
>>> ------------------------------------------------------------------------------
>>> > October Webinars: Code for Performance
>>> > Free Intel webinars can help you accelerate application performance.
>>> > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the
>>> most from
>>> > the latest Intel processors and coprocessors. See abstracts and
>>> register >
>>> >
>>> http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk
>>> > ________________________________________________________
>>> > To unsubscribe from this list, go to:
>>> http://sourceforge.net/mail/?group_id=1365
>>> >
>>>
>>
>>
>>
>