Inspired wrote:

berkinet wrote:...running the plugin in Advanced mode, the zone state will change from clear to fault even if the system is armed.

My system does not behave this way. If does not fault while waiting for the disarm code. Is there a way to compare 20P firmware revisions?

You would have to contact an Ademco specialist on this issue. I did check with Sean at NuTech and his experience is the same as mine. Are you watching the data stream on the ad2usb to see if there is a fault message from the faulted zone, or just looking for the zone device to change in Indigo? If you haven't tried watching the raw stream, give that a shot and see what you get.

Inspired also wrote:Another thing I noticed in your release history is that you fixed an issue where communication between Indigo and the AD2USB was getting dropped. Can you point me to that code? That may be what I am seeing in my setup.

I am not sure which bug that was. But, the latest beta is available at:
http://dl.dropbox.com/u/50307533/ad2usb ... -1-0-2.zip

and Inspired also wrote:I am still having trouble with reading configuration. I get this error:

AD2USB Alarm Interface Error Error in plugin execution UiAction:

Traceback (most recent call last):
File "plugin.py", line 535, in ConfigButtonPressed
<type 'exceptions.UnboundLocalError'>: local variable 'testSocket' referenced before assignment

I realize I am a little off the common path with a serial to IP connection. So I understand if these issues aren't something you can fix.

I strongly suspect the communications problems you are having are related to the iTach interface. The plugin expects either a direct USB connection or a completely transparent IP stream. My guess is that the iTach serial-to-IP protocol is not completely transparent and something being send from the ad2usb is causing the iTach to drop out, or, there is a timeout bug in the iTach software.

I'd like to use Cynical Network plugin to monitor the data output from the AD2USB, but i think it needs a second port on ser2sock. How would one open a second port ser2sock without messing up the communication with the AD2USB? I tried simply adding a second shell script line as below:

Code: Select all

do shell script ("/usr/local/bin/ser2sock -p15005 -s/dev/cu.usbserial-A2001wLz -b115200 -d -c -w 5000")

do shell script ("/usr/local/bin/ser2sock -p15006 -s/dev/cu.usbserial-A2001wLz -b115200 -d -c -w 5000")

which opened a second instance of ser2sock. The alarm plugin did not like it, and the cynical network plugin didn't show any data received. In fact, with ser2sock restarted with only port 15006 for cynical network and no alarm plugin (alarm plugin disabled and no port 15005 initialized), I'm not getting a data stream. Cynical network is set up for TCP in and I tried the various end of line options. Suggestions?


edit: since all I need to do is find out which partition is being displayed so I can parse the messages, I went to the plugin contents and modified the chime line as follows:

Code: Select all

indigoDevice.updateStateOnServer(key='chimeMode', value=rawData[30:31])

substituting the partition raw data for the chime data. Surprisingly it worked, changing to "0" for my garage partition, and "1" for my house partition. Now to see if a trigger will accurately place the data in my variables.....

hamw wrote:I'd like to use Cynical Network plugin to monitor the data output from the AD2USB, but i think it needs a second port on ser2sock. How would one open a second port ser2sock without messing up the communication with the AD2USB? I tried simply adding a second shell script line as below:

You do not need to make any changes to ser2sock, or run an additional instance of the program (which, as you have discovered, you can't do anyway).

Just have theCynical Network plugin use the same port setting as the ad2usb plugin (15005). ser2sock delivers an IP stream and multiple programs can listen at the same time to the same (IP) port.

hamw wrote:edit: since all I need to do is find out which partition is being displayed so I can parse the messages, I went to the plugin contents and modified the chime line as follows:...

Feel free to make changes to the plugin source. However, note that if you do make changes, your support channel for those changes becomes @hamw

berkinet wrote:

Inspired wrote:

berkinet wrote:...running the plugin in Advanced mode, the zone state will change from clear to fault even if the system is armed.

My system does not behave this way. If does not fault while waiting for the disarm code. Is there a way to compare 20P firmware revisions?

You would have to contact an Ademco specialist on this issue. I did check with Sean at NuTech and his experience is the same as mine. Are you watching the data stream on the ad2usb to see if there is a fault message from the faulted zone, or just looking for the zone device to change in Indigo? If you haven't tried watching the raw stream, give that a shot and see what you get.

This is a capture of the raw data stream. REL:12,02,00 is the doorway "clearing" a fault upon entry when the alarm is armed (edited):

[0100000110000000----],008,[f70000051008000c2c020000000000],"ARMED ***AWAY***** ALL SECURE **"
[0101050110000000----],008,[f70000051008050c2c020000000000],"DISARM SYSTEM or alarm occurs "
!REL:12,02,00
[0101050110000000----],008,[f70000051008050c2c020000000000],"DISARM SYSTEM or alarm occurs "
[1001010110000000----],008,[f70000051008011c28020000000000]," DISARMED CHIME Ready to Arm "

It also causes a "clear" event when I leave and the alarm is timing down to arm (edited):

[0101050110000000----],008,[f70000051008050c2c020000000000],"ARMED ***AWAY***You may exit now"
!REL:12,02,00
[0101050110000000----],008,[f70000051008050c2c020000000000],"ARMED ***AWAY***You may exit now"
[0100000110000000----],008,[f70000051008000c2c020000000000],"ARMED ***AWAY***** ALL SECURE **"

This is the normal open/close door activity when the alarm is not set (edited):

!REL:12,02,01
[0000000100000000----],008,[f70000051008000c08020000000000],"****DISARMED****Hit * for faults"
[1000000100000000----],008,[f70000051008001c08020000000000],"****DISARMED**** Ready to Arm "
!REL:12,02,00
[1000000100000000----],008,[f70000051008001c08020000000000],"****DISARMED**** Ready to Arm "

I fixed the other issue, the issue with dropping communication to the iTach device, by setting the plugin to use a fixed IP instead of a device name. The iTach IP was always fixed but I assume there is some DNS delay that is causing a timeout with the IP connection. It has been stable for 3 or 4 weeks now. I did confirm with iTach that their device is transparent (no escape sequence) on port 4999 as I am using it.

I also don't see what you would do about my above situation. If the alarm panel is reporting a "clear" on door activity when it is in the intermediate state between "Arming-Away" and "End of Exit" there is nothing you could change. I am currently working around this by assigning 2 other phantom relays to respond to these events.

berkinet wrote:

hamw wrote:...However, when I load the plugin and press the config button I get this:

Code: Select all

 ---Here the "Read AD2USB Configuration" button is pressed---
22Feb, 2012 9:00:32 PM
  AD2USB Alarm Interface Error    Error in plugin execution UiAction:

Traceback (most recent call last):
  File "plugin.py", line 540, in ConfigButtonPressed
<type 'exceptions.IndexError'>: list index out of range

Does that matter? Should I just ignore the button config error and move on?

Did you load the patched version of the plugin I placed on dropbox? That should prevent the error you saw. It would help if you could run the plugin in debug mode while you press the config button and post the output here. Then, try loading the new version.

I am running the patched version. It is throwing this error on pressing the "Read AD2USB Config".

AD2USB Alarm Interface Error Error in plugin execution UiAction:

Traceback (most recent call last):
File "plugin.py", line 546, in ConfigButtonPressed
<type 'exceptions.NameError'>: global name 'length' is not defined

Put the plugin into "Debug" and pressed the "Read AD2USB" button. Here's the output:

Code: Select all

  AD2USB Alarm Interface Debug    The raw zone type is: [100
  AD2USB Alarm Interface Debug    Panel Message: Before:=[100000011000--------],025,[f71300000025001c28020000000000],"****DISARMED****  READY TO ARM  "
, Current=[100000011000--------],017,[f70400000017001c28020000000000],"****DISARMED****  READY TO ARM  "

  AD2USB Alarm Interface Debug    Panel msg: [100000011000--------],
  AD2USB Alarm Interface Debug    panelReadMsg Quit
  AD2USB Alarm Interface Debug    Button callback called with UiValuesDict : (dict)
     ad2usb2usbSerialPort :  (string)
     ad2usbAddress : 127.0.0.1 (string)
     ad2usbCommType : IP (string)
     ad2usbConfigRead :  (string)
     ad2usbDeduplicate : true (bool)
     ad2usbExpander_1 : false (bool)
     ad2usbExpander_2 : false (bool)
     ad2usbExpander_3 : false (bool)
     ad2usbExpander_4 : false (bool)
     ad2usbExpander_5 : false (bool)
     ad2usbKeyPadAddress : 4 (string)
     ad2usbLabel0 :  (string)
     ad2usbLabel1 :  (string)
     ad2usbLrr : false (bool)
     ad2usbPort : 15005 (string)
     ad2usbRelLabel :  (string)
     ad2usbSerialPort : /dev/cu.usbserial-A2001wLz (string)
     ad2usbVirtRelay_1 : false (bool)
     ad2usbVirtRelay_2 : false (bool)
     ad2usbVirtRelay_3 : false (bool)
     ad2usbVirtRelay_4 : false (bool)
     ad2usbVirtZoneExpander : 0 (string)
     ad2usbZxpLabel :  (string)
     infoLabel :  (string)
     isAdvanced : false (bool)
     logUnknownDevices : true (bool)
     makeSpace1 :  (string)
     makeSpace2 :  (string)
     makeSpace3 :  (string)
     modeNotes1 :  (string)
     msgControl : 0 (string)
     msgTestFail1 :  (string)
     msgTestFail2 :  (string)
     msgTestSuccess :  (string)
     restartClear : false (bool)
     sectionLabel1 :  (string)
     sectionLabel2 :  (string)
     sectionLabel3 :  (string)
     showDebugInfo : true (bool)
     simpleSeparator1 :  (string)
     simpleSeparator2 :  (string)
     simpleSeparator3 :  (string)
     simpleSeparator4 :  (string)
     space1 :  (string)
  AD2USB Alarm Interface Debug    Button callback: the url is:socket://127.0.0.1:15005
  AD2USB Alarm Interface Debug    created new connection
  AD2USB Alarm Interface Debug    readline:!SER2SOCK Connected
, 0
  AD2USB Alarm Interface Debug    readline:!SER2SOCK SERIAL_CONNECTED
, 1
  AD2USB Alarm Interface Debug    readline:[100000011000--------],017,[f70400000017001c28020000000000],"****DISARMED****  READY TO ARM  "
, 2
  AD2USB Alarm Interface Debug    Read msg: [100000011000--------],017,[f70400000017001c28020000000000],"****DISARMED****  READY TO ARM  "

  AD2USB Alarm Interface Debug    The raw zone type is: [100
  AD2USB Alarm Interface Debug    Panel Message: Before:=[100000011000--------],017,[f70400000017001c28020000000000],"****DISARMED****  READY TO ARM  "
, Current=[100000011000--------],025,[f71300000025001c28020000000000],"****DISARMED****  READY TO ARM  "

  AD2USB Alarm Interface Debug    Panel msg: [100000011000--------],
  AD2USB Alarm Interface Debug    panelReadMsg Quit
  AD2USB Alarm Interface Debug    readline:[100000011000--------],025,[f71300000025001c28020000000000],"****DISARMED****  READY TO ARM  "
, 3
  AD2USB Alarm Interface Debug    Read msg: [100000011000--------],025,[f71300000025001c28020000000000],"****DISARMED****  READY TO ARM  "

  AD2USB Alarm Interface Debug    The raw zone type is: [100
  AD2USB Alarm Interface Debug    Panel Message: Before:=[100000011000--------],025,[f71300000025001c28020000000000],"****DISARMED****  READY TO ARM  "
, Current=[100000011000--------],017,[f70400000017001c28020000000000],"****DISARMED****  READY TO ARM  "

  AD2USB Alarm Interface Debug    Panel msg: [100000011000--------],
  AD2USB Alarm Interface Debug    panelReadMsg Quit
  AD2USB Alarm Interface Debug    readline:, 4
  AD2USB Alarm Interface Debug    Button callback: the raw config is:
  AD2USB Alarm Interface Debug    Button callback: the split config is:['']
  AD2USB Alarm Interface Error    Error in plugin execution UiAction:

Traceback (most recent call last):
  File "plugin.py", line 546, in ConfigButtonPressed
<type 'exceptions.NameError'>: global name 'length' is not defined

  AD2USB Alarm Interface Debug    Read msg: [100000011000--------],017,[f70400000017001c28020000000000],"****DISARMED****  READY TO ARM  "

  AD2USB Alarm Interface Debug    The raw zone type is: [100
  AD2USB Alarm Interface Debug    Panel Message: Before:=[100000011000--------],017,[f70400000017001c28020000000000],"****DISARMED****  READY TO ARM  "
, Current=[100000011000--------],025,[f71300000025001c28020000000000],"****DISARMED****  READY TO ARM  "

  AD2USB Alarm Interface Debug    Panel msg: [100000011000--------],
  AD2USB Alarm Interface Debug    panelReadMsg Quit
  AD2USB Alarm Interface Debug    Read msg: [100000011000--------],025,[f71300000025001c28020000000000],"****DISARMED****  READY TO ARM  "

  AD2USB Alarm Interface Debug    The raw zone type is: [100
  AD2USB Alarm Interface Debug    Panel Message: Before:=[100000011000--------],025,[f71300000025001c28020000000000],"****DISARMED****  READY TO ARM  "
, Current=[100000011000--------],017,[f70400000017001c28020000000000],"****DISARMED****  READY TO ARM  "

  AD2USB Alarm Interface Debug    Panel msg: [100000011000--------],
  AD2USB Alarm Interface Debug    panelReadMsg Quit
  AD2USB Alarm Interface Debug    validating Prefs called
  AD2USB Alarm Interface Debug    valuesDict =UiValuesDict : (dict)
     ad2usb2usbSerialPort :  (string)
     ad2usbAddress : 127.0.0.1 (string)
     ad2usbCommType : IP (string)
     ad2usbConfigRead :  (string)
     ad2usbDeduplicate : true (bool)
     ad2usbExpander_1 : false (bool)
     ad2usbExpander_2 : false (bool)
     ad2usbExpander_3 : false (bool)
     ad2usbExpander_4 : false (bool)
     ad2usbExpander_5 : false (bool)
     ad2usbKeyPadAddress : 4 (string)
     ad2usbLabel0 :  (string)
     ad2usbLabel1 :  (string)
     ad2usbLrr : false (bool)
     ad2usbPort : 15005 (string)
     ad2usbRelLabel :  (string)
     ad2usbSerialPort : /dev/cu.usbserial-A2001wLz (string)
     ad2usbVirtRelay_1 : false (bool)
     ad2usbVirtRelay_2 : false (bool)
     ad2usbVirtRelay_3 : false (bool)
     ad2usbVirtRelay_4 : false (bool)
     ad2usbVirtZoneExpander : 0 (string)
     ad2usbZxpLabel :  (string)
     infoLabel :  (string)
     isAdvanced : false (bool)
     logUnknownDevices : true (bool)
     makeSpace1 :  (string)
     makeSpace2 :  (string)
     makeSpace3 :  (string)
     modeNotes1 :  (string)
     msgControl : 0 (string)
     msgTestFail1 :  (string)
     msgTestFail2 :  (string)
     msgTestSuccess :  (string)
     restartClear : false (bool)
     sectionLabel1 :  (string)
     sectionLabel2 :  (string)
     sectionLabel3 :  (string)
     showDebugInfo : false (bool)
     simpleSeparator1 :  (string)
     simpleSeparator2 :  (string)
     simpleSeparator3 :  (string)
     simpleSeparator4 :  (string)
     space1 :  (string)
  AD2USB Alarm Interface Debug    Validation: no test for USB device 127.0.0.1


--turned off debug.

  AD2USB Alarm Interface          Plugin preferences have been updated
  AD2USB Alarm Interface Error    plugin runConcurrentThread function returned or failed (will attempt again in 10 seconds)
  AD2USB Alarm Interface          ad2usb opened for communication at socket://127.0.0.1:15005


Ideas?

Inspired wrote:

berkinet wrote:

Inspired wrote:

berkinet wrote:...running the plugin in Advanced mode, the zone state will change from clear to fault even if the system is armed.

My system does not behave this way. If does not fault while waiting for the disarm code. Is there a way to compare 20P firmware revisions?

You would have to contact an Ademco specialist on this issue. I did check with Sean at NuTech and his experience is the same as mine. Are you watching the data stream on the ad2usb to see if there is a fault message from the faulted zone, or just looking for the zone device to change in Indigo? If you haven't tried watching the raw stream, give that a shot and see what you get.

This is a capture of the raw data stream. REL:12,02,00 is the doorway "clearing" a fault upon entry when the alarm is armed (edited):

[0100000110000000----],008,[f70000051008000c2c020000000000],"ARMED ***AWAY***** ALL SECURE **"
[0101050110000000----],008,[f70000051008050c2c020000000000],"DISARM SYSTEM or alarm occurs "
!REL:12,02,00
[0101050110000000----],008,[f70000051008050c2c020000000000],"DISARM SYSTEM or alarm occurs "
[1001010110000000----],008,[f70000051008011c28020000000000]," DISARMED CHIME Ready to Arm "

So did this setup work for you. I was thinking of doing the same thing as with an wifi2serial itach device but didn't want to spend the money before finding out if it was a workable solution...
It also causes a "clear" event when I leave and the alarm is timing down to arm (edited):

[0101050110000000----],008,[f70000051008050c2c020000000000],"ARMED ***AWAY***You may exit now"
!REL:12,02,00
[0101050110000000----],008,[f70000051008050c2c020000000000],"ARMED ***AWAY***You may exit now"
[0100000110000000----],008,[f70000051008000c2c020000000000],"ARMED ***AWAY***** ALL SECURE **"

This is the normal open/close door activity when the alarm is not set (edited):

!REL:12,02,01
[0000000100000000----],008,[f70000051008000c08020000000000],"****DISARMED****Hit * for faults"
[1000000100000000----],008,[f70000051008001c08020000000000],"****DISARMED**** Ready to Arm "
!REL:12,02,00
[1000000100000000----],008,[f70000051008001c08020000000000],"****DISARMED**** Ready to Arm "

I fixed the other issue, the issue with dropping communication to the iTach device, by setting the plugin to use a fixed IP instead of a device name. The iTach IP was always fixed but I assume there is some DNS delay that is causing a timeout with the IP connection. It has been stable for 3 or 4 weeks now. I did confirm with iTach that their device is transparent (no escape sequence) on port 4999 as I am using it.

I also don't see what you would do about my above situation. If the alarm panel is reporting a "clear" on door activity when it is in the intermediate state between "Arming-Away" and "End of Exit" there is nothing you could change. I am currently working around this by assigning 2 other phantom relays to respond to these events.

So did this setup work for you? I was thinking of doing the same thing with a wifi2serial device but wanted to make sure it was a workable solution first.

Hello!

Apologies in advance if this post is in the wrong place - feel free to move it if required. However, I'm new to this, and have recently gotten Indigo working with my AD2USB, which I'm using with my Ademco Vista 20p.

Before I invest in the Pro version of Indigo, I want to verify that this software (and likewise the ad2usb plugin) will do what I need it to do. (gotta figure this out and test before the trial ends.) My needs, for now, are quite simple:
-- Notify me when an alarm occurs. Preferably via text message, and/or via push notification within Indigo Touch for iOS.
-- Allow me to somehow ack the alarm, and remotely silence it, and/or disarm the system using Indigo Touch.
-- If I don't ack the alarm (silence or disarm the alarm remotely), then notify a friend or family member via text message of the alarm after a given timeout period (say 5 to 10 minutes.)
-- Use Indigo Touch for routiene arm (stay/away) and disarm operation of the panel, to save the hassle of having to use the old keypad.

I gather that the ad2usb plugin can do these things, correct? One of the disturbing factors of the ad2usb plugin is that there's no plain old keypad emulator from what I can see. Unless I'm mistaken?
-- The plug-in seems entirely driven by Triggers. I have to wrap my head around that. I believe I have made a trigger to SMS me if alarm status = 1 (alarm active.) It uses my SMS gateway email address, using SMTP. But I haven't yet figured out ways to arm or disarm it remotely.

And finally, (this may be a question for a different forum,) the Indigo Touch app does not display any devices or triggers. I can connect to my server locally, and I made a device folder called "Alarm", and that's where the ad2usb alarm device sits. But tapping on the "Alarm" folder displays nothing in Indigo Touch - the same for triggers. So how can I operate the ad2usb plugin with Indigo Touch?

There's SO MUCH information.. I'm wondering where I ought to start. I found an ad2usb plugin PDF, and am almost done reading it. Any other info would be very helpful, on the above functionalities. Thank you in advance!

brokencircuit85 wrote:And finally, (this may be a question for a different forum,) the Indigo Touch app does not display any devices or triggers. I can connect to my server locally, and I made a device folder called "Alarm", and that's where the ad2usb alarm device sits. But tapping on the "Alarm" folder displays nothing in Indigo Touch - the same for triggers. So how can I operate the ad2usb plugin with Indigo Touch?

You're correct - this is a general Indigo Touch question but I'll answer it here.

Custom plugin devices (like the ones created by the ad2usb plugin) don't show up in the devices section of Indigo Touch because they have custom behaviors that we can't predict. What you need to do is create a control page that shows the custom device states on it and has controls to execute the actions provided by the plugin.

Triggers don't show up in Indigo Touch because you can't do anything with them (neither do Schedules). Indigo Touch is for controlling your automation, not editing it (like the Mac client). Since triggers and schedules run whenever they're defined to run (and not explicitly) they don't show up in Indigo Touch.

brokencircuit85 wrote:...Before I invest in the Pro version of Indigo, I want to verify that this software (and likewise the ad2usb plugin) will do what I need it to do. (gotta figure this out and test before the trial ends.) My needs, for now, are quite simple:
-- Notify me when an alarm occurs. Preferably via text message, and/or via push notification within Indigo Touch for iOS.

Yes. Indigo can do this. But, it is not something you just select from a menu. You would have to create a trigger to watch for the event(s) you wanted and then take the required action (send an email, in this case).

-- Allow me to somehow ack the alarm, and remotely silence it, and/or disarm the system using Indigo Touch.

You can either do this automatically, as in the case of the email, or via Indigo-Touch or an Indigo Control Page. However, note that custom control pages, and therefore Indigo-Touch, require the Pro version of Indigo. The plugin distribution contains two example virtual alarm keypad layouts that do just this.

-- If I don't ack the alarm (silence or disarm the alarm remotely), then notify a friend or family member via text message of the alarm after a given timeout period (say 5 to 10 minutes.)

Just like with the email, this can all be defined in a custom trigger action.

-- Use Indigo Touch for routiene arm (stay/away) and disarm operation of the panel, to save the hassle of having to use the old keypad.

I gather that the ad2usb plugin can do these things, correct? One of the disturbing factors of the ad2usb plugin is that there's no plain old keypad emulator from what I can see. Unless I'm mistaken?

As noted above, two virtual keypads are included with the plugin but does require Indigo Pro.

-- The plug-in seems entirely driven by Triggers. I have to wrap my head around that. I believe I have made a trigger to SMS me if alarm status = 1 (alarm active.) It uses my SMS gateway email address, using SMTP. But I haven't yet figured out ways to arm or disarm it remotely.

Actually, it is the other way around. The plugin monitors the alarm system, via the ad2usb, and then causes triggers that you define to be executed when certain actions happen.

Using plugins requires Indigo Pro so I don't think that's an issue for him...

Thank you both. I got it all sorted out! Just needed to hear a few key words in these replies to find my way to the control pages, etc.

Thank you!

Hello All!

Did we find a resolution to the issue below? I'm having the same problem (and error):
AD2USB Alarm Interface Error Error in plugin execution UiAction:

Traceback (most recent call last):
File "plugin.py", line 546, in ConfigButtonPressed
<type 'exceptions.NameError'>: global name 'length' is not defined

hamw wrote:

berkinet wrote:

hamw wrote:...However, when I load the plugin and press the config button I get this:

Code: Select all

 ---Here the "Read AD2USB Configuration" button is pressed---
22Feb, 2012 9:00:32 PM
  AD2USB Alarm Interface Error    Error in plugin execution UiAction:

Traceback (most recent call last):
  File "plugin.py", line 540, in ConfigButtonPressed
<type 'exceptions.IndexError'>: list index out of range

Does that matter? Should I just ignore the button config error and move on?

Did you load the patched version of the plugin I placed on dropbox? That should prevent the error you saw. It would help if you could run the plugin in debug mode while you press the config button and post the output here. Then, try loading the new version.

I am running the patched version. It is throwing this error on pressing the "Read AD2USB Config".

AD2USB Alarm Interface Error Error in plugin execution UiAction:

Traceback (most recent call last):
File "plugin.py", line 546, in ConfigButtonPressed
<type 'exceptions.NameError'>: global name 'length' is not defined

Put the plugin into "Debug" and pressed the "Read AD2USB" button. Here's the output:

Code: Select all

  AD2USB Alarm Interface Debug    The raw zone type is: [100
  AD2USB Alarm Interface Debug    Panel Message: Before:=[100000011000--------],025,[f71300000025001c28020000000000],"****DISARMED****  READY TO ARM  "
, Current=[100000011000--------],017,[f70400000017001c28020000000000],"****DISARMED****  READY TO ARM  "

  AD2USB Alarm Interface Debug    Panel msg: [100000011000--------],
  AD2USB Alarm Interface Debug    panelReadMsg Quit
  AD2USB Alarm Interface Debug    Button callback called with UiValuesDict : (dict)
     ad2usb2usbSerialPort :  (string)
     ad2usbAddress : 127.0.0.1 (string)
     ad2usbCommType : IP (string)
     ad2usbConfigRead :  (string)
     ad2usbDeduplicate : true (bool)
     ad2usbExpander_1 : false (bool)
     ad2usbExpander_2 : false (bool)
     ad2usbExpander_3 : false (bool)
     ad2usbExpander_4 : false (bool)
     ad2usbExpander_5 : false (bool)
     ad2usbKeyPadAddress : 4 (string)
     ad2usbLabel0 :  (string)
     ad2usbLabel1 :  (string)
     ad2usbLrr : false (bool)
     ad2usbPort : 15005 (string)
     ad2usbRelLabel :  (string)
     ad2usbSerialPort : /dev/cu.usbserial-A2001wLz (string)
     ad2usbVirtRelay_1 : false (bool)
     ad2usbVirtRelay_2 : false (bool)
     ad2usbVirtRelay_3 : false (bool)
     ad2usbVirtRelay_4 : false (bool)
     ad2usbVirtZoneExpander : 0 (string)
     ad2usbZxpLabel :  (string)
     infoLabel :  (string)
     isAdvanced : false (bool)
     logUnknownDevices : true (bool)
     makeSpace1 :  (string)
     makeSpace2 :  (string)
     makeSpace3 :  (string)
     modeNotes1 :  (string)
     msgControl : 0 (string)
     msgTestFail1 :  (string)
     msgTestFail2 :  (string)
     msgTestSuccess :  (string)
     restartClear : false (bool)
     sectionLabel1 :  (string)
     sectionLabel2 :  (string)
     sectionLabel3 :  (string)
     showDebugInfo : true (bool)
     simpleSeparator1 :  (string)
     simpleSeparator2 :  (string)
     simpleSeparator3 :  (string)
     simpleSeparator4 :  (string)
     space1 :  (string)
  AD2USB Alarm Interface Debug    Button callback: the url is:socket://127.0.0.1:15005
  AD2USB Alarm Interface Debug    created new connection
  AD2USB Alarm Interface Debug    readline:!SER2SOCK Connected
, 0
  AD2USB Alarm Interface Debug    readline:!SER2SOCK SERIAL_CONNECTED
, 1
  AD2USB Alarm Interface Debug    readline:[100000011000--------],017,[f70400000017001c28020000000000],"****DISARMED****  READY TO ARM  "
, 2
  AD2USB Alarm Interface Debug    Read msg: [100000011000--------],017,[f70400000017001c28020000000000],"****DISARMED****  READY TO ARM  "

  AD2USB Alarm Interface Debug    The raw zone type is: [100
  AD2USB Alarm Interface Debug    Panel Message: Before:=[100000011000--------],017,[f70400000017001c28020000000000],"****DISARMED****  READY TO ARM  "
, Current=[100000011000--------],025,[f71300000025001c28020000000000],"****DISARMED****  READY TO ARM  "

  AD2USB Alarm Interface Debug    Panel msg: [100000011000--------],
  AD2USB Alarm Interface Debug    panelReadMsg Quit
  AD2USB Alarm Interface Debug    readline:[100000011000--------],025,[f71300000025001c28020000000000],"****DISARMED****  READY TO ARM  "
, 3
  AD2USB Alarm Interface Debug    Read msg: [100000011000--------],025,[f71300000025001c28020000000000],"****DISARMED****  READY TO ARM  "

  AD2USB Alarm Interface Debug    The raw zone type is: [100
  AD2USB Alarm Interface Debug    Panel Message: Before:=[100000011000--------],025,[f71300000025001c28020000000000],"****DISARMED****  READY TO ARM  "
, Current=[100000011000--------],017,[f70400000017001c28020000000000],"****DISARMED****  READY TO ARM  "

  AD2USB Alarm Interface Debug    Panel msg: [100000011000--------],
  AD2USB Alarm Interface Debug    panelReadMsg Quit
  AD2USB Alarm Interface Debug    readline:, 4
  AD2USB Alarm Interface Debug    Button callback: the raw config is:
  AD2USB Alarm Interface Debug    Button callback: the split config is:['']
  AD2USB Alarm Interface Error    Error in plugin execution UiAction:

Traceback (most recent call last):
  File "plugin.py", line 546, in ConfigButtonPressed
<type 'exceptions.NameError'>: global name 'length' is not defined

  AD2USB Alarm Interface Debug    Read msg: [100000011000--------],017,[f70400000017001c28020000000000],"****DISARMED****  READY TO ARM  "

  AD2USB Alarm Interface Debug    The raw zone type is: [100
  AD2USB Alarm Interface Debug    Panel Message: Before:=[100000011000--------],017,[f70400000017001c28020000000000],"****DISARMED****  READY TO ARM  "
, Current=[100000011000--------],025,[f71300000025001c28020000000000],"****DISARMED****  READY TO ARM  "

  AD2USB Alarm Interface Debug    Panel msg: [100000011000--------],
  AD2USB Alarm Interface Debug    panelReadMsg Quit
  AD2USB Alarm Interface Debug    Read msg: [100000011000--------],025,[f71300000025001c28020000000000],"****DISARMED****  READY TO ARM  "

  AD2USB Alarm Interface Debug    The raw zone type is: [100
  AD2USB Alarm Interface Debug    Panel Message: Before:=[100000011000--------],025,[f71300000025001c28020000000000],"****DISARMED****  READY TO ARM  "
, Current=[100000011000--------],017,[f70400000017001c28020000000000],"****DISARMED****  READY TO ARM  "

  AD2USB Alarm Interface Debug    Panel msg: [100000011000--------],
  AD2USB Alarm Interface Debug    panelReadMsg Quit
  AD2USB Alarm Interface Debug    validating Prefs called
  AD2USB Alarm Interface Debug    valuesDict =UiValuesDict : (dict)
     ad2usb2usbSerialPort :  (string)
     ad2usbAddress : 127.0.0.1 (string)
     ad2usbCommType : IP (string)
     ad2usbConfigRead :  (string)
     ad2usbDeduplicate : true (bool)
     ad2usbExpander_1 : false (bool)
     ad2usbExpander_2 : false (bool)
     ad2usbExpander_3 : false (bool)
     ad2usbExpander_4 : false (bool)
     ad2usbExpander_5 : false (bool)
     ad2usbKeyPadAddress : 4 (string)
     ad2usbLabel0 :  (string)
     ad2usbLabel1 :  (string)
     ad2usbLrr : false (bool)
     ad2usbPort : 15005 (string)
     ad2usbRelLabel :  (string)
     ad2usbSerialPort : /dev/cu.usbserial-A2001wLz (string)
     ad2usbVirtRelay_1 : false (bool)
     ad2usbVirtRelay_2 : false (bool)
     ad2usbVirtRelay_3 : false (bool)
     ad2usbVirtRelay_4 : false (bool)
     ad2usbVirtZoneExpander : 0 (string)
     ad2usbZxpLabel :  (string)
     infoLabel :  (string)
     isAdvanced : false (bool)
     logUnknownDevices : true (bool)
     makeSpace1 :  (string)
     makeSpace2 :  (string)
     makeSpace3 :  (string)
     modeNotes1 :  (string)
     msgControl : 0 (string)
     msgTestFail1 :  (string)
     msgTestFail2 :  (string)
     msgTestSuccess :  (string)
     restartClear : false (bool)
     sectionLabel1 :  (string)
     sectionLabel2 :  (string)
     sectionLabel3 :  (string)
     showDebugInfo : false (bool)
     simpleSeparator1 :  (string)
     simpleSeparator2 :  (string)
     simpleSeparator3 :  (string)
     simpleSeparator4 :  (string)
     space1 :  (string)
  AD2USB Alarm Interface Debug    Validation: no test for USB device 127.0.0.1


--turned off debug.

  AD2USB Alarm Interface          Plugin preferences have been updated
  AD2USB Alarm Interface Error    plugin runConcurrentThread function returned or failed (will attempt again in 10 seconds)
  AD2USB Alarm Interface          ad2usb opened for communication at socket://127.0.0.1:15005


Ideas?

Which panel?

Mine is a Vista 20p panel.

berkinet wrote:Which panel?

I have found what may be the cause of the problem. Please try version 1.0.3 on Dropbox