Can anyone tell me if there is a known method to get the ad2usb recognized by a Vera Edge running ui7? I have one set up and connected to my panel and the edge is not recognizing that there is a serial port. I tried searching but I can’t find anything definitive on this subject.
Thanks
yes, I had the same issue… about 10 posts prior.
Contact Vera support. they need to update the USB drivers for you.
Call them… they will have you enable remote support and do it in a few minutes
So this plug in locked up on me in the worst moment ever. We just left on vacation and my vera is showing connection down. I was using the plug in fine but then I armed my system from the physical panel when I left my home today and now my dashboard shows the connection is down and the status of the alarm panel is “exitdelay”… can anyone help me troubleshoot this problem asap?
Edit: (vacation over) Came home and found my Vista20P powered completely off. Went to work troubleshooting. It seems that my 12V terminals were overloaded, I unplugged one of my panels and the system came back up. It showed an alarm state pointing to one of my windows. As luck would have it (not), one of my magnets fell off while I was gone. It seems that the system triggered the siren and then didn’t have enough power to operate and completely shut down. Lesson learned.
The devices section of the UI 7 interface indicates my plugin 2.45. Under My Apps it indicates the current version is 3.12. I have auto updates on and it doesn’t update to that version.
I noted this commit by Hugh in SVN:
http://code.mios.com/trac/mios_vista-alarm-panel-ad2usb/changeset?reponame=&new=83%40trunk%2FL_VistaAlarmPanel1.lua&old=82%40trunk%2FL_VistaAlarmPanel1.lua
Which includes an update for the VERSION var from 2.45 to 3.89. Then I looked at the diff between r77 and r83 and didn’t see any other version changes:
http://code.mios.com/trac/mios_vista-alarm-panel-ad2usb/changeset?old_path=%2Ftrunk&old=77&new_path=%2Ftrunk&new=83
So questions:
-
Where is the UI under My Apps getting the 3.12 from? Is that not tied to the VERSION variable in the code, i.e., it is specific to Apps not the code itself?
-
Am I correct in assuming that that is inaccurate, and the released version would still indicate 2.45 until this update to v3.89 is released? If it is inaccurate, where is the 3.12 coming from and should it be filed as a bug to support?
EDIT: looking at another thread it appears other people are on 3.0+/ I guess another question would be, why am I stuck on 2.45 even if I have auto update checked? Back on UI 5 I manually updating to a beta version via SSH but I’d prefer to avoid that and fix it properly.
TIA
The joys of power-limited aux power terminals… At least it didn’t fry your panel…
The aux power terminals are limited to 600ma… If you are using them to power all your keypads/AUIs, you can easily overload them… and, as you discovered, bad things happen…
Ideally, you should only be powering zone devices (a single PIR uses 10-30ma), zone expanders (4219 uses 30ma) and a single keypad (a 6160 150ma, 6160RF uses 180ma, don’t try to power a TuxWifi as it uses 310ma)…
Additional keypads (such as the TuxWifi) and other non essential devices should be powered from a supplementary power supply (with the ground terminals interconnected)… My preferred choice is a 12VDC 5AH power supply designed for access control use… It provides up to 5000ma and can have it’s own backup battery connected…
[quote=“cybrmage, post:945, topic:168766”]Ideally, you should only be powering zone devices (a single PIR uses 10-30ma), zone expanders (4219 uses 30ma) and a single keypad (a 6160 150ma, 6160RF uses 180ma, don’t try to power a TuxWifi as it uses 310ma)…
Additional keypads (such as the TuxWifi) and other non essential devices should be powered from a supplementary power supply (with the ground terminals interconnected)… My preferred choice is a 12VDC 5AH power supply designed for access control use… It provides up to 5000ma and can have it’s own backup battery connected…[/quote]
Ya… I’ve installed over 500 vista 15p’s but I’ve never done a system as advanced as what I have in my home. I have 1 6150RF, 2 6160’s, 2 6270’s, and 6 motion detectors. I’d never worried about power requirements on the standard 2 panel, 2 motion system. I’m guessing I was just lucky up to this point. I’ve unplugged the 2 6270’s until I can get a stand alone power supply.
Just to comment on the power usage - the AD2USB only uses 30ma itself, so it is pretty safe to use in conjunction with most add-ons, but yes the bus can become easily overloaded if you have too many keypads for instance.
In your case, I would keep the RF keypad for the radio, and ditch one or two of the other ones if convenient. Since the Vera makes things so easy to arm/disarm maybe some of the keypads have become redundant.
My plugin stopped working. It was working OK over the network when andrei_mcv did the changes to the plugin for network awareness but I mistakenly left autoupdate enabled so when andrei reverted the plugin I lost my ability to use the system. Is the new plugin in beta? Can I get a copy of the kua files that enable networking? I’d be happy to help with testing. The ad2usb is working fine from the RPi with the Alarm Decoder software web interface.
There is an issue with this plugin when the panel goes into ready, it should clear all faulted zones so that you do not have to wait for a timeout. This will help alleviate zone restores based on the TTL parameter (which is a hack). Ready realy means that ALL ZONES ARE GOOD, so they should all be restored in the UI when the status is “Ready”.
Kevin, I’ve seen this since my recent upgrade to UI7… but cannot find anything on the forums to get this resolved:
“can’t detect device”
but I can toggle the alarm state on either of two partitions?
Got me, must be a bug in the UI or the plugin - not the developer so I can’t say one way or the other. If you have specific AD2 questions, I can answer them no problem. Plugin issues you’ll have to direct toward Vera as I am doing as well.
Go to the variables tab for the device and set CommFailure and CommFailureTime to 0 and see if it comes back. I’ve had these variables not set before and experienced the issue on that device.
Well, I couldn’t get it fixed… I contacted Vera and they took care of it.
Thanks Vera Team!
I’m using version 2.45 of the Ademco Vista Alarm Panel plugin with an AlarmDecoder ad2usb and Veralite UI7. I’ve configured it using minicom and a Linux computer to have the correct device address for my alarm panel (31, it’s an FA148C which is mostly the same as a Vista 15P). I receive messages from my alarm panel when I use minicom.
But when transferring the USB device to my Veralite, it is not detected. I made the changes described earlier in this thread to add the correct USB device numbers to the USB serial driver. And I also replaced the Start_serproxy.sh file with the script at forum.micasaverde.com/index.php/topic,7266.msg209964.html#msg209964.
In the serial port configuration in the Web interface, the ttyUSB0 device shows up. It had 9600 baud which was wrong, and was not assigned to a device, so I assigned it to “Ademco Vista Alarm Panel” (also tried assigning it to “Ademco Vista Partition 1”) and changed the baud rate to 115200. When I run “ps aux” on the Vera I can see the serproxy and ser2net processes running:
12294 root 900 S /usr/bin/serproxy 127.0.0.1 127.0.0.1 35038308 /dev/ttyUSB0
12328 root 1676 S /bin/sh -c ser2net -n -C "3482:raw:0:/dev/ttyUSB0:115200 1STOPBIT NONE"
12329 root 800 S ser2net -n -C 3482 raw 0 /dev/ttyUSB0 115200 1STOPBIT
However the Vera Web interface shows “Ademco Vista Alarm Panel[7] : Failed to open IO Port” at the top in a blue bar and “Can’t Detect Device” in a red one below the device itself.
I’ve notice recently that my VERA edge running u17 v 1.7.1320 recently created 12 motion sensors for my AD2USB alarm interface.
It has my device id_parent pointing at my Ademco panel.
All of my devices are wireless for this panel. Are these just ghost devices that are now being created to support the hardwired zones?
Which zones do they represent? (VERA named them _Motion Sensor to _Motion Sensor 11)
[quote=“BulldogLowell, post:953, topic:168766”]Well, I couldn’t get it fixed… I contacted Vera and they took care of it.
Thanks Vera Team![/quote]
BulldogLowell - do you know who you worked with at Vera? The tech I’ve been emailing isn’t getting me anywhere…
[quote=“terminus, post:954, topic:168766”]I’m using version 2.45 of the Ademco Vista Alarm Panel plugin with an AlarmDecoder ad2usb and Veralite UI7. I’ve configured it using minicom and a Linux computer to have the correct device address for my alarm panel (31, it’s an FA148C which is mostly the same as a Vista 15P). I receive messages from my alarm panel when I use minicom.
But when transferring the USB device to my Veralite, it is not detected. I made the changes described earlier in this thread to add the correct USB device numbers to the USB serial driver. And I also replaced the Start_serproxy.sh file with the script at forum.micasaverde.com/index.php/topic,7266.msg209964.html#msg209964.
In the serial port configuration in the Web interface, the ttyUSB0 device shows up. It had 9600 baud which was wrong, and was not assigned to a device, so I assigned it to “Ademco Vista Alarm Panel” (also tried assigning it to “Ademco Vista Partition 1”) and changed the baud rate to 115200. When I run “ps aux” on the Vera I can see the serproxy and ser2net processes running:
12294 root 900 S /usr/bin/serproxy 127.0.0.1 127.0.0.1 35038308 /dev/ttyUSB0
12328 root 1676 S /bin/sh -c ser2net -n -C "3482:raw:0:/dev/ttyUSB0:115200 1STOPBIT NONE"
12329 root 800 S ser2net -n -C 3482 raw 0 /dev/ttyUSB0 115200 1STOPBIT
However the Vera Web interface shows “Ademco Vista Alarm Panel[7] : Failed to open IO Port” at the top in a blue bar and “Can’t Detect Device” in a red one below the device itself.[/quote]
My posted script should not be needed. As of 1.7.1419 I no longer have to make or reapply my script modifications. This was the first release I encountered that actually fixed the issue for me.
Associating it with the panel, not the partition, is correct. Baud rate is also correct. Unfortunately this means I can’t provide much help. To be sure, the keypad address 31 is not in use by anything else?
Re: version 2.45, I contacted support as that version was old, not sure why Dashboard/Devices said that. They told me to ignore that version and rely on the one in the Apps interface. Based on changes in the plugin, I believe they are correct.
Upgraded to 1.7.1419 plugin v3.12. Now I’m getting notifications from every door/entry sensor each time it is triggered, although I’ve never configured any notifications for those sensors. Anybody else experiencing this?
Hi all,
I’ve looked everywhere for an answer to this question but am coming up blank. Is it possible to trigger the alarm/siren (Ademco 10SE) with sensors other than those connected to the panel? For example, I have Fibaro magnetic door sensors, and I would love to be able to have the alarm go off if one of these is faulted. I thought of maybe creating a scene so that, when the Fibaro faulted, the scene pressed a lettered key (A,B,C,D) for the panic mode - setting off the alarm. Unfortunately, these buttons don’t appear as selectable options on the partition when I’m creating a scene.
Can anyone help?
Cheers,
Stibbzy.
You should have the option for letter key press in the advanced tab when creating a new scene. I’m on UI5 but I assume UI7 is the same