alarmdecoder.com

I just completed an AD2Pi / Raspberry Pi 3 setup. I downloaded the pre-built image from Alarm Decoder and wired the board to my Vista 20P panel as keypad address 19 (I have 3 existing keypads). I'm not sure if the WebApp is working correctly: I can login to the WebApp and arm/disarm the system. However, when I look at the Zones or Keypad tabs they are empty. Not sure if this is normal. I have 25 Zones and 3 Keypads setup in my Vista 20P. Seems like I should see the 25 Zones and 3 Keypads in the WebApp tabs. Also, the WebApp log shows faults correctly for the 25 Zones in real-time so maybe it is OK?

Based on this assumption, I proceeded with the SmartThings set up and that seemed to go per the instructions, but the SmartThings app is not working as expected. It will not Arm or Disarm. Also, it does not show any Zones at all just 12 red dots? I did enter the API and I assigned 8 zones to the ZoneTracker Switches, but that changed nothing.

Any thoughts on what I have done incorrectly?

Thanks, Mike

As for the first part of your question:

The zones in the webapp are not learned from your panel. This interface just maps a zone number (which your panel uses) to a human readable name for notification purposes.

The keypad tab is just for custom user defined buttons.

As for smartthings, please email ad2usb@support.nutech.com - I am not wholly savvy to our implementation.

Thanks Kevin. I might have spoken too soon re: my successful WebApp setup. Last night I was able arm from the webapp keypad, but today I cannot. I tried several keyboard addresses and made sure they are active on my v20p. When I enable a keypad for the ad2pi to use how should I set the audio alert portion of the setting? i am currently set up as 01 00 on keypad address 19. I have the webapp keypad set to 19 via the Webapp settings.

Is it possible I have other programming issues with my v20p that could effect the ad2pi? I have 25 zones set up, but there are also 4 zones (26-29) for Away, Stay, Disarm and Panic. Are they OK?

Your zones are your zones, it's agnostic to the alarmdecoder - the zones interface on the webapp is only to make human readable number to name mappings for the webapp.

If you are unable to communicate with the alarm directly via the webapp, we have a few things we can try.

Firstly, connect directly to your alarmdecoder via telnet (telnet alarmdecoder.local 10000) and see if you can arm/disarm using keypresses there.

If not, check your device settings as well as wiring. I typically set up my keypad addresses as 1 and 1 but chime off isn't an issue.

If you can successfully arm/disarm via a direct stream with the alarmdecoder, we can go from there.

Kevin, I was able to Arm & Disarm via Telnet. What does that tell us? Thx

Did you happen to update the software on your pi? Can you check your nginx version?
from command line via ssh: nginx -V

I used your image. I will check when I get home though.

What version should it be?

1.7.4

If it is working with ser2sock and not working with the webapp itself, it is a software or webapp configuration issue - so we need to verify the versions of your software, and then we need to go through your webapp settings.

What should the web app settings be? I will confirm them as well.