Wondering if anyone has been able to get the new interface modules with a vista panel and smartthings. I can get the interface to connect and I can see the zones open and closed on the smartthings app but I cannot get the panel to program the relays correctly. I can trigger the relay from the app but cant get the programming correctly to arm the system.

  • @ David Parsons Could you take some multi-meter reading across each of your zones for me please. I have the 15p I believe as i dont have any connectors on 18,19 and 20. On zone 1 of my system I have two door sensors wired together in series and the voltage output on that zone is 13v while my other double sensor zone is 3.73v and another at the same voltage and then i have one at 6.02v. Last thing i want to do is hook up my esp8266 NodeMCU pins to any one of those and fry my board. Thanks for your guys help and efforts.

  • Hi Martin. Please give me a ring tomorrow and I’ll see what I can do to help. (425) 879-0848. Pacific time zone.
  • Hi I'm having issues setting up the interface board with a relay. I managed to setup the interface board, addon board with the vista20p. I can see the different sensors in smartthings and konnected app. I can turn my relay on and off. The relay is connected to zone 7 of the vista20p with a 2k resistor as per instructions. I connected output 18 to zone 6 of interface and output 17 to zone 4. I programmed zone 7 in *56 for the switch. I did the *79 and 80 programming. I can't seem to be able to activate system in smartthings. What are the next steps. I've attached pics of my setup
  • Giuseppe, I would try my vista integrations smart app, it helped simplify things:


    Although I will say, be sure your wifi connection is good. I wound up scrapping this configuration because it turns out the chip sends a blip of a high signal to the relay on boot, which causes a key switch fault to register on the 20p. Mine would reboot often and made it annoying. Its a known issue with D0. See  https://rabbithole.wwwdotorg.org/2017/03/28/esp8266-gpio.html

  • Typo, D8.

  • Hi Peter, I managed to activate the system through the app. I activate the relay switch and the the system activates. However I don't seem to be able to get the arm and disarm functions to work on the app. When I change the relay from momentary to the konnected relay switch and add it in the integration app it doesn't work. I can't even activate the switch.
  • @Francis Glaser , did you ever get the programming for output 18 to alert when alarm triggers?
  • I have been using Konnected Alarm Panel INTERFACE for wired security systems with Honeywell Vista system. It has been working great for almost 2 years with old smarthings app. Recently the old smarthings app suggested to migrate to new Smarthings app and I migrated all. Now it is not working with new smarthings app. It says 2 sensors open the Armed Away and Armed Stay. Please advice.

    Thank you.

  • Any one lucky connecting to new Smarthings app?

  • I just wanted to say thanks to David Parsons - used the doc to tie in my Vista 21ip to the interface board with alarm stay/away statuses.  I started with the *80 figuring the *79 defaulted to 0, but I found I still had to program the *79 in.

    Maybe one day I will get to the relay for arming & disarming, but that's for another time.

    Thanks again.

  •  I've got a Vista 20-p with 2 wall mounted controllers... Looking at getting this interface module so I can replace one of those controllers with an android tablet, that will view zone statuses, and be able to arm or disarm the Vista.  Will that be possible without me pulling out the little hair I have left?  I am competent, but dont qualify as a real geek.

  • Hi Andy,
    I just installed my interface about a month ago so I'm no expert but it is a fairly easy process (just watch the youtube video).  Right now I've tapped into my three door sensors and the Stay and Away statuses from the main panel.  I am able to view these five "contacts" in my Hubitat dashboards.  If you want to add the Stay / Away statuses, check the Doc that David posted on the first page.
    I haven't gone as far as adding in the ability to arm / disarm the system but it just requires adding in the relay (it comes with the kit) and I've been too busy to do it.  From what I've read, you would need to program in another zone on your Vista as a key switch and there is something about the delay that selects the difference between Arm Stay and Arm Away.

  • This thread is exactly what I've been looking for for the past few days of research trying to figure out how to:

    - Enable SmartThings to GET the armed status of the Vista 20P (e.g. away/stay/disarmed/burglar)

    - Enable SmartThings to SET the armed state of the Vista 20P (e.g. away/stay/disarm)

    There's info out there on how to set and get arm/disarm/burglar but this is the first thing I've found that hints at the ability to work with specific arming states.

    Awesome work by Peter Babinski and David Parsons - thank you.

    If I'm understanding this correctly, I will need 3 outputs on the Vista 20P which will connect to 3 zone inputs on the Konnected interface board:

    1. Output burglar state

    2. Output AWAY arming state

    3. Output STAY arming state

    Then I will just need a single zone on my Vista 20P configured as a keyswitch and by using the device handler built by Peter Babinski, I'll be able to set the following momentary durations to set the armed state of the Vista:

    - Under .5 second (instantaneous) disarms

    - Between .5 and 1 second arms AWAY

    - Longer than 1 second arms STAY

    This is according to the Vista 20P User Manual (see attached VistaKeyswitch.JPG)

    I've also been experimenting with zone types 20, 21 and 22 (see attached VistaArmingZoneTypes.JPG) but I'm not sure these do what I want. I was hoping a momentary contact on an input configured as one of those zone types would arm or disarm the system but I can't get it working. It seems to want to configure those zone types for an unsupervised RF button.

    Peter/David - are you guys still around? Am I understanding this all correctly?



  • I have since moved on from Konnected. I did research into the GPIO of the chip used and the Konnected interface pin assignments and found that the relay tripped every time the device rebooted. I would get a Key Switch Fault showing up on my keypads afterwards and would have to key in to reset the status. I may or may not have posted in this thread linking to the diagnostics of the chip and an oscilloscope but it's there. I also think I saw someone try and use my smart app but the Konnected codebase may have diverged from my original commits and it may no longer function (although maybe it could with some love yet I have no way to test now). My current setup is an Alarm Decoder pihat on a pi zero and works much more seamless. The code is completely open source as compared to Konnected 2.0. Feel free to hit me up on GitHub or just my last name at gmail. I love that Konnected got me into this world of smart alarms but have moved on to more customizable pastures.
  • Thanks, @Peter Babinski

    Last night after reading your post about the AlarmDecoder solution, I did some research and just by sheer coincidence, had the parts I needed to set it up. I took apart my Homeseer Z-net on a hunch and sure enough, there was a Raspberry Pi B+ and on closer inspection of the device I've been using to connect Homeseer to my Vista 20P, it was a Nutech/AlarmDecoder AD2USB. So I got the Raspbian image from AlarmDecoder, put it on the Pi, connected the AD2USB, configured the WebApp, installed the device handlers, installed the SmartApp and have things sort of working.

    The complexity of this solution and what I had to do to get it working is mind-boggling. This solution is not for the faint of heart. I guess that's open source for you. It certainly didn't help that Samsung has their SmartThings cloud infrastructure split into different shards so the things I was installing in the IDE weren't showing up on my hub or finding the webapp.

    Anyway, this the wrong forum for AlarmDecoder info but just wanted to pass that along to anyone following along that was thinking about heading down that path. It may work great but I'm a little turned off by the complexity.

    I've been going back and forth today with Konnected support and they are telling me the momentary duration can be configured in the Konnected cloud on a per-relay basis. This apparently means I can configure relay #1 for .5 second and relay #2 for 1 second and achieve STAY/AWAY arming. For disarm, I think I would send a momentary to either relay and if the system is armed, it will interpret any momentary as DISARM.

    I can't really confirm any of this until I buy one and try to set it up though.

Login or Signup to post a comment