Honeywell Ademco Vista Alarm Panels Plugin via AD2USB

I’ve got my scenes activated by schedule. It’s what works for me so far as I know times when everyone should be home or not. I’ve got my alarm auto-disarming at a certain time b/c I know i’ll be ready to leave the house then. The more complicated ones will require something called PLEG which allows you to add conditions to your scenes. I’ve not got into those just yet.

Edit: Also, i found that I don’t need to change my door sensor contacts from “motion” to “door” as it trips when it is open anyway. All my sensors are armed by default so that when tripped you see the red running man. The alarm panel is what decides if it triggers an alarm or not.

I upgraded from a Vera 2 to a Vera 3 tonight. All works well, except for my Ademco plugin. What do I need to change? Is it a port problem?

Here’s my serial port config screen:

link to photo

I keep getting “Ademco Vista Alarm Panel[99] : Failed to open IO Port”. Any thoughts?

[quote=“DeltaNu1142, post:802, topic:168766”]I upgraded from a Vera 2 to a Vera 3 tonight. All works well, except for my Ademco plugin. What do I need to change? Is it a port problem?

Here’s my serial port config screen:

link to photo

I keep getting “Ademco Vista Alarm Panel[99] : Failed to open IO Port”. Any thoughts?[/quote]

If you’ve got an AD2USB, this should show up on a ttyUSB0 or USB1 port. Try switching your “used by device” to the ttyUSB0 port. Don’t forget to adjust the port speed also. I suspect that’s all you need.

Hey, you’re right–I just swapped over to the other port. All’s well–kudos!

I’ve got my scenes activated by schedule. It’s what works for me so far as I know times when everyone should be home or not. I’ve got my alarm auto-disarming at a certain time b/c I know i’ll be ready to leave the house then. The more complicated ones will require something called PLEG which allows you to add conditions to your scenes. I’ve not got into those just yet.

Edit: Also, i found that I don’t need to change my door sensor contacts from “motion” to “door” as it trips when it is open anyway. All my sensors are armed by default so that when tripped you see the red running man. The alarm panel is what decides if it triggers an alarm or not.[/quote]

Is PLEG a app? I tried to search for it but could not find one. It seems I should be able to turn on lights with the alarm system disarm. There must be some step I am missing.

Yes, PLEG is an app, and yes, you can do that and more with it. I have a PLEG that does exactly that. Think of it as a replacement for scenes, but with more flexibility.
I’m on TapaTalk or I’d link to the forum for it…

I found out today talking to Alarm Decoder (Nutech) that the reason I had so many problems is because the latest batch of AD2USB’s that were made have a new USB chip set. The drivers for it is not loaded in the Vera. That explains why I had problems even with UI5 when other people never had any issues. Here is a link to their forum talking about it.

http://www.alarmdecoder.com/forums/viewtopic.php?f=3&t=122

aaaaah. That makes perfect sense. That’s why some people were able to get it working in UI7 and the rest of us weren’t. Maybe the next release of UI7 will incorporate drivers for the new chip. That’s nice to know, thanks Chasiu!

But why when you loaded the drivers for UI7 you couldn’t get it to work? Is it some other UI7 issue?

It worked fine. The drivers loaded and I could telnet into the AD2USB from vera (through putty.)

But when I added the device to the serproxy.ports file and then clicked on Serial Port Config in the Vera web, it just froze. Nothing loaded and the screen didn’t change. I could click on any other screen and link but it didn’t like the serproxy.ports file. When I deleted that file then the Serial port Config worked again - although it was empty.

[quote=“DeltaNu1142, post:806, topic:168766”]Yes, PLEG is an app, and yes, you can do that and more with it. I have a PLEG that does exactly that. Think of it as a replacement for scenes, but with more flexibility.
I’m on TapaTalk or I’d link to the forum for it…[/quote]

I didn’t get PLEG but it suddenly started to work all on its own. How does that happen? So I guess I set it up correctly but Vera was having a stroke or something. When I was out of town when the pet sitter disarmed the lights came on and off with the alarm system. So strange that it just started to work with no changes from me.

Thanks for letting us know. Sometimes we just have to take yes for an answer.

PLEG stands for program logic event generator. go ahead and get started on it now, it will change your vera life. make certain you read the pdf at the first page of the really long thread.

Oh, that is why I couldn’t find it. I was searching for PLEG. I had no idea what it meant. Thanks for the info!

[quote=“pentium, post:812, topic:168766”]Thanks for letting us know. Sometimes we just have to take yes for an answer.

PLEG stands for program logic event generator. go ahead and get started on it now, it will change your vera life. make certain you read the pdf at the first page of the really long thread.[/quote]

I got this working! I enabled the relays in the panel config through AD2USB, and then programmed the panel through the GUI in menus *79 and *80… works great. Thanks for your help.

[quote=“djrobx, post:745, topic:168766”]One thing I did notice - if you are using relays, use a fake zone number that doesn’t exist in the cheat sheet. When I used the real zone numbers, I think the old “display based” detection code confused the relay trigger code, and the detections were sloppy and would seemingly get stuck in the tripped state.
With just relays specified along with fake zone numbers (100+), the activity sensors are instant - when I open the door, the action figure in the UI changes, and as soon as I close the door, it goes back to the closed state.[/quote]
This is where I want to get to. I tried fake zone numbers (see attachments), but they did not restore instantly… they appeared to take about as long as when I had the real zone numbers in the cheat sheet. That, and the arm/disarm buttons went away… and now I can’t get them back, even after restoring the cheat sheet. I didn’t really use them anyway, but I don’t understand why they’re gone.

EDIT: They came back after a reload. I’m still curious how to achieve the bold part above! Any ideas?

Hi. I just bought a new ad2usb (my old one died) and no matter what I do, it won’t come up in the Serial Port configuration section of the Vera. I’ve rebooted, removed and reinstalled the plugin, and even reverted the Vera to factory defaults. I can access the ad2usb on my computer so I believe its working. Has anyone come across this before? Although my old one is no longer working, I was able to see it in the Serial Port configuration section so I know its not a USB cable or a dead USB port. Thanks.

Rather than find the post in this thread that details it - over at the manufacturer website we have posted the instructions on how to get new AD2USB detected by the Vera UI’s serial ports configuration. Please see here: alarmdecoder.com » View topic - Veralite shows serial port as Not Available

This is due to a new USB chip from FTDI being used in manufacture.

Thanks,
Kevin
Nu Tech/AlarmDecoder

[quote=“helraiser, post:795, topic:168766”]1. type: lsusb

  • this will list all the vendor and product id for usb ports and adapters on your vera
  • the AD2USB will show up as 0403:6015, 0403:6010 or 0403:60xx. Write this down as it is your “vendor id:product id”
  • if you’re not sure which your AD2USB is, unplug your AD2USB and type “lsusb”. Plug it in and type “lsusb”. See which line was added. That is your adapter’s info.
  1. type: rmmod -f ftdi_sio
  • we are removing the existing ftdi driver for the AD2USB. We will add one specifically for the AD2USB adapter next
  1. type: insmod vendor=0x403 product=0x6015 (replace those with what you wrote down earlier)
  • this loads the driver specifically for your AD2USB adapter
  1. type: echo “ftdi_sio vendor=0x403 product=0x6015” > /etc/modules.d/65-usb-serial-ftdi
  • this allows your vera to autoload drivers for the AD2USB even after reboot or power cycles. the original file just has “ftdi_sio”
  1. type: echo “vendor:0403 product:6015” > /etc/cmh/serproxy.ports
  • this allows vera 3 to see the new adapter as a serial adapter and adds it to the UI.[/quote]

As a relatively noob to Vera, where am I typing this information in? I just bought an AD2USB and interfaced it into my panel (VISTA-20). I’m having issues getting my Vera to find the serial port per the directions. As a result, I stumbled across this thread. Where do I enter these commands?

ssh to your vera and enter them at the shell as root

…using a program like PuTTY.

My current ad2usb is just barely old enough to not need this, but i would like to go ahead and do it now while everyone is talking about it unless that would stop mine from working. Will it?