Honeywell Ademco Vista Alarm Panels Plugin via AD2USB

Plugins & Plugin Development Unmaintained
#1

  • Version 2.4 has been launched for beta testing. See here.

  • All the files, documentation and installation instructions can be found here.

[hr]
Next week I’m on vacation, so I didn’t have time to make it more foolproof (haven’t tested unlikely scenarios or usage patterns). Please put your panel in test mode when trying the plugin for the first time.

I still have to make it more standard compliant, and to add more events and scenes. I also have to write documentation for it.

Features:

  • Arm / Disarm.
  • Press lettered key (A, B, C, D); this is the only way to go into panic mode.
  • See and bypass faulted zones.
  • No zone and partition discovery. You have to input the number of partitions in the panel’s Advanced tab.

Here you can get the files:
http://code.mios.com/trac/mios_vista-alarm-panel-ad2usb/wiki

Please post here any bugs you encounter or any feature requests.

#2

Awesome, I’ll give it a shot.

#3

Well, it works! I’m able to arm, disarm, bypass zones, etc.

When you get “DISARMED-Press * to show faults”, you need to send it a * in order to detect the faulted zones. (Sean suggests this in his forum posts).

You mention that you need to add events - are we going to have events for zones or are we going to get child devices for each zone?

As I mentioned previously, handling !RFX and !EXP messages is very important if you want to have Vera respond to faults quickly. I use these events to turn on my garage light, hall lights, etc.

Great work!

#4

I have my Vista 20P panel on the bench still, and I am adding sensors to my house as I have time (mostly RF), when I have it all done I will permanently install the panel in its final location, for now I have my NuTech AD2USB connected to my PC and am running the “AD2USB Virtual Keypad” to test it out, works well. Eventually my goal is to connect it to the Vera and use the 5 wireless (RF) 5800-PIR’s to trigger scenes in rooms, via Vera integration. If you can get the “!RFX” processing working, for event generation/firing off scenes, that is what I need to get that part done.

Here is an example of a few of the !RFX messages

Here is opening the rear door to the house, which has a 5820L on it, and is in “Zone 10”, in partition 1

!RFX:0867715,80
!AUI:120600000000656c02456cf5ec0101010000
!AUI:1606000000006663024543f531fb456cf5ec03020106
[0000000110000000----],010,[f70000231010000028020000000000],"FAULT 10 HOUSE REAR DOOR "

Here is the house rear door being closed…

[0000000110000000----],010,[f70000231010000028020000000000],"FAULT 10 HOUSE REAR DOOR "
!RFX:0867715,00
!AUI:120600000000676c02456cf5ec0101010000
!AUI:1606000000006063024543f531fb456cf5ec03010101
[1000000110000000----],008,[f70000231008001c28020000000000],“HOUSE CHIME,Rdy to Arm”

Here is an example of a 5800-PIR going off and then restoring

!RFX:0475165,a0
!AUI:120600000000616c02456cf5ec0101010000
!AUI:1606000000006263024543f531fb456cf5ec03020106
[0000000110000000----],012,[f70000231012000028020000000000],"FAULT 12 HOUSE KITCHEN MOTION "

!RFX:0475165,00
!AUI:120600000000636c02456cf5ec0101010000
[1000000110000000----],008,[f70000231008001c28020000000000],“HOUSE CHIME,Rdy to Arm”
!AUI:1606000000006463024543f531fb456cf5ec03010101

#5

Does the device get created using the:

D_VistaAlarmPanel1.xml
and the:
I_VistaAlarmPanel1.xml

JOD.

#6
Yes. Are you trying it out?
Yes, uploaded the files last night and after dozens of engine restarts and a couple of reboots, I'm not seeing anything other than the generic_device that was created.

JOD.

#7

AD2USB adapter.
http://code.mios.com/trac/mios_vista-alarm-panel-ad2usb

There are extra steps not outlined in the DSC instructions.
After picking the serial port and assigning the device.
The page then jumps to another page.
Pick the serial port? This area only allows you to pick a device, not port.
Pick the Vista Alarm again.
“Save”
Brings me back to the “generic_device” where I first started.

*Edit. Bug: http://bugs.micasaverde.com/view.php?id=1661

JOD.

#8

I connected AD2USB(which was working with ad2usbgui) to the VERA at USB1. I uploaded all 8 files in ‘Luup Files’ then created a device with UpnpDevFilename ‘D_VERAADEMCO.xml’ and called it VERAADEMCO in Description, restarted the Lua engine, Reloaded the web page. Device called ‘VERAADEMCO’ showed up on Mios but can’t do anything with it. What am I doing wrong ???

#9

@shahhim,

Use the D_VistaAlarmPanel1.xml and the I_VistaAlarmPanel1.xml to create the device and Save.

In your instance just replace the D_VERAADEMCO.xml and add the I_xml.

Then go to MIOS Developers → Serial Port configuration → select the serial port → select Used by device → select the device you created → Select the serial port → Save.

I then had two devices show up. That’s as far as I got tonight.

What baud rate should be used?

Is it a necessity to have the #6139 keypad?

Are there any additional instructions someone can post?

JOD.

#10

I was able to link Ademco V20P and Vera via AD@USB Plugin Version 1.0 Alpha !!!. [Inspite of not being a computer person, Thanks to this forum and everyone’s eagerness to help]
Great, great work mcvflorin !
Thanks JOD. Actually, I was able to create device using ‘D_VistaAlarmPanel1.xml’. When I connected AD2USB to my computer and used ad2usbgui, i used 115200 as the baud rate as suggested by Sean M since other rates were not working right. So I used the same baud rate here. I have the 6160RF keyboard
Arm/Stay/Night/Disarm works with Droid Incredible
Still learning how to check Defaulted zones, etc
Can’t wait to be able to do more with future versions

#11
I was able to create device using 'D_VistaAlarmPanel1.xml'
You're correct. I started over and was able to create the same two devices by only using the D_xml. I'm not able to get any further than that. My installed keypad is #31, does the AD2USB need to be given an address? In order to see the status or control arming / disarming?

JOD.

#12

The only time I had to put in the keypad info was when I initailly connected AD2USB to the laptop using ad2usbgui. Prior to re-creating the device, I just checked that AD2USB connection was working well with the putty and ad2usbgui

#13

[quote=“JOD, post:11, topic:168766”]

I was able to create device using ‘D_VistaAlarmPanel1.xml’

You’re correct. I started over and was able to create the same two devices by only using the D_xml.
I’m not able to get any further than that.
My installed keypad is #31, does the AD2USB need to be given an address? In order to see the status or control arming / disarming?

JOD.[/quote]

Hay JOD

If your alarm panel wants keypads at address 31 then you have an SE panel probably a 10 or 20SE
If this is the case then depending on what firmware you may need to update your AD2USB.

Press V in a terminal with the AD2USB or reboot the device with = and let me know the firmware version.
If you do need to update the firmware download the latest 2.2a.3 from my forums page at nutech dot com.
This version supports the SE panel as well as LRR support. It will also work with exposing any Zone expander or RF expander you have but you wont be able to Emulate a zone expander or relay board that is not supported on the SE panel at this time.

Re
Sean M

#14

Sean,

Thank you!!!
Yep, I have the SE and that’s the info I needed. I’ve been researching how to get into the Vista product thinking that the AD2USB supported the SE out of the box, so I’m glad you brought that search to an end.

I havent yet attempted to connect the adapter to the PC so that’s tommorow’s project. I’ll let you know what the FW version is after that.

Oh, Is it true the baud rate is not important? I just stumbled on an article stating that.

Thanks again for the info.

JOD.

#15

If you have a new AD2USB (with the mini-USB plug), the serial port MUST be 115200.

#16

!VER:00000581,V2.2a.2,TX;RX;SM;VZ;RF;ZX;PE;RE;AU

No issues logging in with putty and changing the keypad address from the default (18) to my (31), it then came alive.

[000000010000--------],001,[f70000008001000008000000000000],"FAULT 01 ZONE 01 " [100000010000--------],001,[f70000008001001c08000000000000],"****DISARMED**** READY TO ARM " [001103010000--------],001,[f70000008001038c08000000000000],"ARMED ***STAY***You may exit now" [100100010000--------],001,[f70000008001001c08000000000000],"****DISARMED**** READY TO ARM "
But no joy with Vera.
Do I need to change the firmware?

JOD.

#17

I’m back. :slight_smile:

This is implemented in the current plugin version.

I thought about adding child devices for each zone, but the problem is that I don’t know how to get the number of zones, or even if it’s possible to do that. The only easy way to find about a zone’s existence is when that zone is faulted. The hard way would be to go into Install Mode and go through all the zones and check if they are disabled or not. Too complicated and unreliable.

Thanks for the feedback!

#18

mcvflorin,

How about a manual way to setup the zones? most of mine will be RF, so processing of the “!RFX” messages will get you open/close on those very quickly, perhaps a table we can setup with the zone#,name,!RFX Serial # would do it.

Mitch

#19

I certainly don’t mind adding the child zone device manually.

Another option is to have a checkbox for “learn mode” where the Vista alarm plugin automatically creates devices for zones it sees faulted. You can use the zone descriptions to name the children. The user can just walk around the house and manually fault each zone to create the children. This is similar to how the panel itself pairs with wireless sensors (or adding Z-wave devices, for that matter :wink: )

#20

I like the idea with the table, will add this to my TODO list.