SmartThings Community

[RELEASE] Honeywell / Ademco Vista 20P Integration

honeywell
dth_security
smartapp_security
project_security
alarmdecoder

(Scott Herchenbach) #946

I don’t know why it’s DSC other than that’s the name of the variable in the DH.

Here’s the piston example:

I did not have to restart the server.


#947

Awesome. I assume you had to type in “alarm” in the variable?

Also, just curious how you test your alarm without sending a signal out to the monitoring company or hearing that siren go off…


(Scott Herchenbach) #948

I typed in alarm in the variable. You can also check for other status. If you open the DH, you can see all the options.

The only way to test is by triggering the alarm. I use alarm relay for monitoring, and I have to call them ahead of time to let them know I’m testing. They will put my system in “test mode” for as long as I ask them to. The alarm still goes off, but the cops don’t show up. Hope this helps.


#949

Yes, extremely helpful. Unless I missed a post somewhere, up until this point I haven’t seen a solution for this outside SHM, so this is really good…thanks!


(Ryan ) #950

would you be able to help with this. I want to connect my Visa20p panel to smart things. I have an envisalink4 connected already. I want to run the smartthings Node on Windows machine but not sure how to get everything talking with each other. My main issue is im not a programmer so when im reading the .JS coed I see IP’s and ports but not sure where I should input ip’s in from my devices


#951

Hi Folks…

This question may have already been ask.

I have everything working as advertised. Is there a way to tell Node Proxy to use the WiFi interface instead of the Ethernet interface on a Raspberry Pi?

Thanks


(Kenneth Pocius) #952

Hello. I think there may be an issue with the serialport version. I’m trying an AD2USB install. I was having an install issue with a bunch of errors saying that the link to the serialport v5.5.0 was bad. I look at another redloro thread for the Russound and saw someone had a similar issue. The suggested fix there was to manually install serialport in the project folder and to remove the install request from the package.json. It worked for me.


(Kenneth Pocius) #953

So I continue to struggle with getting this running on the Pi. I had it running fine on the windows machine, but no luck with the Pi. I’m able to get STNP up and running on the Pi, and I can see the events as they occur. I can’t get the SmartApp to discover, create the zones and/or create the devices. I thought the issue was the Hue-bridge running on the Pi, but I’ve since reflashed the Pi (reinstalled the OS) and reinstalled everything. So I’m at a loss.

I’ve reinstalled the SmartApp several times, thinking there could be an issue there. Still nothing.

Any help troubleshooting why the discovery isn’t working?

Thanks!


(Kenneth Pocius) #954

I also have an Envisalink, and I am able to get that running in the STNP. Same story as with the AD2USB - I can see the events with the server running and I can see the SmartApp call into the server and I see “panel discovery”, but there is no device creation. I reused the config.json file from when I had it running successfully on the windows machine so the zones are already created in that file. So the SmartApp isn’t creating devices.

So to summarize - both the AD2USB and Envisalink are themselves running fine (at least they read the panel and report events); the server on the Pi works with both (not at the same time, I run them separately) and I can see the events (e.g., zone faults as I walk around); the SmartApp calls into both and I see “Completed Panel Discovery” on both. Me thinks there’s something with the SmartApp.

There are no other SmartApps that I can think of which would interfere with this SmartApp, and there’s nothing else running on the Pi (I reinstalled the OS on the Pi to clear out any hidden processes)

I’ve uninstalled and reinstalled the SmartApp several times.

This is a real headscratcher.


#955

As follow-up to anyone who wants to use WebCoRE with this integration, I was able to get it to work perfectly using “dscpartition is” rather than “dscpartition changes to.”

My integration with the Vista20P integration and SHM never worked great (as I mentioned previously, bypassing a sensor would cause false SHM activations). With this “new” set-up, I longer have to worry about that and clearing out SHM false alarms.


#956

This is interesting. Can you share more details on your use of WebCoRE with Vista20P/SHM? I have EVL4 with Vista20P but haven’t looked at SHM in the recent past because I couldn’t find a good entry/exit delay solution that last time I tried this.


#957

Theherks has a great example (except, at least for me, I had to use the “is” instead of “changed to.”)

Your intrusion status (e.g. “alarm”) can be used to activate lights, make your Amazon Echos speak, send you email/text notification, etc. To use the speak portion, you’ll need to check out Echo Speaks, done by Tonesto7.

SHM is not needed.


#958

Thanks, I’ll have to read up on the example and echo speaks.


(Mark H) #959

Hey Eric! Would you mind sharing what code you used in your command lines on crontab? I am kind of learning as I go and just can’t figure out how to auto load and run on reboot or loss of power. Thanks in advance!


#960

Anyone have a WebCoRE sample that shows alarm status in one of the dashboards(SmartTiles, ActionTiles, Housepanel, etc)? I was able to get a basic WebCoRE piston for “alarm” intrusion status to work fine using Theherks example above with tweak of “is” instead of “changed to” that smartie highlighted. I’d like to get a tile in my dashboard that would display Vista 20P panel status of “Armed”, “Stay”, “Instant” or “Away” directly instead of SHM. Even similar samples would be helpful as I try to adapt it to my dashboard needs.


#961

I am not clear if this method is specific to the Honeywell system, or if it can be used to integrate a DSC 32 zone system.

I wanted to get some clarification before I dig in.

Thanks for any guidance.


(Scott Herchenbach) #962

Pilot04, I have not tried it myself, but you should be able to use dspartition or panelstatus to give you the panel status. In IDE, in My Devices, click on the Honeywell device, and click on List Events. You can see all the changes to the variables dspartition and panelstatus. You should be able to use these to give you all the information you should need.


#963

I was able to get the status from the dscpartition and panelstatus variables. However, I can’t figure out how to get them out of WebCoRE into SmartThings to display in one of the dashboards outside of WebCoRE.


(Jon) #964

Hi all and @redloro

I’m stuck getting the node proxy to run and I’ve never worked with nodejs before so I’m a little lost trying to debug.

I spun up an Ubuntu VM, installed the latest distro stable nodejs and npm packages, and then installed the nodeproxy with envisalink plugin by following the read me. I couldn’t make anything of the error messages I received when I tried to start the server, so I removed and purged nodejs and npm and started over but got the same result. here’s my debug log:

0 info it worked if it ends with ok
1 verbose cli [ ‘/usr/bin/node’, ‘/usr/bin/npm’, ‘run’, ‘start’ ]
2 info using npm@3.5.2
3 info using node@v8.10.0
4 verbose run-script [ ‘prestart’, ‘start’, ‘poststart’ ]
5 info lifecycle smartthings-nodeproxy@1.0.0~prestart: smartthings-nodeproxy@1.0.0
6 silly lifecycle smartthings-nodeproxy@1.0.0~prestart: no script for prestart, continuing
7 info lifecycle smartthings-nodeproxy@1.0.0~start: smartthings-nodeproxy@1.0.0
8 verbose lifecycle smartthings-nodeproxy@1.0.0~start: unsafe-perm in lifecycle true
9 verbose lifecycle smartthings-nodeproxy@1.0.0~start: PATH: /usr/share/npm/bin/node-gyp-bin:/home/batteryxsnare/smartthings/smartthings-nodeproxy/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin
10 verbose lifecycle smartthings-nodeproxy@1.0.0~start: CWD: /home/batteryxsnare/smartthings/smartthings-nodeproxy
11 silly lifecycle smartthings-nodeproxy@1.0.0~start: Args: [ ‘-c’, ‘node server.js’ ]
12 silly lifecycle smartthings-nodeproxy@1.0.0~start: Returned: code: 1 signal: null
13 info lifecycle smartthings-nodeproxy@1.0.0~start: Failed to exec start script
14 verbose stack Error: smartthings-nodeproxy@1.0.0 start: node server.js
14 verbose stack Exit status 1
14 verbose stack at EventEmitter. (/usr/share/npm/lib/utils/lifecycle.js:232:16)
14 verbose stack at emitTwo (events.js:126:13)
14 verbose stack at EventEmitter.emit (events.js:214:7)
14 verbose stack at ChildProcess. (/usr/share/npm/lib/utils/spawn.js:24:14)
14 verbose stack at emitTwo (events.js:126:13)
14 verbose stack at ChildProcess.emit (events.js:214:7)
14 verbose stack at maybeClose (internal/child_process.js:925:16)
14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
15 verbose pkgid smartthings-nodeproxy@1.0.0
16 verbose cwd /home/batteryxsnare/smartthings/smartthings-nodeproxy
17 error Linux 4.15.0-43-generic
18 error argv “/usr/bin/node” “/usr/bin/npm” “run” “start”
19 error node v8.10.0
20 error npm v3.5.2
21 error code ELIFECYCLE
22 error smartthings-nodeproxy@1.0.0 start: node server.js
22 error Exit status 1
23 error Failed at the smartthings-nodeproxy@1.0.0 start script ‘node server.js’.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the smartthings-nodeproxy package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error node server.js
23 error You can get information on how to open an issue for this project with:
23 error npm bugs smartthings-nodeproxy
23 error Or if that isn’t available, you can get their info via:
23 error npm owner ls smartthings-nodeproxy
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]

I’m sure it’s simple…any ideas what I messed up? Thanks and happy new year all!


(Jon) #965

update to above…got rid of old node v8.10.0 and npm v3.5.2 and updated to latest to ensure node v11 and npm v6.5…new debug log:

0 info it worked if it ends with ok
1 verbose cli [ ‘/usr/bin/node’, ‘/usr/bin/npm’, ‘run’, ‘start’ ]
2 info using npm@6.5.0
3 info using node@v11.6.0
4 verbose run-script [ ‘prestart’, ‘start’, ‘poststart’ ]
5 info lifecycle smartthings-nodeproxy@1.0.0~prestart: smartthings-nodeproxy@1.0.0
6 info lifecycle smartthings-nodeproxy@1.0.0~start: smartthings-nodeproxy@1.0.0
7 verbose lifecycle smartthings-nodeproxy@1.0.0~start: unsafe-perm in lifecycle true
8 verbose lifecycle smartthings-nodeproxy@1.0.0~start: PATH: /usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/batteryxsnare/smartthings/smartthings-nodeproxy/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/s$
9 verbose lifecycle smartthings-nodeproxy@1.0.0~start: CWD: /home/batteryxsnare/smartthings/smartthings-nodeproxy
10 silly lifecycle smartthings-nodeproxy@1.0.0~start: Args: [ ‘-c’, ‘node server.js’ ]
11 silly lifecycle smartthings-nodeproxy@1.0.0~start: Returned: code: 1 signal: null
12 info lifecycle smartthings-nodeproxy@1.0.0~start: Failed to exec start script
13 verbose stack Error: smartthings-nodeproxy@1.0.0 start: node server.js
13 verbose stack Exit status 1
13 verbose stack at EventEmitter. (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:301:16)
13 verbose stack at EventEmitter.emit (events.js:188:13)
13 verbose stack at ChildProcess. (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:188:13)
13 verbose stack at maybeClose (internal/child_process.js:978:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:265:5)
14 verbose pkgid smartthings-nodeproxy@1.0.0
15 verbose cwd /home/batteryxsnare/smartthings/smartthings-nodeproxy
16 verbose Linux 4.15.0-43-generic
17 verbose argv “/usr/bin/node” “/usr/bin/npm” “run” “start”
18 verbose node v11.6.0
19 verbose npm v6.5.0
20 error code ELIFECYCLE
21 error errno 1
22 error smartthings-nodeproxy@1.0.0 start: node server.js
22 error Exit status 1
23 error Failed at the smartthings-nodeproxy@1.0.0 start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]