alarmdecoder.com

Howdy folks - have my ad2usb setup as a 'common' keypad across two partitions on a Vista 20P; wondering if there's an easy way to handle events generated by the individual partitions?

The event handlers in the AlarmDecoder library seem to get confused by the common ad2usb keypad 'seeing' events from both partitions (in this case, partition one is ARMED AWAY ZONE BYPASSED, and partition 2 is DISARMED, READY TO ARM):

Apr 21 14:12:52 *** ARMED *** (device.on_arm)
Apr 21 14:12:52 *** DISARMED *** (device.on_disarm)
Apr 21 14:12:53 [1000000100010000----],008,[f70000020008005c08020000000000],"****DISARMED**** Ready to Arm "
Apr 21 14:12:56 *** ARMED *** (device.on_arm)
Apr 21 14:12:56 [0100001100010000----],008,[f70000091008004c1c020000000000],"ARMED ***AWAY*** ZONE BYPASSED "
Apr 21 14:12:56 *** DISARMED *** (device.on_disarm)
Apr 21 14:12:56 [1000000100010000----],008,[f70000040008005c08020000000000],"****DISARMED**** Ready to Arm "
Apr 21 14:13:00 *** ARMED *** (device.on_arm)
Apr 21 14:13:00 *** DISARMED *** (device.on_disarm)
Apr 21 14:13:01 [1000000100010000----],008,[f70000020008005c08020000000000],"****DISARMED**** Ready to Arm "
Apr 21 14:13:04 *** ARMED *** (device.on_arm)
Apr 21 14:13:04 [0100001100010000----],008,[f70000091008004c1c020000000000],"ARMED ***AWAY*** ZONE BYPASSED "
Apr 21 14:13:04 *** DISARMED *** (device.on_disarm)
Apr 21 14:13:04 [1000000100010000----],008,[f70000040008005c08020000000000],"****DISARMED**** Ready to Arm "
Apr 21 14:13:07 *** ARMED ***
Apr 21 14:13:08 *** DISARMED ***
Apr 21 14:13:08 [1000000100010000----],008,[f70000020008005c08020000000000],"****DISARMED**** Ready to Arm "
Apr 21 14:13:11 *** ARMED ***
Apr 21 14:13:11 [0100001100010000----],008,[f70000091008004c1c020000000000],"ARMED ***AWAY*** ZONE BYPASSED "
Apr 21 14:13:12 *** DISARMED ***
Apr 21 14:13:12 [1000000100010000----],008,[f70000040008005c08020000000000],"****DISARMED**** Ready to Arm "

Could probably parse out the raw message field - f7000002... looks like partition 2, f7000009 looks like partition 1?

Robert

I'm not sure on the data in the field, maybe Sean can chime in on that, but I think the easiest way would be to enable emulation for the Long Range Radio and handle those events. If you have a physical radio installed you'll just need to enable the individual messages on your panel. The partition number is the second parameter in LRR messages reported by the AlarmDecoder.

You can take a look at LRR messages for message details, or How do I enable LRR? for instructions on how to enable it.

I'm having the same exact issue. I have a Vista 20P with two partitions and the A2DUSB messaging toggles between one partition being armed and the other not being armed. I also have an 7847i Internet Connection Module which is monitored by an alarm company using LRR. I'm not sure I understand the previous suggestions but I'm leery to change the LRR settings. Any more information on this subject would be appreciated.

Thanks, Joe

Joe89 wrote:I'm having the same exact issue. I have a Vista 20P with two partitions and the A2DUSB messaging toggles between one partition being armed and the other not being armed. I also have an 7847i Internet Connection Module which is monitored by an alarm company using LRR. I'm not sure I understand the previous suggestions but I'm leery to change the LRR settings. Any more information on this subject would be appreciated.

Thanks, Joe

We are looking at writing an example function to "filter" out messages to specific keypads using the Python API. This way one only sees messages to the partition they want as a keypad is assigned to a given partition.

Using the AlarmDecoder keypad app this is already done by setting the keypad mask filter in the App.

As for your 7847i. You can already see LRR messages and can write LRR events using the Python API and it wont be necessary to make any programming changes to your panel or to the AD2*. Those changes are only needed if you do not have a 7847 or similar device and need to "emulate" one using the AD2* device.

Re
Sean M

Scott wrote:I'm not sure on the data in the field, maybe Sean can chime in on that, but I think the easiest way would be to enable emulation for the Long Range Radio and handle those events. If you have a physical radio installed you'll just need to enable the individual messages on your panel. The partition number is the second parameter in LRR messages reported by the AlarmDecoder.

You can take a look at LRR messages for message details, or How do I enable LRR? for instructions on how to enable it.

Thanks, Scott - I'll give that a shot.

Any kind of caveats to worry about enabling LRR emulation on the ad2usb device?

Nope, should be pretty straight forward.

You'll get an error message on the panel in two cases:

• Panel expects an LRR device but none are found. (LRR enabled, no physical LRR or emulation)
• Panel had a collision because of multiple LRR devices. (LRR enabled, physical LRR and emulation enabled)

Those can be fixed by changing the emulation setting and then entering and exiting programming mode on the panel.

Ok, I'm seeing the LRR messages in my terminal program, but only for partition 1:

Using PIN + *1 + 2 to GOTO partition 1 and arm:

Code: Select all

[1000000100000000----],008,[f70000020008001c08020000000000],"****DISARMED****  Ready to Arm  "
!Sending.done
!Sending.done
[0101020100000000----],008,[f70000051008020c0c020000000000],"ARMED ***AWAY***You may exit now"
[0101000100000000----],008,[f70000080008000c0c020000000000],"ARMED ***AWAY***You may exit now"
!LRR:003,1,ARM_AWAY  <-----------
!Sending.done
!Sending.done
!Sending.done
!Sending.done

Sending disarm:

Code: Select all

!LRR:003,1,OPEN  <-----------
[1000000100000000----],008,[f70000020008001c08020000000000],"****DISARMED****  Ready to Arm  "
[1001010100000000----],008,[f70000051008011c08020000000000],"****DISARMED****  Ready to Arm  "
[1001000100000000----],008,[f70000080008001c08020000000000],"****DISARMED****  Ready to Arm  "
[1001000100000000----],008,[f700000d1008001c08020000000000],"****DISARMED****  Ready to Arm  "


GOTO partition *2 and arm:

Code: Select all

!Sending.done
!Sending.done
!Sending.done
!Sending.done
!Sending.done
[1000010100000000----],008,[f70000060008011c08020000000000],"****DISARMED****  Ready to Arm  "
!Sending.done
[1000000100000000----],008,[f70000060008001c08020000000000],"****DISARMED****  Ready to Arm  "
!Sending.done
[1001000100000000----],008,[f70000060008001c08020000000000],"****DISARMED****  Ready to Arm  "
!Sending.done
[0101050100000000----],008,[f70000060008050c0c020000000000],"ARMED ***AWAY***You may exit now"
[1001000100000000----],008,[f70000091008001c08020000000000],"****DISARMED****  Ready to Arm  "
[0101050100000000----],008,[f70000060008050c0c020000000000],"ARMED ***AWAY***You may exit now"
[1001000100000000----],008,[f70000091008001c08020000000000],"****DISARMED****  Ready to Arm  "

Sending disarm to partition 2:

Code: Select all

!Sending.done
!Sending.done
!Sending.done
[1001010100000000----],008,[f70000060008011c08020000000000],"****DISARMED****  Ready to Arm  "
[1001000100000000----],008,[f70000060008001c08020000000000],"****DISARMED****  Ready to Arm  "
[1001000100000000----],008,[f70000091008001c08020000000000],"****DISARMED****  Ready to Arm  "

No LRR messages for the second partition for arm/disarm?

The Vista 20P 9.18 offers a bunch of options under *29 for an AlarmNet IP/GSM communicator of some kind, but I basically just did "*29 1 * *".

You just need to program the panel to report for partition #2
∗65 Open Report Code (1,1,0)
∗66 Arm Away/Stay Rpt Code (1,1,1,1,0,0)

These expect a 1 for enable of each partition and also it can be turned on for the common partition if you have one setup.

Hope this helps.

Re
Sean M

Yeap, that was it - thanks for pointing me in the right direction, Sean!