[OBSOLETE] Honeywell / Ademco Vista 20P Integration

SmartApps & Automations Community Created SmartApps
, , , ,
346

Hi @redloro, thanks for the SmartThings Node Proxy. The first time I finally managed to get everything working, the STNP seemed to work flawlessly, reporting status, door openings and closings, etc., via PuTTY. When server.js was closed and then restarted, however, it seemed to be immediately disconnected every time it contacted my EVL4:

pi@raspberrypi:~/STnodeproxy $ node server.js
[2017-03-21T20:51:56.538Z] [stnp] SmartThings Node Proxy listening at http://:::8080
[2017-03-21T20:51:56.584Z] [stnp] Loaded plugin: envisalink
[2017-03-21T20:51:56.593Z] [evl3] Connected to Envisalink at 192.168.0.102:4025
[2017-03-21T20:51:56.644Z] [evl3] Envisalink connection closed.
[2017-03-21T20:52:00.659Z] [evl3] Connected to Envisalink at 192.168.0.102:4025
[2017-03-21T20:52:00.700Z] [evl3] Envisalink connection closed.

I have tried reformatting the microSD card and reinstalling system (using 2017-03-02-raspbian-jessie.zip), and nodejs (using node-v6.10.0-linux-armv6l.tar.xz) on the RPi3, and resetting the EVL4 (by power off). The first time I installed the Honeywell Security smartapp, it worked well until the connection was closed. The last time I reinstalled everything, using only the envisalink plugin, I received the above result. I then removed the Honeywell Security smartapp, chose again to install it, filled in all the information, but did not hit ‘done.’ I then restarted server.js, and when I hit ‘done’ on the smartapp configuration, this was the result:

pi@raspberrypi:~/STnodeproxy $ node server.js
[2017-03-21T20:29:08.059Z] [stnp] SmartThings Node Proxy listening at http://:::8080
[2017-03-21T20:29:08.105Z] [stnp] Loaded plugin: envisalink
[2017-03-21T20:29:08.114Z] [evl3] Connected to Envisalink at 192.168.0.102:4025
[2017-03-21T20:29:08.164Z] [evl3] Envisalink connection closed.
[2017-03-21T20:29:12.175Z] [evl3] Connected to Envisalink at 192.168.0.102:4025
[2017-03-21T20:29:12.209Z] [evl3] Envisalink connection closed.

[2017-03-21T20:31:50.956Z] [stnp] ::ffff:192.168.0.100 GET /subscribe/192.168.0.100:39500
[2017-03-21T20:31:51.107Z] [stnp] ::ffff:192.168.0.100 GET /plugins/envisalink/config/192.168.0.102:4025:_:
[2017-03-21T20:31:52.560Z] [evl3] Connected to Envisalink at 192.168.0.102:4025
[2017-03-21T20:31:52.598Z] [evl3] Envisalink connection closed.
[2017-03-21T20:31:53.241Z] [evl3] Connected to Envisalink at 192.168.0.102:4025
[2017-03-21T20:31:53.278Z] [evl3] Envisalink connection closed.
[2017-03-21T20:31:53.911Z] [evl3] Connected to Envisalink at 192.168.0.102:4025
[2017-03-21T20:31:53.948Z] [evl3] Envisalink connection closed.
[2017-03-21T20:31:55.359Z] [stnp] ::ffff:192.168.0.100 GET /plugins/envisalink/discover
[2017-03-21T20:31:55.405Z] [evl3] Completed panel discovery
[2017-03-21T20:31:56.601Z] [evl3] Connected to Envisalink at 192.168.0.102:4025
[2017-03-21T20:31:56.638Z] [evl3] Envisalink connection closed.

So the smartapp added all the contacts to my ‘things,’ but since shows as not ready. I am new to the Raspberry Pi and to Raspbian, and cannot think of anything else to try. I cannot understand why it seemed to work so well on first try, but never again. If you have the time, could you steer me in the right direction?

347

Hello and welcome! Have you checked out my EVL test connect video: https://www.youtube.com/watch?v=e2Xs0WWKl1Q

If the system connects/disconnects, there is something wrong with your config.json or the EVL itself. Make sure that you disconnect all connections to the EVL (this can be monitored via the EVL web console) and then test using telnet as shown in the video. Once you have that working correctly, make sure the settings in the config.json are correct, the EVL has released all clients (under EnvisaLink TPI Status) and then fire up the STNP.

348

Hi,

First I’d like to say wonderful piece of work, thanks. Either somethings not working correctly or I’m under the wrong impression
on how something works. Is it supposed to automatically discover the zone programed into the panel. I see the following when I finish
setting up everything.

[2017-03-23T00:16:42.573Z] [stnp] ::ffff:192.168.5.20 GET /subscribe/192.168.5.20:39500
[2017-03-23T00:16:47.386Z] [stnp] ::ffff:192.168.5.20 GET /plugins/envisalink/discover
[2017-03-23T00:16:47.386Z] [evl3] Completed panel discovery

Is this correct?

Thanks

349

@KJ61 a little bit of both. The plugin does do auto-discovery, but at the risk of completely destroying your alarm panel, I’ve disabled it and have only run it at my house! :slight_smile: So what you need to do is configure your zones in the config.json, start the STNP and then configure the SmartApp with Discover Zones enabled. Then all the zones will show up in ST.

Let us know if you need any help!

350

OK

One other question, can core pickup the armed states from the app?

351

Yes - I believe so… I use it with ST Home Monitor enabled and pickup states that way.

352

I own a honeywell ademco vista 10P would this solution from the 20P work for me ?

353

As long as the Envisalink or Alarm Decoder components work with your panel, this will work. From the docs it looks like both do support your panel… just check with their sales/support team before buying.

354

Thanks for the quick reply. I had a few questions.

I see that you went the route of envisalink and running a mac mini 24/7 to setup a LAN network.

  1. I am just looking for the cheapest option for me to arm/disarm my alarm while I am out, I dont mind using the cloud or having that lag. Is what you are doing overkill for me?

  2. Which option is cheaper Envisalink or Alarm Decoder

  3. Do you happen to sell any kits combo’s ect or have a suggestion on where to buy on the best retailer to buy from?

355

Correct - that’s just cause I already had a mac mini in my media rack, on 24x7 and within arms length of the Honeywell panel.

I don’t think this is overkill… if all you want to do is arm/disarm while you are out, you could start with the Envisalink and just use their web console for free at http://www.eyezon.com/

They’re both about the same price… components are usually between $80-100.

Best thing would be for you to find an online retailer to buy the alarm component (either Envisalink or Alarm Decoder)… and that’s a personal preference. Once you settle on that, figure out what computer you’ll connect to the alarm component, where you’ll put it, etc. If you don’t have a machine on 24x7 or anything close to your alarm panel, you may want to go with the RPi Zero W… amazing little thing that can be had for $10 at Micro Center now.

Good luck and let us know if you have any questions.

356

When I run node server.js this is the output I get…

[2017-03-26T09:53:35.649Z] [stnp] SmartThings Node Proxy listening at http://:::8080
[2017-03-26T09:53:35.701Z] [stnp] Loaded plugin: envisalink
[2017-03-26T09:53:35.717Z] [evl3] Connected to Envisalink at 10.0.0.222:4025
[2017-03-26T09:53:35.734Z] [evl3] Envisalink connection closed.
[2017-03-26T09:53:35.736Z] [evl3] Envisalink not connected.
[2017-03-26T09:53:35.738Z] [evl3] Envisalink not connected.
[2017-03-26T09:53:35.739Z] [evl3] Envisalink not connected.
[2017-03-26T09:53:35.740Z] [evl3] Envisalink not connected.
[2017-03-26T09:53:35.741Z] [evl3] Envisalink not connected.

The Envisalink not connected message will then just repeat over and over again, have any thoughts on what to try?

My config.json file…

{
“port”: 8080,
“authCode”: “authCode”,
“envisalink”: {
“address”: “10.0.0.222”,
“port”: “4025”,
“password”: “password”,
“securityCode”: “1234”,
“panelConfig”: {
“type”: “discover”,
“partitions”: [
{
“partition”: 1,
“name”: “Security Panel”
}
],
“zones”: [
{
“zone”: 1,
“type”: “contact”,
“name”: “Front Door”
},
…zones 2-15 here…
{
“zone”: 16,
“type”: “contact”,
“name”: “Motion”
}
]
}
}
}

357

Refer to post 347… and let us know if you have any questions!

358

Thanks for the help. I just tried to ssh but I keep getting the error “Server unexpectedly closed network connection”. I tried port 4025 and 22, port 22 says refused port 4025 says unexpectedly closed.
When I hit port 4025 with the browser it shows

Login:

and nothing else.
I can login using the IP in a browser and it displays current data. I rebooted the Envisalinlk get the same thing. Any thoughts?

359

@Kay did you watch the video?? It’s not ssh… you have to use telnet. If you are unable to do what is demonstrated in the video, this will not work. You have to first make sure you’ve got the EVL setup correctly and you can connect to it.

360

Just got a SmartThings. Previously used my EVL4 and Ademco 15P panel with Homeseer.

I was testing things to make sure it works before I setup the NODE, and I can’t telnet in…

I can connect via telnet, and I get the “Login:” prompt. As soon as I press any key it immediately says FAILED and exits. Is that right? I tried 2 different telnet clients. Does the same on both.

I know the EVL4 works, I’ve been using it for months.

361

I experienced same thing until redloro told me to stop STNP first before your telnet session. Once I did that, it worked as expected.

362

I don’t even have the node software installed yet, so I don’t think that is my issue…

363

Ok, well I decided to try setting up the STNP anyway. Seems to work fine. Not sure why I can’t telnet in and see things, but is I run the server.js I see events as expected, so I guess I won’t worry about it.

Now to figure out the Smartapps part. Since I’ve only had my SmartThings for one day, I haven’t ever done a manual one of those before…

364

I had to toggle the ‘discover zone’ option, and hit DONE to get the devices created. I then went and turned that back off and hit DONE again because I’m not sure what happens if you leave that on long term…

Everything is looking to work perfectly!

Now I just need to figure out how to run that server.js automatically on reboot. Are there any instruvtions/guide on that? I’m running the NODE.JS on a Ubuntu Server 16.04 install.

EDIT: Looks like it is my lucky night. I got it to run on start using pm2, following the guide here:
https://www.digitalocean.com/community/tutorials/how-to-set-up-a-node-js-application-for-production-on-ubuntu-16-04

365

Awesome! Great to hear you got it up and running so quick… and thanks for the pointer to pm2.