Honeywell Vista 20P - Unable to remotely arm/disarm

Support
1

I purchased and installed the Alarm.com Honeywell Vista Security Enhancement Module for my Honeywell Vista 20P. Everything seems to be working, I got it activated on Alarm.com and I’m able to see the status of my panel as well as all the sensors. I get notifications when I arm/disarm my system from the keypad. The SEM is able to read data from the panel. When I use the “Reboot Alarm Panel” button in my System Manager, it will indeed reboot the panel where the SEM will go through the process of setting all the various fields using the installer code. So it seems like the SEM can send and receive data from my panel. I made sure to enable keypad address 23 and don’t have any other keypads using that same address.

However, the one thing that it cannot seem to do is to remotely arm and disarm. Also, it seems to take a while to sync users with the panel and I’m not sure user syncing actually works. What could be causing the issue where I cannot remotely arm/disarm?

2

This may be an issue with the master code sync.

What revision of the Vista 20p do you have? The revision number is on the prom chip located on the control board.

What specific model of the alarm.com SEM do you have?

Can you confirm you don’t have any trouble conditions (low battery, tamper, fire trouble etc.) or open zones while you’re trying to remotely arm?

When you first power up the Vista and SEM, did you allow it to finish performing the zone scan before pressing any buttons on the keypad?

Do you have any other devices connected to the Vista besides keypads (like zone expanders, RF receiver, or 3rd party modules like an Envisalink 4)?

Do all of your programmed zones show up properly on alarm.com’s website?

3

The version on the chip shows as 2010 REV 9.12.

I ordered this model from the Surety store: Alarm.com Honeywell Vista System Enhancement Module - Alarm.com ADC-SEM210-VT-VZ - Surety

There are no trouble conditions and all zones are closed.

Upon first powering up, I did allow it to finish before pressing anything on the keypad.

I do have a RF receiver, in particular, the Honeywell 5881 EN. I also have the Honeywell 6270 Touchscreen. Both are using the default settings (to my knowledge, neither use keypad address 23).

All of my zones show up in Alarm.com and the status (open/closed/triggered) is accurately shown as well. Although, sometimes my RF sensors will periodically show up as open/closed events on alarm.com, even though they don’t trigger any events on my panel. This is without them actually being triggered.

4

What’s the version of the SEM that’s on the box/unit? If it has a firmware version listed post that too.

You don’t have a telephone line connected to the Vista, correct?

I have two troubleshooting steps for you to try

According to the documentation, older firmware versions of the SEM are not compatible with voice talking keypads (SEM needs to be on firmware 1.60+ for compatibility). I don’t think the 6270 is a talking keypad but it’s similar to the current talking touchscreen keypads which also use an AUI address.

I don’t have any affiliation with Surety so I can’t check which firmware version your SEM is running from the dealer portal.

I recommend powering down your Vista panel and SEM, disconnecting the 6270 and powering the system back up.

If that doesn’t work. Do a manual master code sync (with the 6270 disconnected).

I recommend deleting all user codes from the system except for the master code. Also, verify you don’t have any codes assigned in the 6270 (newer touchscreens are capable of this, but I’m not sure about the 6270).

The alarm.com documentation recommends changing the master code from the alarm.com app or website. If that doesn’t work, change it locally via the keypad.

According to the documentation, if the master code sync does not work via the website, they want you to change the master code to 1234.

Enter your installer code and press 8, followed by 02, then enter 1234. If that worked the keypad should beep. Wait a minute and verify the master code works. Then test the arming/disarming from the app.

You can also change the master code by entering the current master code + 8 + 02 + new master code + new master code again.

I’m also assuming you have an alpha keypad like the 6160 or similar. If you have a 6160V or talking keypad let me know, because if the SEM is on an older firmware version, it’s not compatible.

I’m not sure what kind of backend access you get with Surety, but if you can update the firmware on the SEM, I recommend doing so. If not, you should request they update it when they’re available during the week.

1 Like
5

This is correct. When remote arming fails on the vista 20P, it most likely is the syncing of the master code that is the issue.

Change the master code to default using the steps above and change the master code to 1234 as well using the alarm.com app if it has been changed. Wait about 5 minutes then update the master code to the one desired using the alarm.com app. Wait about 5 minutes again and try remote arming and disarming. Also, test locally to make sure master code was updated.

Thank you

1 Like
6

The sticker inside shows “FW: SM189-VZ”. I was able to determine the firmware version as being “17011899”, which I assume is something like 1.7+

The Vista does not have a telephone line and has never had a telephone line connected to it. It has had various cellular modules connected to it throughout the years.

I do have a talking keypad, the 6160V and is set to address 16.

I logged into Alarm.com and noticed that the master code was reset to 1234. I figured I’d try resetting the master code via the keypad to 1234. Sure enough, things actually started to work. I was able to change change and sync the master code, sync a second user, and also arm/disarm the system remotely.

Thanks for the help! It seems to be working now.

7

Np, I’m glad you got it to work!