alarmdecoder.com

Hi,

I'm having some issues trying to debug an installation on openHab(2.2 specifically). My system (all wired zones) is as follows:

Ademco Vista 20p
[2] Zone expansion boards
[1] 6162 Keypad
Raspberry Pi 2b running AD image (upgraded to Stretch).

The AD WebUI shows all my zones and zone naming. I can arm/disarm successfully... On my openHab server, I can successfully telnet into AD's port 10000 (so far so good). The issue is I'm only observing !AUI messages during a zone fault. I did however see a !EXP when I closed the alarm panel cabinet door. I haven't seen any relay messages whatsoever (shouldn't I ??).

I'm hoping this is a simple config issue or you can assist me in isolating the root cause.

Code: Select all

!CONFIG>MODE=A&CONFIGBITS=ff05&ADDRESS=19&LRR=N&COM=N&EXP=NNNNN&REL=NNNN&MASK=ffffffff&DEDUPLICATE=N
!VER:ffffffff,V2.2a.8.8,TX;RX;SM;VZ;RF;ZX;RE;AU;3X;CG;DD;MF;L2;KE;M2;CB;DS;ER;CR


Code: Select all

root@openHab:/etc/openhab2/services# telnet
telnet> open 10.0.9.102 10000
Connected to 10.0.9.102.
Escape character is '^]'.
[00000001000000000A--],024,[f70200ff10240000080200000010f0],"FAULT 24 CABINETTAMPER          "
[00000001000000000A--],024,[f70200ff10240000080200000010f0],"FAULT 24 CABINETTAMPER          "
[00000001000000000A--],024,[f70200ff10240000080200000010f0],"FAULT 24 CABINETTAMPER          "
!EXP:08,08,00
!AUI:120600000000666c02456cf5ec0101010000
!AUI:1606000000006763024543f531fb456cf5ec01010101
[10000001000000003A--],008,[f70200ff1008001c08020000000000],"****DISARMED****  Ready to Arm  "
[10000001000000003A--],008,[f70200ff1008001c08020000000000],"****DISARMED****  Ready to Arm  "
[10000001000000003A--],008,[f70200ff1008001c08020000000000],"****DISARMED****  Ready to Arm  "
[10000001000000003A--],008,[f70200ff1008001c08020000000000],"****DISARMED****  Ready to Arm  "
[10000001000000003A--],008,[f70200ff1008001c08020000000000],"****DISARMED****  Ready to Arm  "
[10000001000000003A--],008,[f70200ff1008001c08020000000000],"****DISARMED****  Ready to Arm  "
[10000001000000003A--],008,[f70200ff1008001c08020000000000],"****DISARMED****  Ready to Arm  "
[10000001000000003A--],008,[f70200ff1008001c08020000000000],"****DISARMED****  Ready to Arm  "
!AUI:120600000000606c02456cf5ec0101010000
!AUI:1606000000006163024543f531fb456cf5ec01020106
[00000001000000000A--],002,[f70200ff1002000008020000000000],"FAULT 02 FRONT  ENTRY DOOR      "
[00000001000000000A--],002,[f70200ff1002000008020000000000],"FAULT 02 FRONT  ENTRY DOOR      "
[00000001000000000A--],002,[f70200ff1002000008020000000000],"FAULT 02 FRONT  ENTRY DOOR      "
[00000001000000000A--],002,[f70200ff1002000008020000000000],"FAULT 02 FRONT  ENTRY DOOR      "
[00000001000000000A--],002,[f70200ff1002000008020000000000],"FAULT 02 FRONT  ENTRY DOOR      "
[00000001000000000A--],002,[f70200ff1002000008020000000000],"FAULT 02 FRONT  ENTRY DOOR      "
!AUI:120600000000626c02456cf5ec0101010000
!AUI:1606000000006363024543f531fb456cf5ec01010101
[10000001000000003A--],008,[f70200ff1008001c08020000000000],"****DISARMED****  Ready to Arm  "



Thanks,
Monika

A quick follow-up to my previous post. For clarity, the faulted zone (front door) is zone #02 which is wired direct to the 20p. Deep diving I was able to find a very old thread that discussed zones 1-8 not reporting faults as !REL. So it appears that I have to do some sort of Virtual zones? Does this sound correct? I'm still searching for instructions on how and where this is performed.

The easiest way around this would be to hook the zones up through a zone expander which always report as !EXP messages

There is some programming fu you can do but I don't recall what it is - I seem to recall something on the old forums as well with regard to this http://archive.nutech.com/index.php?opt ... mitstart=0

Thanks Kevin,

This is very disheartening. One option requires me to spend more money (and time to reprogram all 8 zones) and the other in search of someone who can help walk me through programming at least one Virtual so I feel confident enough to do the remaining zones. I guess I had hoped that there was some sort of write up in the FAQ section but other than the post you linked, there is little to no information. I don't feel like guessing my way through this one.

--Monika

kevin wrote:The easiest way around this would be to hook the zones up through a zone expander which always report as !EXP messages

There is some programming fu you can do but I don't recall what it is - I seem to recall something on the old forums as well with regard to this http://archive.nutech.com/index.php?opt ... mitstart=0

Sorry that isn't enough information for you - I can't tell you how to program your panel as each one is different and that post does give all the necessary information to do what you're asking

What I suggest is emailing support and see if they will walk you through the process, referencing the archived posting.

Actually, I owe you an apology Kevin. I didn't mean for my post to sound so strong. The information you provided was helpful, it just isn't something I feel comfortable performing on a production system. This would be a different story if I had an bench system on hand but I don't.

--Monika

kevin wrote:Sorry that isn't enough information for you - I can't tell you how to program your panel as each one is different and that post does give all the necessary information to do what you're asking

What I suggest is emailing support and see if they will walk you through the process, referencing the archived posting.

Email support, they may ask you to chip in to their coffee fund for the time, but they'll walk you through the process. ad2usb@support.nutech.com

Thanks Kevin, I emailed support with hope they can resolve this issue. If this is a case of funding coffee ... DONE ! Is this a Starbucks or Dunkin Donuts run ?

--Monika