Ok first day with AD2USB and Veralite. Sooooo confused. I have everything working but something is concerning me. I stored my PIN and set “securestore” to 1 so it should require a PIN for each command. It does! Problem is all you have to do is go and change “securestore” back to 0 and suddenly it doesn’t require a PIN anymore.
I guess my concern is that if someone got into my getvera account they would be able to disarm my alarm without even knowing the PIN. Is there a way to stop this?
Also, is there a way to only show certain buttons on the dashboard. For example, I never use “night-stay” and would rather it just not be there. Same thing goes for using Home Buddy, it shows way too many buttons.
I posted this in the Vera Alert section, but I think this is probably an issue with the AD2USB. I am trying to have a verbal announcement each time one of the alarm sensors is tripped in my house. For example, when the front door is opened, there would be an announcement stating “Front door open”. I have my Honeywell Ademco Vista alarm panel connected to my Vera Lite via an AD2USB with the Honeywell Ademco Vista Alarm Panels Plugin on the Vera. The senors all work well in the Vera. Now, I am trying to use Vera Alerts to send an announcement to an Android tablet that will be permanently mounted in the house. I have installed the Vera Alerts Plugin on the Vera and the Android app on the tablet. The plan is to have one scene with triggers for each sensor that will send a notification when the sensor is tripped. The notification is sent using the Luup event in the trigger with the following code:
I have created the scene and some test triggers. The notification gets sent, but the issue is that it repeats approximately every 4 seconds until the sensor is closed. The Message Repeat Count in the Android app is set to 0, so I do not think it is the cause. Plus, I have tried making a test trigger with an Z-wave appliance module as the trigger (instead of an alarm sensor) and it makes the announcement only once. So my thoughts are that the sensor/panel is repeatedly sending an open signal until it is closed, which is repeatedly triggering; the announcements stop within seconds of the sensor being closed. I saw that in April 2013 there where some posts in this thread that some people had similar issues when version 3.00 of the plugin came out. The main panel plugin states I am running plugin version 2.45 (though when I go to my apps it states 3.10). My TTL setting is 60.
Did people get this fixed? Any suggestions on how to fix this? I would like Vera Alerts to make only one announcement when an alarm sensor is tripped.
I had this same issue using the mcv notifications. Basically the notification was telling me the door was open, so repeated non stop until the door was closed. I fixed this by setting up pleg so that I was notified only on the door opening event instead of being notified based on the state of the sensor. Unless I’m missing something, I don’t think this is an issue with the plugins–I think they’re doing what you’ve asked them to, which is to notify you when the sensor is tripped. Not intuitive, but makes sense when you think about it.
Same here, switched it to pleg and the problem went away. I had forgotten how annoying that was, so I added this to save you some time and just look for a good example in the pleg documenation or on that thread.
tb001 or pentium, thank you for the responses. I am still new to PLEG. Would you be so kind as to explain exactly how you setup the notifications using PLEG?
I am not certain what to assume about your experience with pleg, but this can get you started with something very simple and you can go from there. If you don’t already have the app, then get it. There is a nominal fee and it is worth every penny.
Create a trigger similar to my tBackDoorMotion. It will ask for you a device and then similar to a scene setup.
tBackDoorMotion Back Door Motion armed is tripped
then go to conditions and create a condition to trigger off of the trigger you just created
cBackDoorMotion No tBackDoorMotion
then, similar to a scene, you go to actions and you will see that cBackDoorMotion already has its own line and it is just waiting for you to add actions. click edit and it will bring up a screen similar to the scene on the advanced tab. In my example i am using prowl to send me a not, but it would be just as easy to add a veralert.
Actions for Condition: cBackDoorMotion
Device Actions:
Immediate
Device Action Arguments
Push Notification SendProwlNotification Event=Back Door Motion Description=Back Door Motion Priority=-1 URL=
[quote=“pentium, post:766, topic:168766”]I am not certain what to assume about your experience with pleg, but this can get you started with something very simple and you can go from there. If you don’t already have the app, then get it. There is a nominal fee and it is worth every penny.
Create a trigger similar to my tBackDoorMotion. It will ask for you a device and then similar to a scene setup.
tBackDoorMotion Back Door Motion armed is tripped
then go to conditions and create a condition to trigger off of the trigger you just created
cBackDoorMotion No tBackDoorMotion
then, similar to a scene, you go to actions and you will see that cBackDoorMotion already has its own line and it is just waiting for you to add actions. click edit and it will bring up a screen similar to the scene on the advanced tab. In my example i am using prowl to send me a not, but it would be just as easy to add a veralert.
Actions for Condition: cBackDoorMotion
Device Actions:
Immediate
Device Action Arguments
Push Notification SendProwlNotification Event=Back Door Motion Description=Back Door Motion Priority=-1 URL=[/quote]
Thank you for your help. I got it working with PLEG and it makes only one announcement! To make it work with Vera Alerts I just put the code listed in my earlier post into the Luup tab in the PLEG Action.
SO forgive me for cross posting but I’m not getting much help in my own thread and it seems like there are a lot of knowledgeable people replying to this topic.
I’m not sure where the functionality is lacking. I’m using AuthomationHD on my phone and when I hit the panic buttons (fire,police,medical) it gives me a warning, I accept the warning and nothing happens. Looking at my dashboard, I’m given this message “Vista Alarm Panel : RequestPanicMode not implemented.” How can I get these buttons to work? I can trigger a panic from buttons A, B, and C on my micasa dashboard.
I spoke with the AuthomationHD creator and he said that panics are implemented in his program and that it works with his DSC panel. Is the implementation different with AD2USB?
I’m honestly not interesting in changing programs just for the panic. AuthomationHD has been a dream to use and I have it on multiple devices. If this is the only hiccup with the program, then I’ll gladly just accept it and move on. I’m just trying to make sure I’m not doing something wrong…
It states that they fully support now Honeywell systems. Instead of having to go with the distance limitation of USB, the EVL-3 could go over IP and make many peoples’ lives easier.
It states that they fully support now Honeywell systems. Instead of having to go with the distance limitation of USB, the EVL-3 could go over IP and make many peoples’ lives easier.[/quote]
There is a plug in avaliable for this now in the app store
Vera Dashboard reporting “Vista Alarm Panel: Connection Down” after installing Vista Plug-in.
Seems as if my “Vista Alarm Panel” device is not working.
Also Serial Port Configuration never worked.
History:
Have been using VeraLite for over 8 months with no issues.
Have 3 devices assigned with no issues (Light switch, Garage Door tilt detector, Water leak detector)
Have been using existing ADT Pulse system for over 8 months with no issues.
Have Vista 20P with 6160V & 6150 keypads
Recently purchased AD2USB so I could use this plugin to see my alarm devices within Vera.
On my Vista 20P, ADT installed a 5800TM & 5881EN for wireless access.
From Honeywell?s documentation:
5800TM defaults to device address 28
5881EN defaults to device address 00 (not sure if this is the 8, 16 or 40 zone version)
Using the 1-3 shortcut, I was able to verify the keypad address for my 6160V & 6150 keypads.
6160V ? device address 16
6150 ? device address 17
I checked Vista 20P values in *192 ? *196 (keypads 4-8 = device addresses 19-23),
all values returned were 00.
I have two 4-button keyfobs programmed in zones 50-57.
All 8 hardwired zones are used. (1-8)
Current:
When I programmed my third keypad (ad2USB), I used the unassigned keypad default address 18 (via *191).
After wiring AD2USB to the Vista 20P panel I was able to successfully connect the AD2USB to my desktop.
Using my installer code I was able to use the Virtual keypad UI program without issues.
Virtual keypad appeared and I was able to arm and disarm my alarm system.
I also verified it was set to address 18 and was using the recommended baud rate.
Also green led on AD2USB is blinking normally.
Problem occurred after I connected to Vera and installed the Vera Vista Alarm Plugin.
Verified number of Partitions set to 1
Changed TTL to 30
Changed keypad device address to 16, 17,18
These are three issues:
Vera dashboard is reporting several errors:
Device not responding.
They can be disconnected, out of range, or the batteries should be replaced. 1 devices are no longer connected
No devices under serial port configuration
Also tried moving AD2USB to device address 19, same errors occurred.
It states that they fully support now Honeywell systems. Instead of having to go with the distance limitation of USB, the EVL-3 could go over IP and make many peoples’ lives easier.[/quote]
Pseudomizer,
It sounds like EVL-3 support has been added with a new plugin. However, if you already have an AD2USB. I recently modified the AD2USB plugin to support ethernet / network connections using a raspberry pi as a bridge. See this thread for more details:
Just a note from us at Nu Tech/AlarmDecoder - if you are looking to talk to your AD2 device over the network, our ser2sock is compatible with the ser2net connection if you run ser2sock in raw device mode (-0 (zero) from command line)
ABSOLUTELY LOVE this plugin, and wanted to thank all involved in the development and support of it.
I also wanted to ask, I have some Everspring water sensors in my setup, and was hoping to get them communicating with the ADEMCO alarm panel to set off the siren/alarm if any of them are tripped.
Hello everyone, I am a new user of Vera and just got the VeraLite last week. Today I installed the AD2USB for my Ademco Vista 15. My Vera is running 1.7.318 will not see the AD2USB device. I tried to reload LUUP under serial port configuration with no luck. I have been working on this for hours with no progress and hope someone may know what I should do. I installed the USB driver on my laptop and connected and communicated fine with my alarm panel via the AD2USB with no issues. Just I don’t know why my VeraLite won’t see it. I installed the Ademco app 5 times with no change.