[RELEASE] Honeywell / Ademco Vista 20P Integration

Hey @solutionssquad - yes all of this will also run on Windows… here’s the basic steps:

  1. Install Node and get it setup - here’s a tutorial: http://blog.teamtreehouse.com/install-node-js-npm-windows
  2. Download the SmartThings Node Proxy source from here: https://github.com/redloro/smartthings/tree/master/smartthings-nodeproxy
  3. Put it in a folder and run start server.js from the command line (ignore the restart.me command)
  4. Follow the rest of the steps to configure and connect as outlined here: https://github.com/redloro/smartthings

If you want to get this running on a Pi… it’s basically the same thing, but you would be on Linux.

Good luck!

1 Like

Thanks for this solution! The Alarm Server solution was doing my head in. Cheers mate.
All running here.

I am trying to install this application on a raspberry pi 3 but was unable to install serialport 1.7.4 because of incompatability errors. Finally installed with version 2,1,2 and Envistalink 4.
Whenever I press Done in the Smartthings app I get 4 lines in the log file starting with ::ffff. and nothing else. All this stuff is new to me but try to follow simple instructions. Thanks

SmartThings Node Proxy listening at http://:::8080
Loaded plugin: envistalink
Connected to Envisalink at 192.168.1.199:4025
{“type”:“partition”,“partition”:1,“state”:“ready”,“alpha”:“DISARMED Ready to Arm”}
::ffff:192.168.1.58 GET /subscribe/192.168.1.58:39500
::ffff:192.168.1.58 GET /plugins/envisalink/config/192.168.1.199:4025:tester:1947
::ffff:192.168.1.58 GET /plugins/envisalink/config/192.168.1.199:4025:tester:1947
::ffff:192.168.1.58 GET /plugins/envisalink/discover
{“type”:“zone”,“partition”:1,“zone”:18,“state”:“open”}
{“type”:“partition”,“partition”:1,“state”:“notready”,“alpha”:“FAULT 18 LIVING ROOM MOTION”}
{“type”:“zone”,“partition”:1,“zone”:18,“state”:“closed”}
{“type”:“partition”,“partition”:1,“state”:“ready”,“alpha”:“DISARMED Ready to Arm”}

I think that is the SmartAPP sending these commands to your SmartThings Hub and in turn the SmartThings Hub sends these HTTP commands to your SmartThings Node Proxy web server on your RaspberryPI at 192.168.1.58:8080. Mine does this as well without the ::ffff prefixes (see below).

The log file shows that your Vista alarm is relaying commands to the SmartThings Proxy… which should in turn send them to your hub…

Here is my log file below (with sensitive information removed of altered)

SmartThings Node Proxy listening at http://0.0.0.0:8080
Starting Discovery
GetZone Data
Loaded plugin: envisalink
Connected to Envisalink at 10.0.0.37:4025
{"type":"partition","partition":1,"state":"ready","alpha":"****DISARMED****  Ready to Arm"}
{"type":"zone","partition":1,"zone":7,"state":"open"}
{"type":"partition","partition":1,"state":"notready","alpha":"FAULT 07 MOTION KITCHEN BEDROOM"}
{"type":"zone","partition":1,"zone":7,"state":"closed"}
{"type":"partition","partition":1,"state":"ready","alpha":"****DISARMED****  Ready to Arm"}
{"type":"zone","partition":1,"zone":7,"state":"open"}
{"type":"partition","partition":1,"state":"notready","alpha":"FAULT 07 MOTION KITCHEN BEDROOM"}
{"type":"zone","partition":1,"zone":7,"state":"closed"}
{"type":"partition","partition":1,"state":"ready","alpha":"****DISARMED****  Ready to Arm"}
{"type":"zone","partition":1,"zone":7,"state":"open"}
{"type":"partition","partition":1,"state":"notready","alpha":"FAULT 07 MOTION KITCHEN BEDROOM"}
{"type":"zone","partition":1,"zone":7,"state":"closed"}
{"type":"partition","partition":1,"state":"ready","alpha":"****DISARMED****  Ready to Arm"}
APP.use 10.0.0.45 GET /subscribe/10.0.0.45:39500
APP.use 10.0.0.45 GET /plugins/envisalink/config/10.0.0.37:4025:user:{Your Alarm Codes)
APP.use 10.0.0.45 GET /plugins/envisalink/config/10.0.0.37:4025:user:{Your Alarm Codes)
{"type":"zone","partition":1,"zone":7,"state":"open"}
{"type":"partition","partition":1,"state":"notready","alpha":"FAULT 07 MOTION KITCHEN 

Here is my config file:

{
“port”: 8080,
“authCode”: “Your secret-key that matches in SmartAPP”,
“raspilink”: {
“nodeAddress_1”: “10.0.0.56”,
“nodeName_1”: “Alarmdecoder”,
“nodeAddress_2”: “10.0.0.39”,
“nodeName_2”: “RaspberryPi2”,
“nodeAddress_3”: “10.0.0.41”,
“nodeName_3”: “RaspberryPi3”
},
“envisalink”: {
“address”: “10.0.0.37”,
“port”: “4025”,
“password”: “The password of your envisalink system”,
“securityCode”: {Your Alarm Codes),
“panelConfig”: {
“type”: “discover”,
“partitions”: [
{
“partition”: 1,
“name”: “Security Panel”
}
],
“zones”: [
{
“zone”: 1,
“type”: “contact”,
“name”: “Honey -Front Door”
},
{
“zone”: 2,
“type”: “contact”,
“name”: “Honey -Walkout LL Door”
},
{
“zone”: 3,
“type”: “contact”,
“name”: “Honey -Side of Garage Door”
},
{
“zone”: 4,
“type”: “motion”,
“name”: “Honey -Living Rm/Hall”
},
{
“zone”: 5,
“type”: “motion”,
“name”: “Honey -Upstairs”
},
{
“zone”: 6,
“type”: “motion”,
“name”: “Honey -Garage”
},
{
“zone”: 7,
“type”: “motion”,
“name”: “Honey -Kitchen/BR/Living Rm”
},
{
“zone”: 8,
“type”: “contact”,
“name”: “Honey -Panic”
},
{
“zone”: 9,
“type”: “contact”,
“name”: “Honey -Kitchen to Garage Door”
},
{
“zone”: 10,
“type”: “contact”,
“name”: “Honey -Sound Theater Rm”
},
{
“zone”: 11,
“type”: “contact”,
“name”: “Honey -Sound Living Rm”
},
{
“zone”: 12,
“type”: “contact”,
“name”: “Honey -Sound Furnance Rm”
},
{
“zone”: 13,
“type”: “smoke”,
“name”: “Honey -Fire Upstairs”
},
{
“zone”: 14,
“type”: “smoke”,
“name”: “Honey -Fire Main Fl”
},
{
“zone”: 15,
“type”: “smoke”,
“name”: “Honey -Fire Furnance”
}
]
},
“installerCode”: “Your installer code for Vista - Optional”
},
“notify”: {
“address”: “10.0.0.45”,
“port”: “39500”
},
“root”: “/home/pi/smartthings-nodeproxy/”,
“pidPath”: “/home/pi/smartthings-nodeproxy/pids”,
“sockPath”: “/home/pi/smartthings-nodeproxy/sock”,
“loglength”: 100,
“logstream”: false,
“columns”: [
“uid”,
“command”,
“script”,
“forever”,
“pid”,
“id”,
“logfile”,
“uptime”
]
}

Thanks Kurtsanders for the input but this did not change anything for me. The second and third lines of your logfile, Starting Discovery and GetZone Data are missing from my logfile. Did you install serialport version 1.7.4 on your Pi3. what versions of node and npm did you install. Thanks again

I have NPM 3.8.1 and Node v4.4.0 installed. I do not have serialport installed.

@Boone can you share the contents of your log file on the Pi3? Looks like it’s probably some setup issue.

redloro I just updated to Node V4.4.5 and NPM 3.9.3
config.json
{
“port”: 8080,
“authCode”: “tester”,
“envisalink”: {
“address”: “192.168.1.199”,
“port”: “4025”,
“password”: “tester”,
“securityCode”: “1947”,
“panelConfig”: {
“type”: “discover”,
“partitions”: [
{
“partition”: 1,
“name”: “Security Panel”
}
],
“zones”: [
{
“zone”: 2,
“type”: “contact”,
“name”: “Exterior Doors House”
},
{
“zone”: 3,
“type”: “contact”,
“name”: “Exterior Doors Workshop”
},
{
“zone”: 4,
“type”: “motion”,
“name”: “Motion Detector Workshop”
},
{
“zone”: 5,
“type”: “motion”,
“name”: “West Garage”
},
{
“zone”: 6,
“type”: “motion”,
“name”: “East Garage”
},
{
“zone”: 10,
“type”: “contact”,
“name”: “Glass Break Master Bath”
},
{
“zone”: 11,
“type”: “contact”,
“name”: “Glass Break Master Bedroom”
},
{
“zone”: 12,
“type”: “contact”,
“name”: “Glass Break Front Door”
},
{
“zone”: 13,
“type”: “contact”,
“name”: “Glass Break Great Room”
},
{
“zone”: 14,
“type”: “contact”,
“name”: “Glass Break Kitchen”
},
{
“zone”: 15,
“type”: “contact”,
“name”: “Glass Break Dining Room”
},
{
“zone”: 16,
“type”: “contact”,
“name”: “Glass Break Front Bedroom”
},
{
“zone”: 17,
“type”: “contact”,
“name”: “Glass Break Small Bedroom”
},
{
“zone”: 18,
“type”: “motion”,
“name”: “Motion Detector Great Room”
},
{
“zone”: 19,
“type”: “motion”,
“name”: “Motion Detector Kitchen”
},
{
“zone”: 20,
“type”: “contact”,
“name”: “Service Room Door”
},
{
“zone”: 21,
“type”: “contact”,
“name”: “Laundry Room Door”
},
{
“zone”: 22,
“type”: “contact”,
“name”: “Kitchen Door”
},
{
“zone”: 23,
“type”: “contact”,
“name”: “Patio Door”
},
{
“zone”: 24,
“type”: “contact”,
“name”: “Front Door”
},
{
“zone”: 25,
“type”: “contact”,
“name”: “Garage Side Door”
},
{
“zone”: 26,
“type”: “contact”,
“name”: “Garage Back Door”
}
]
}
},
“notify”: {
“address”: “192.168.1.58”,
“port”: “39500”
}

*****************log file, ::ffff lines are created when I hit Done in Smartthings Honeywell App

SmartThings Node Proxy listening at http://:::8080
Loaded plugin: envistalink
Connected to Envisalink at 192.168.1.199:4025
{“type”:“partition”,“partition”:1,“state”:“ready”,“alpha”:“DISARMED Ready to Arm”}
::ffff:192.168.1.58 GET /subscribe/192.168.1.58:39500
::ffff:192.168.1.58 GET /plugins/envisalink/config/192.168.1.199:4025:tester:1947
::ffff:192.168.1.58 GET /plugins/envisalink/config/192.168.1.199:4025:tester:1947
::ffff:192.168.1.58 GET /plugins/envisalink/discover

************Terminal output from Install

pi@raspberrypi:~/smartthings-nodeproxy $ npm install
SmartThingsNodeProxy@0.0.1 /home/pi/smartthings-nodeproxy
±- express@4.13.4
¦ ±- accepts@1.2.13
¦ ¦ ±- mime-types@2.1.11
¦ ¦ ¦ ±- mime-db@1.23.0
¦ ¦ ±- negotiator@0.5.3
¦ ±- array-flatten@1.1.1
¦ ±- content-disposition@0.5.1
¦ ±- content-type@1.0.2
¦ ±- cookie@0.1.5
¦ ±- cookie-signature@1.0.6
¦ ±- debug@2.2.0
¦ ¦ ±- ms@0.7.1
¦ ±- depd@1.1.0
¦ ±- escape-html@1.0.3
¦ ±- etag@1.7.0
¦ ±- finalhandler@0.4.1
¦ ¦ ±- unpipe@1.0.0
¦ ±- fresh@0.3.0
¦ ±- merge-descriptors@1.0.1
¦ ±- methods@1.1.2
¦ ±- on-finished@2.3.0
¦ ¦ ±- ee-first@1.1.1
¦ ±- parseurl@1.3.1
¦ ±- path-to-regexp@0.1.7
¦ ±- proxy-addr@1.0.10
¦ ¦ ±- forwarded@0.1.0
¦ ¦ ±- ipaddr.js@1.0.5
¦ ±- qs@4.0.0
¦ ±- range-parser@1.0.3
¦ ±- send@0.13.1
¦ ¦ ±- destroy@1.0.4
¦ ¦ ±- http-errors@1.3.1
¦ ¦ ¦ ±- inherits@2.0.1
¦ ¦ ±- mime@1.3.4
¦ ¦ ±- statuses@1.2.1
¦ ±- serve-static@1.10.2
¦ ±- type-is@1.6.13
¦ ¦ ±- media-typer@0.3.0
¦ ±- utils-merge@1.0.0
¦ ±- vary@1.0.1
±- forever@0.15.2
¦ ±- cliff@0.1.10
¦ ¦ ±- colors@1.0.3
¦ ¦ ±- eyes@0.1.8
¦ ±- clone@1.0.2
¦ ±- colors@0.6.2
¦ ±- flatiron@0.4.3
¦ ¦ ±- broadway@0.3.6
¦ ¦ ¦ ±- cliff@0.1.9
¦ ¦ ¦ ±- nconf@0.6.9
¦ ¦ ¦ ¦ ±- async@0.2.9
¦ ¦ ¦ ¦ ±- optimist@0.6.0
¦ ¦ ¦ ±- winston@0.8.0
¦ ¦ ±- director@1.2.7
¦ ¦ ±- optimist@0.6.0
¦ ¦ ±- prompt@0.2.14
¦ ¦ ±- read@1.0.7
¦ ¦ ¦ ±- mute-stream@0.0.6
¦ ¦ ±- revalidator@0.1.8
¦ ±- forever-monitor@1.6.0
¦ ¦ ±- chokidar@1.5.1
¦ ¦ ¦ ±- anymatch@1.3.0
¦ ¦ ¦ ¦ ±- arrify@1.0.1
¦ ¦ ¦ ¦ ±- micromatch@2.3.8
¦ ¦ ¦ ¦ ±- arr-diff@2.0.0
¦ ¦ ¦ ¦ ¦ ±- arr-flatten@1.0.1
¦ ¦ ¦ ¦ ±- array-unique@0.2.1
¦ ¦ ¦ ¦ ±- braces@1.8.5
¦ ¦ ¦ ¦ ¦ ±- expand-range@1.8.2
¦ ¦ ¦ ¦ ¦ ¦ ±- fill-range@2.2.3
¦ ¦ ¦ ¦ ¦ ¦ ±- is-number@2.1.0
¦ ¦ ¦ ¦ ¦ ¦ ±- isobject@2.1.0
¦ ¦ ¦ ¦ ¦ ¦ ±- randomatic@1.1.5
¦ ¦ ¦ ¦ ¦ ¦ ±- repeat-string@1.5.4
¦ ¦ ¦ ¦ ¦ ±- preserve@0.2.0
¦ ¦ ¦ ¦ ¦ ±- repeat-element@1.1.2
¦ ¦ ¦ ¦ ±- expand-brackets@0.1.5
¦ ¦ ¦ ¦ ¦ ±- is-posix-bracket@0.1.1
¦ ¦ ¦ ¦ ±- extglob@0.3.2
¦ ¦ ¦ ¦ ±- filename-regex@2.0.0
¦ ¦ ¦ ¦ ±- kind-of@3.0.3
¦ ¦ ¦ ¦ ¦ ±- is-buffer@1.1.3
¦ ¦ ¦ ¦ ±- normalize-path@2.0.1
¦ ¦ ¦ ¦ ±- object.omit@2.0.0
¦ ¦ ¦ ¦ ¦ ±- for-own@0.1.4
¦ ¦ ¦ ¦ ¦ ¦ ±- for-in@0.1.5
¦ ¦ ¦ ¦ ¦ ±- is-extendable@0.1.1
¦ ¦ ¦ ¦ ±- parse-glob@3.0.4
¦ ¦ ¦ ¦ ¦ ±- glob-base@0.3.0
¦ ¦ ¦ ¦ ¦ ±- is-dotfile@1.0.2
¦ ¦ ¦ ¦ ±- regex-cache@0.4.3
¦ ¦ ¦ ¦ ±- is-equal-shallow@0.1.3
¦ ¦ ¦ ¦ ±- is-primitive@2.0.0
¦ ¦ ¦ ±- async-each@1.0.0
¦ ¦ ¦ ±- glob-parent@2.0.0
¦ ¦ ¦ ±- is-binary-path@1.0.1
¦ ¦ ¦ ¦ ±- binary-extensions@1.4.1
¦ ¦ ¦ ±- is-glob@2.0.1
¦ ¦ ¦ ¦ ±- is-extglob@1.0.0
¦ ¦ ¦ ±- readdirp@2.0.0
¦ ¦ ¦ ±- graceful-fs@4.1.4
¦ ¦ ¦ ±- minimatch@2.0.10
¦ ¦ ¦ ±- readable-stream@2.1.4
¦ ¦ ¦ ±- buffer-shims@1.0.0
¦ ¦ ¦ ±- core-util-is@1.0.2
¦ ¦ ¦ ±- isarray@1.0.0
¦ ¦ ¦ ±- process-nextick-args@1.0.7
¦ ¦ ¦ ±- string_decoder@0.10.31
¦ ¦ ¦ ±- util-deprecate@1.0.2
¦ ¦ ±- minimatch@2.0.10
¦ ¦ ¦ ±- brace-expansion@1.1.4
¦ ¦ ¦ ±- balanced-match@0.4.1
¦ ¦ ¦ ±- concat-map@0.0.1
¦ ¦ ±- ps-tree@0.0.3
¦ ¦ ±- event-stream@0.5.3
¦ ¦ ±- optimist@0.2.8
¦ ±- nconf@0.6.9
¦ ¦ ±- async@0.2.9
¦ ¦ ±- optimist@0.6.0
¦ ±- nssocket@0.5.3
¦ ¦ ±- eventemitter2@0.4.14
¦ ¦ ±- lazy@1.0.11
¦ ±- object-assign@3.0.0
¦ ±- optimist@0.6.1
¦ ¦ ±- minimist@0.0.10
¦ ¦ ±- wordwrap@0.0.3
¦ ±- path-is-absolute@1.0.0
¦ ±- prettyjson@1.1.3
¦ ¦ ±- colors@1.1.2
¦ ¦ ±- minimist@1.2.0
¦ ±- shush@1.0.0
¦ ¦ ±- caller@0.0.1
¦ ¦ ¦ ±- tape@2.3.3
¦ ¦ ¦ ±- deep-equal@0.1.2
¦ ¦ ¦ ±- defined@0.0.0
¦ ¦ ¦ ±- jsonify@0.0.0
¦ ¦ ¦ ±- resumer@0.0.0
¦ ¦ ¦ ±- through@2.3.8
¦ ¦ ±- strip-json-comments@0.1.3
¦ ±- timespan@2.3.0
¦ ±- utile@0.2.1
¦ ¦ ±- async@0.2.10
¦ ¦ ±- deep-equal@1.0.1
¦ ¦ ±- i@0.3.5
¦ ¦ ±- mkdirp@0.5.1
¦ ¦ ¦ ±- minimist@0.0.8
¦ ¦ ±- ncp@0.4.2
¦ ¦ ±- rimraf@2.5.2
¦ ¦ ±- glob@7.0.3
¦ ¦ ±- inflight@1.0.5
¦ ¦ ¦ ±- wrappy@1.0.2
¦ ¦ ±- minimatch@3.0.0
¦ ¦ ±- once@1.3.3
¦ ±- winston@0.8.3
¦ ±- cycle@1.0.3
¦ ±- isstream@0.1.2
¦ ±- pkginfo@0.3.1
¦ ±- stack-trace@0.0.9
±- nconf@0.8.4
±- async@1.5.2
±- ini@1.3.4
±- secure-keys@1.0.0
±- yargs@3.32.0
±- camelcase@2.1.1
±- cliui@3.2.0
¦ ±- strip-ansi@3.0.1
¦ ¦ ±- ansi-regex@2.0.0
¦ ±- wrap-ansi@2.0.0
±- decamelize@1.2.0
±- os-locale@1.4.0
¦ ±- lcid@1.0.0
¦ ±- invert-kv@1.0.0
±- string-width@1.0.1
¦ ±- code-point-at@1.0.0
¦ ¦ ±- number-is-nan@1.0.0
¦ ±- is-fullwidth-code-point@1.0.0
±- window-size@0.1.4
±- y18n@3.2.1

npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.0.12
pi@raspberrypi:~/smartthings-nodeproxy $
pi@raspberrypi:~/Desktop/files $

Thanks

@Boone it looks like it’s all working as it should… when you hit “Done” in the SmartApp, it sends a discovery request to the SmartThings Node Proxy service running on the Pi3… it returns the configuration and zone info so that the appropriate zones get automatically setup. If you exit and re-open the SmartThings app on your phone, you should see all the zones configured… and you would use the Honeywell Security thing to arm/disarm your system.

If you do not see all your zones automatically configured, you may need to re-open the SmartApp and hit “Done” again to force another discovery request.

I usually do not re-run the Honeywell discovery once I have all the Vista alarm zones captured by the Smartthings App. If you do, you will need to re-add them back into a room (if you use a SmartThings “room” for your Home Alarm).

I have tried everything to make this thing work but no data is being returned to th ST Hub. The NP logs are filling up with lots of activity from the Zones but none is picked up by the ST Hub. I have installed the smart app and device handlers many times, reboot the ST Hub, Hit Done too many times to count, it just adds four more lines to the NP logs. I get exactly the same behavour on 2 Android devices and an Ipad. Do you have any suggestions on how to debug this problem. THANKS

@Boone Yes - first let’s start with turning off your ST Hub (and pulling the batteries) so that it is completely power cycled… I’ve seen times where the ST Hub gets into a weird state and won’t process events.

Once you power cycled the ST Hub, go to the ST IDE, pull up the Honeywell Security SmartApp and uncomment the log.trace lines in the lanResponseHandler() method. Save/publish the SmartApp and then pull up Live Logging in the ST IDE.

Now on your phone/tablet, refresh the SmartApps (by pulling down and getting the spinning wheel) and then tap on the Honeywell Security smart app. Don’t change anything and just tap Done. Check ST Live Logging and report back what you find.

Thanks.

This is the logging File

e2cd986e-f644-40c1-b2ea-ca39726e9a89 9:40:07 PM: trace Body: null
e2cd986e-f644-40c1-b2ea-ca39726e9a89 9:40:07 PM: trace Headers: [HTTP/1.1 200 OK:, X-Powered-By:Express, Date:Tue, 31 May 2016 01, Connection:keep-alive, Content-Length:0]
e2cd986e-f644-40c1-b2ea-ca39726e9a89 9:40:07 PM: trace SmartThings Node Proxy: index:17, mac:B827EBC379DF, ip:C0A80107, port:1F90, requestId:65566e23-2c6e-40b4-82dd-96f0f86d379f, headers:SFRUUC8xLjEgMjAwIE9LDQpYLVBvd2VyZWQtQnk6IEV4cHJlc3MNCkRhdGU6IFR1ZSwgMzEgTWF5IDIwMTYgMDE6NDA6MDcgR01UDQpDb25uZWN0aW9uOiBrZWVwLWFsaXZlDQpDb250ZW50LUxlbmd0aDogMA==, body:
e2cd986e-f644-40c1-b2ea-ca39726e9a89 9:40:07 PM: trace Body: null
e2cd986e-f644-40c1-b2ea-ca39726e9a89 9:40:07 PM: trace Headers: [HTTP/1.1 200 OK:, X-Powered-By:Express, Date:Tue, 31 May 2016 01, Connection:keep-alive, Content-Length:0]
e2cd986e-f644-40c1-b2ea-ca39726e9a89 9:40:07 PM: trace SmartThings Node Proxy: index:17, mac:B827EBC379DF, ip:C0A80107, port:1F90, requestId:10ad1b27-96ff-4aa3-84cd-749afd132f7f, headers:SFRUUC8xLjEgMjAwIE9LDQpYLVBvd2VyZWQtQnk6IEV4cHJlc3MNCkRhdGU6IFR1ZSwgMzEgTWF5IDIwMTYgMDE6NDA6MDYgR01UDQpDb25uZWN0aW9uOiBrZWVwLWFsaXZlDQpDb250ZW50LUxlbmd0aDogMA==, body:
e2cd986e-f644-40c1-b2ea-ca39726e9a89 9:40:07 PM: debug getChildDevices(true), children=0
e2cd986e-f644-40c1-b2ea-ca39726e9a89 9:40:06 PM: debug getChildDevices(true), children=0

Thanks

@Boone Is that everything?? Doesn’t look right at all. What version of the ST hub do you have and what firmware version?

Firmware Version 000.014.00040
Hardware Version hub v2, US customer Rev E

@Boone If you open a door and then close it, do you see anything in the logs on the Pi3 or ST Live Logging??

All of the zone activity are in the log file on the pi maybe a few 1000 entries over the past 24 hrs. None of it is in the trace files from the St hub

There are also a few of those errors in the pi log file
Notify error: Error: read ECONNRESET
Notify error: Error: read ECONNRESET
Notify error: Error: read ECONNRESET
Notify error: Error: read ECONNRESET

This morning I am getting more info in trace files
e2cd986e-f644-40c1-b2ea-ca39726e9a89 7:11:43 AM: trace Body: [partition:1, state:closed, type:zone, zone:19]
e2cd986e-f644-40c1-b2ea-ca39726e9a89 7:11:43 AM: trace Headers: [NOTIFY /notify HTTP/1.1:, CONTENT-TYPE:application/json, CONTENT-LENGTH:56, stnp-plugin:envistalink, Host:192.168.1.58, Connection:close]
e2cd986e-f644-40c1-b2ea-ca39726e9a89 7:11:43 AM: trace SmartThings Node Proxy: index:08, mac:B827EBC379DF, headers:Tk9USUZZIC9ub3RpZnkgSFRUUC8xLjENCkNPTlRFTlQtVFlQRTogYXBwbGljYXRpb24vanNvbg0KQ09OVEVOVC1MRU5HVEg6IDU2DQpzdG5wLXBsdWdpbjogZW52aXN0YWxpbmsNCkhvc3Q6IDE5Mi4xNjguMS41ODozOTUwMA0KQ29ubmVjdGlvbjogY2xvc2U=, body:eyJ0eXBlIjoiem9uZSIsInBhcnRpdGlvbiI6MSwiem9uZSI6MTksInN0YXRlIjoiY2xvc2VkIn0=
e2cd986e-f644-40c1-b2ea-ca39726e9a89 7:11:43 AM: trace Body: [partition:1, alpha:DISARMED Ready to Arm, state:ready, type:partition]
e2cd986e-f644-40c1-b2ea-ca39726e9a89 7:11:43 AM: trace Headers: [NOTIFY /notify HTTP/1.1:, CONTENT-TYPE:application/json, CONTENT-LENGTH:91, stnp-plugin:envistalink, Host:192.168.1.58, Connection:close]
e2cd986e-f644-40c1-b2ea-ca39726e9a89 7:11:43 AM: trace SmartThings Node Proxy: index:03, mac:B827EBC379DF, headers:Tk9USUZZIC9ub3RpZnkgSFRUUC8xLjENCkNPTlRFTlQtVFlQRTogYXBwbGljYXRpb24vanNvbg0KQ09OVEVOVC1MRU5HVEg6IDkxDQpzdG5wLXBsdWdpbjogZW52aXN0YWxpbmsNCkhvc3Q6IDE5Mi4xNjguMS41ODozOTUwMA0KQ29ubmVjdGlvbjogY2xvc2U=, body:eyJ0eXBlIjoicGFydGl0aW9uIiwicGFydGl0aW9uIjoxLCJzdGF0ZSI6InJlYWR5IiwiYWxwaGEiOiIqKioqRElTQVJNRUQqKioqICBSZWFkeSB0byBBcm0ifQ==
e2cd986e-f644-40c1-b2ea-ca39726e9a89 7:11:40 AM: trace Body: [partition:1, state:open, type:zone, zone:19]
e2cd986e-f644-40c1-b2ea-ca39726e9a89 7:11:40 AM: trace Headers: [NOTIFY /notify HTTP/1.1:, CONTENT-TYPE:application/json, CONTENT-LENGTH:54, stnp-plugin:envistalink, Host:192.168.1.58, Connection:close]
e2cd986e-f644-40c1-b2ea-ca39726e9a89 7:11:40 AM: trace SmartThings Node Proxy: index:06, mac:B827EBC379DF, headers:Tk9USUZZIC9ub3RpZnkgSFRUUC8xLjENCkNPTlRFTlQtVFlQRTogYXBwbGljYXRpb24vanNvbg0KQ09OVEVOVC1MRU5HVEg6IDU0DQpzdG5wLXBsdWdpbjogZW52aXN0YWxpbmsNCkhvc3Q6IDE5Mi4xNjguMS41ODozOTUwMA0KQ29ubmVjdGlvbjogY2xvc2U=, body:eyJ0eXBlIjoiem9uZSIsInBhcnRpdGlvbiI6MSwiem9uZSI6MTksInN0YXRlIjoib3BlbiJ9
e2cd986e-f644-40c1-b2ea-ca39726e9a89 7:11:40 AM: trace Body: [partition:1, alpha:FAULT 19 KITCHENMOTION, state:notready, type:partition]
e2cd986e-f644-40c1-b2ea-ca39726e9a89 7:11:40 AM: trace Headers: [NOTIFY /notify HTTP/1.1:, CONTENT-TYPE:application/json, CONTENT-LENGTH:86, stnp-plugin:envistalink, Host:192.168.1.58, Connection:close]
e2cd986e-f644-40c1-b2ea-ca39726e9a89 7:11:40 AM: trace SmartThings Node Proxy: index:07, mac:B827EBC379DF, headers:Tk9USUZZIC9ub3RpZnkgSFRUUC8xLjENCkNPTlRFTlQtVFlQRTogYXBwbGljYXRpb24vanNvbg0KQ09OVEVOVC1MRU5HVEg6IDg2DQpzdG5wLXBsdWdpbjogZW52aXN0YWxpbmsNCkhvc3Q6IDE5Mi4xNjguMS41ODozOTUwMA0KQ29ubmVjdGlvbjogY2xvc2U=, body:eyJ0eXBlIjoicGFydGl0aW9uIiwicGFydGl0aW9uIjoxLCJzdGF0ZSI6Im5vdHJlYWR5IiwiYWxwaGEiOiJGQVVMVCAxOSBLSVRDSEVOTU9USU9OIn0=
e2cd986e-f644-40c1-b2ea-ca39726e9a89 7:11:25 AM: trace Body: null
e2cd986e-f644-40c1-b2ea-ca39726e9a89 7:11:25 AM: trace Headers: [HTTP/1.1 200 OK:, X-Powered-By:Express, Date:Tue, 31 May 2016 11, Connection:keep-alive, Content-Length:0]
e2cd986e-f644-40c1-b2ea-ca39726e9a89 7:11:25 AM: trace SmartThings Node Proxy: index:17, mac:B827EBC379DF, ip:C0A80107, port:1F90, requestId:606f49cf-2534-40dc-bbb6-34714f807c05, headers:SFRUUC8xLjEgMjAwIE9LDQpYLVBvd2VyZWQtQnk6IEV4cHJlc3MNCkRhdGU6IFR1ZSwgMzEgTWF5IDIwMTYgMTE6MTE6MjQgR01UDQpDb25uZWN0aW9uOiBrZWVwLWFsaXZlDQpDb250ZW50LUxlbmd0aDogMA==, body:

This is my latest observations
When I hit done in smart app, the body of trace file is null

All Zone activity is in the body of the trace file.

© 2019 SmartThings, Inc. All Rights Reserved. Terms of Use | Privacy Policy

SmartThings; SmartApps®; Physical Graph; Hello, Home; and Hello, Smart Home are all trademarks of the SmartThings, Inc.