It’s definitely a plugin issue - AD2USB only sends what it is asked to send
I received my AD2USB unit in the mail today. I changed the address to 31 since my alarm panel is SE. I also did the procedure to change the driver for the new USB chip in the AD2USB. At one time I was able to arm and disarm my alarm system through vera and also could get notifications on open zones. I’m now getting the message in Vera “Vista Alarm Panel: Connection Down”. At this time I can only arm & disarm the alarm. I cannot get information on open zones. Any help to trouble shoot this problem would
be greatly appreciated.
[quote=“MikeH, post:842, topic:168766”]I received my AD2USB unit in the mail today. I changed the address to 18 since my alarm panel is SE. Everything appears to be working except every once in
a while a get the following message in Vera “Vista Alarm Panel: Connection Down”. When I do a Reload in UI5 it fixes it. Is this suppose to happen?[/quote]
Just so we don’t spread misinformation - SE panels are the UNADDRESSABLE variety where you would set it to 31 - you must mean you have a P 
No I have the SE model. I should have stated that I changed the address to 31. Any idea why I would get the connection down message?
No idea, sorry
HI EVERYONE, IVE BEEN DEALING WITH THE SAME EXACT SITUATION …
THE INSTRUCTIONS ARE STARTING TO MAKE SENSE BUT IM STILL LOST AND MY QUESTION IS… WHEN YOU SAY “TYPE” — WHERE DO I TYPE???
- 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.
- 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
- type: insmod vendor=0x403 product=0x6015 (replace those with what you wrote down earlier)
- this loads the driver specifically for your AD2USB adapter
- 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”
- 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.
Hi djrobx and anyone else who knows,
Sorry it took so long, but I followed your advice. Here’s a sample while logged into ad2usb through my verlite. First tests are unarmed and you can see the relays fire on open and close. But armed, the relay does not. However, the window relay triggers while armed. I also notices that the fromt door only triggers the REL alerts and not the EXP alert. Not sure what that means.
Again, Thanks for the help!
-Mike
[code]Open and Close Window
[1000000110000000----],008,[f700000f1008001c28020000000000]," DISARMED CHIME Ready to Arm "
!EXP:07,06,01
!REL:15,02,01
[0000030110000000----],014,[f700000f1014030028020000000000],“FAULT 14 "
0000000110000000----],008,[f700000f1008000c28020000000000],” DISARMED CHIME Hit * for faults"
!EXP:07,06,00
!REL:15,02,00
[1000000110000000----],008,[f700000f1008001c28020000000000]," DISARMED CHIME Ready to Arm "
Open and Close Front Door
[1000000110000000----],008,[f700000f1008001c28020000000000]," DISARMED CHIME Ready to Arm "
!REL:12,01,01
[0000030110000000----],001,[f700000f1001030028020000000000],“FAULT 01 "
!REL:12,01,00
[1000000110000000----],008,[f700000f1008001c28020000000000],” DISARMED CHIME Ready to Arm "
Open and Close Front Door while ARMED
[0010000110000000----],008,[f700000f1008008c28020000000000],"ARMED STAY "
=== This is where I opened my door ===
[0011050110000000----],008,[f700000f1008058c28020000000000],“DISARM SYSTEM or alarm occurs "
[0011050110000000----],008,[f700000f1008058c28020000000000],“DISARM SYSTEM or alarm occurs "
[0001010110000000----],008,[f700000f1008010c28020000000000],” DISARMED CHIME Hit * for faults”
!REL:12,01,00
Open Window while ARMED
[0010000110000000----],008,[f700000f1008008c28020000000000],"ARMED STAY "
!EXP:07,06,01
!REL:15,02,01
[0011000111100000----],014,[f700000f101400802b020000000000],"ALARM 14 "
!EXP:07,06,01
[0011000111100000----],014,[f700000f101400802b020000000000],"ALARM 14 "
[0001010111000000----],014,[f700000f101401002a020000000000],"ALARM 14 "
[0001000110000000----],0ca,[f700000f10ca200028020000000000],"Alarm Canceled
–[/code]
@mcvflorin I’ve noticed the APPS- MY TABS in the UI shows the plugin as 3.10 but my Vera UI shows 2.45
Have I missed an update or two somewhere?
Just purchased a Vera Edge and AD2USB… I have my AD2USB working correctly from my PC and plugged it into the Edge and installed the plug-in. I was unable to get to the serial port and found the instructions on page 53. When I enter lsusb in step one, I don’t get the resulted mention in the post. I get the same info with or without the AD2USB connected…
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Not sure what to do at this point… Any help would be greatly appreciated…
Thx,
JC
Does anything related to it show up when you do a ‘dmesg’ from the command line?
Not sure… Here is the result of that command…
[ 17.990000]
[ 17.990000] === pAd = c064f000, size = 626016 ===
[ 17.990000]
[ 18.010000] ← RTMPAllocTxRxRingMemory, Status=0
[ 18.020000] ← RTMPAllocAdapterBlock, Status=0
[ 18.030000] AP Driver version-2.7.1.6
[ 18.060000] u32 classifier
[ 18.070000] input device check on
[ 18.070000] Actions configured
[ 18.100000] Mirror/redirect action on
[ 18.200000] fuse init (API version 7.22)
[ 18.220000] usbcore: registered new interface driver cdc_acm
[ 18.230000] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[ 18.240000] Loading modules backported from Linux version master-2014-01-23-0-g62c147d
[ 18.260000] Backport generated by backports.git backports-20140124-0-g1256d3e
[ 18.290000] nf_conntrack version 0.5.0 (1980 buckets, 7920 max)
[ 18.310000] Netfilter messages via NETLINK v0.30.
[ 18.320000] usbcore: registered new interface driver ums-alauda
[ 18.340000] usbcore: registered new interface driver ums-cypress
[ 18.350000] usbcore: registered new interface driver ums-datafab
[ 18.370000] usbcore: registered new interface driver ums-freecom
[ 18.380000] usbcore: registered new interface driver ums-isd200
[ 18.400000] usbcore: registered new interface driver ums-jumpshot
[ 18.410000] usbcore: registered new interface driver ums-karma
[ 18.420000] usbcore: registered new interface driver ums-sddr09
[ 18.440000] usbcore: registered new interface driver ums-sddr55
[ 18.450000] usbcore: registered new interface driver ums-usbat
[ 18.470000] usbcore: registered new interface driver usbserial
[ 18.480000] usbcore: registered new interface driver usbserial_generic
[ 18.500000] usbserial: USB Serial support registered for generic
[ 18.540000] xt_time: kernel timezone is -0000
[ 18.550000] usbcore: registered new interface driver belkin_sa
[ 18.570000] usbserial: USB Serial support registered for Belkin / Peracom / GoHubs USB Serial Adapter
[ 18.610000] cfg80211: Calling CRDA to update world regulatory domain
[ 18.620000] usbcore: registered new interface driver cp210x
[ 18.640000] cfg80211: World regulatory domain updated:
[ 18.650000] cfg80211: DFS Master region: unset
[ 18.650000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 18.670000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 18.690000] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 18.700000] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 18.720000] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz), (300 mBi, 2000 mBm)
[ 18.730000] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (300 mBi, 2000 mBm)
[ 18.750000] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm)
[ 18.760000] usbserial: USB Serial support registered for cp210x
[ 18.800000] usbcore: registered new interface driver ftdi_sio
[ 18.820000] usbserial: USB Serial support registered for FTDI USB Serial Device
[ 18.840000] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 18.860000] usbcore: registered new interface driver keyspan
[ 18.870000] usbserial: USB Serial support registered for Keyspan - (without firmware)
[ 18.890000] usbserial: USB Serial support registered for Keyspan 1 port adapter
[ 18.900000] usbserial: USB Serial support registered for Keyspan 2 port adapter
[ 18.920000] usbserial: USB Serial support registered for Keyspan 4 port adapter
[ 18.970000] usbcore: registered new interface driver mct_u232
[ 18.980000] usbserial: USB Serial support registered for MCT U232
[ 19.000000] ctnetlink v0.93: registering with nfnetlink.
[ 19.010000] usbcore: registered new interface driver pl2303
[ 19.020000] usbserial: USB Serial support registered for pl2303
[ 19.040000] PPP generic driver version 2.4.2
[ 19.050000] NET: Registered protocol family 24
[ 19.080000] usbcore: registered new interface driver option
[ 19.090000] usbserial: USB Serial support registered for GSM modem (1-port)
[ 27.130000] device eth0.1 entered promiscuous mode
[ 27.140000] device eth0 entered promiscuous mode
[ 27.150000] br-lan: port 1(eth0.1) entered forwarding state
[ 27.160000] br-lan: port 1(eth0.1) entered forwarding state
[ 28.130000] IPv6: ADDRCONF(NETDEV_CHANGE): eth0.1: link becomes ready
[ 29.160000] br-lan: port 1(eth0.1) entered forwarding state
[ 30.000000] RX DESC a6f68000 size = 2048
[ 30.050000] RTMP_TimerListAdd: add timer obj c06b8990!
[ 30.060000] RTMP_TimerListAdd: add timer obj c0657070!
[ 30.070000] RTMP_TimerListAdd: add timer obj c0656c64!
[ 30.080000] RTMP_TimerListAdd: add timer obj c0657040!
[ 30.090000] RTMP_TimerListAdd: add timer obj c06573e8!
[ 30.100000] RTMP_TimerListAdd: add timer obj c0657138!
[ 30.110000] RTMP_TimerListAdd: add timer obj c0657168!
[ 30.120000] RTMP_TimerListAdd: add timer obj c0657328!
[ 30.130000] RTMP_TimerListAdd: add timer obj c0657358!
[ 30.140000] RTMP_TimerListAdd: add timer obj c068f2fc!
[ 30.150000] RTMP_TimerListAdd: add timer obj c068f418!
[ 30.160000] RTMP_TimerListAdd: add timer obj c068f328!
[ 30.170000] RTMP_TimerListAdd: add timer obj c068685c!
[ 30.180000] RTMP_TimerListAdd: add timer obj c0654530!
[ 30.200000] RTMP_TimerListAdd: add timer obj c0686570!
[ 30.350000] APSDCapable[0]=0
[ 30.360000] APSDCapable[1]=0
[ 30.360000] APSDCapable[2]=0
[ 30.370000] APSDCapable[3]=0
[ 30.370000] APSDCapable[4]=0
[ 30.380000] APSDCapable[5]=0
[ 30.390000] APSDCapable[6]=0
[ 30.390000] APSDCapable[7]=0
[ 30.400000] APSDCapable[8]=0
[ 30.400000] APSDCapable[9]=0
[ 30.410000] APSDCapable[10]=0
[ 30.410000] APSDCapable[11]=0
[ 30.420000] APSDCapable[12]=0
[ 30.430000] APSDCapable[13]=0
[ 30.430000] APSDCapable[14]=0
[ 30.440000] APSDCapable[15]=0
[ 30.650000] Key1Str is Invalid key length(0) or Type(0)
[ 30.660000] Key2Str is Invalid key length(0) or Type(0)
[ 30.670000] Key3Str is Invalid key length(0) or Type(0)
[ 30.680000] Key4Str is Invalid key length(0) or Type(0)
[ 30.710000] 1. Phy Mode = 9
[ 30.710000] 2. Phy Mode = 9
[ 30.720000] nvram_buffer: =d4:21:22:c0:2a:ae
[ 30.730000] Assigned MAC: =d4:21:22:c0:2a:af
[ 30.740000] E2PROM: D0 target power=0xff20
[ 30.740000] E2PROM: 40 MW Power Delta= 0
[ 30.750000] 3. Phy Mode = 9
[ 30.760000] RTMP_TimerListAdd: add timer obj c065412c!
[ 30.770000] AntCfgInit: primary/secondary ant 0/1
[ 30.770000] Initialize RF Central Registers for E2 !!!
[ 30.790000] Initialize RF Central Registers for E3 !!!
[ 30.800000] Initialize RF Channel Registers for E2 !!!
[ 30.810000] Initialize RF Channel Registers for E3 !!!
[ 30.820000] Initialize RF DCCal Registers for E2 !!!
[ 30.830000] Initialize RF DCCal Registers for E3 !!!
[ 30.840000] D1 = 0, D2 = 12, CalCode = 28 !!!
[ 30.850000] RT6352_Temperature_Init : BBPR49 = 0x0
[ 30.860000] RT6352_Temperature_Init : TemperatureRef25C = 0xfffffff6
[ 30.870000] Current Temperature from BBP_R49=0xfffffffe
[ 30.890000] TX BW Filter Calibration !!!
[ 31.000000] RX BW Filter Calibration !!!
[ 31.230000] LOFT Calibration Done!
[ 31.240000] IQCalibration Start!
[ 31.260000] IQCalibration Done! CH = 0, (gain= 1, phase= 2)
[ 31.270000] IQCalibration Start!
[ 31.290000] IQCalibration Done! CH = 1, (gain= 1, phase=3d)
[ 31.300000] TX IQ Calibration Done!
[ 31.340000] MCS Set = ff ff 00 00 00
[ 31.390000] RTMP_TimerListAdd: add timer obj c0686e14!
[ 31.440000] Main bssid = d4:21:22:c0:2a:af
[ 31.450000] <==== rt28xx_init, Status=0
[ 31.550000] 0x1300 = 00064380
[ 32.610000] RX DESC a6f68000 size = 2048
[ 32.670000] RTMP_TimerListAdd: add timer obj c06b8990!
[ 32.680000] RTMP_TimerListAdd: add timer obj c0657070!
[ 32.690000] RTMP_TimerListAdd: add timer obj c0656c64!
[ 32.700000] RTMP_TimerListAdd: add timer obj c0657040!
[ 32.710000] RTMP_TimerListAdd: add timer obj c06573e8!
[ 32.720000] RTMP_TimerListAdd: add timer obj c0657138!
[ 32.730000] RTMP_TimerListAdd: add timer obj c0657168!
[ 32.740000] RTMP_TimerListAdd: add timer obj c0657328!
[ 32.750000] RTMP_TimerListAdd: add timer obj c0657358!
[ 32.760000] RTMP_TimerListAdd: add timer obj c068f2fc!
[ 32.770000] RTMP_TimerListAdd: add timer obj c068f418!
[ 32.780000] RTMP_TimerListAdd: add timer obj c068f328!
[ 32.790000] RTMP_TimerListAdd: add timer obj c068685c!
[ 32.800000] RTMP_TimerListAdd: add timer obj c0654530!
[ 32.810000] RTMP_TimerListAdd: add timer obj c0686570!
[ 32.950000] APSDCapable[0]=0
[ 32.960000] APSDCapable[1]=0
[ 32.960000] APSDCapable[2]=0
[ 32.970000] APSDCapable[3]=0
[ 32.970000] APSDCapable[4]=0
[ 32.980000] APSDCapable[5]=0
[ 32.990000] APSDCapable[6]=0
[ 32.990000] APSDCapable[7]=0
[ 33.000000] APSDCapable[8]=0
[ 33.000000] APSDCapable[9]=0
[ 33.010000] APSDCapable[10]=0
[ 33.020000] APSDCapable[11]=0
[ 33.020000] APSDCapable[12]=0
[ 33.030000] APSDCapable[13]=0
[ 33.030000] APSDCapable[14]=0
[ 33.040000] APSDCapable[15]=0
[ 33.250000] Key1Str is Invalid key length(0) or Type(0)
[ 33.260000] Key2Str is Invalid key length(0) or Type(0)
[ 33.270000] Key3Str is Invalid key length(0) or Type(0)
[ 33.280000] Key4Str is Invalid key length(0) or Type(0)
[ 33.310000] 1. Phy Mode = 9
[ 33.310000] 2. Phy Mode = 9
[ 33.320000] nvram_buffer: =d4:21:22:c0:2a:ae
[ 33.330000] Assigned MAC: =d4:21:22:c0:2a:af
[ 33.340000] E2PROM: D0 target power=0xff20
[ 33.350000] E2PROM: 40 MW Power Delta= 0
[ 33.350000] 3. Phy Mode = 9
[ 33.360000] RTMP_TimerListAdd: add timer obj c065412c!
[ 33.370000] AntCfgInit: primary/secondary ant 0/1
[ 33.370000] Initialize RF Central Registers for E2 !!!
[ 33.390000] Initialize RF Central Registers for E3 !!!
[ 33.400000] Initialize RF Channel Registers for E2 !!!
[ 33.410000] Initialize RF Channel Registers for E3 !!!
[ 33.420000] Initialize RF DCCal Registers for E2 !!!
[ 33.430000] Initialize RF DCCal Registers for E3 !!!
[ 33.440000] D1 = -1, D2 = 11, CalCode = 28 !!!
[ 33.450000] RT6352_Temperature_Init : BBPR49 = 0x0
[ 33.460000] RT6352_Temperature_Init : TemperatureRef25C = 0xfffffff6
[ 33.470000] Current Temperature from BBP_R49=0xfffffffe
[ 33.490000] TX BW Filter Calibration !!!
[ 33.610000] RX BW Filter Calibration !!!
[ 33.830000] LOFT Calibration Done!
[ 33.840000] IQCalibration Start!
[ 33.860000] IQCalibration Done! CH = 0, (gain= 1, phase= 2)
[ 33.870000] IQCalibration Start!
[ 33.890000] IQCalibration Done! CH = 1, (gain= f, phase=3d)
[ 33.900000] TX IQ Calibration Done!
[ 33.940000] MCS Set = ff ff 00 00 00
[ 33.990000] RTMP_TimerListAdd: add timer obj c0686e14!
[ 34.040000] Main bssid = d4:21:22:c0:2a:af
[ 34.050000] <==== rt28xx_init, Status=0
[ 34.050000] 0x1300 = 00064300
[ 37.790000] device ra0 entered promiscuous mode
[ 37.800000] br-lan: port 2(ra0) entered forwarding state
[ 37.810000] br-lan: port 2(ra0) entered forwarding state
[ 39.810000] br-lan: port 2(ra0) entered forwarding state
root@MiOS_45002554:~#
Can we get one without the ad2usb plugged in and one with the ad2usb plugged in? Just to see if there’s an apparent difference - not seeing what I would expect to see, which leads me to believe that the driver potentially doesn’t exist on the Edge
I think I saw another thread that someone said the usb port is not yet working on the edge. Contact support maybe
ok… I ran the dmesg with and without the AD2USB plugged into the Vera Edge. I compared the files and the only difference is this line…
[41931.300000] usb 2-1: new full-speed USB device number 2 using ohci-platform
Just a quick question. I just ordered a Vista 20p alarm panel. I will be using just one partition. When I set-up AD2USB plugin do I just enter 1 partition in the
settings?
I have a 1 in numpartitions. Been working a long time.
[quote=“Vandamme23, post:854, topic:168766”]ok… I ran the dmesg with and without the AD2USB plugged into the Vera Edge. I compared the files and the only difference is this line…
[41931.300000] usb 2-1: new full-speed USB device number 2 using ohci-platform[/quote]
Well, it looks like they haven’t gotten that working for the Edge yet - bummer.
So I have a Vera 2 running UI1 that has been running my AD2USB Ademco Vista 10SE for a while…
I just got a Vera Edge. Based on what I’m reading, I should leave the Vera 2 running the plug-in for now and not try and move it over to the new Edge, correct?
That would be my recommendation until the Edge is mature enough for the product.
Ugh. Thanks Kevin. I guess that’s what I get for trying to be on the cutting edge…And also why I’ve been hesitant to upgrade from UI 1.0 (a bit excessive, but if it ain’t broke…)