SmartThings Community

[RELEASE] Honeywell / Ademco Vista 20P Integration

honeywell
dth_security
smartapp_security
project_security
alarmdecoder

(A Smith) #713

Hi @redloro -

I have been playing with this trying to get it working for a few days now, and am stumped at this point. I have Node up and running fine, and can see it, and can hit if via HTTP within my network. I see events from my Honeywell system, but when I try to run the setup in SmartThings, I get no new things added. In ST IDE, all I see is the following:

5:39:03 PM: debug getChildDevices(true), children=0
5:39:03 PM: trace getPhrases(), state.welcomeIssue = null

Any ideas?


#714

Can you send me the output from STNP when you save the SmartApp with “Discover Zones” enabled? Also send me your config.json


(Jason Bottjen) #715

OK, more help requests… :slight_smile:

I can get STNP to run correctly w/node.js on my Synology, but I can’t get it to autostart. And even then, running it w/upstart creates very large log files I now have to figure out how to manage…

Is there a way to make a Docker container for this, and run it on a synology NAS? I would really prefer that over having to SSH into the NAS regularly to kick off the server.js…


#716

Yep - there’s a dockerfile and instructions here: https://github.com/redloro/smartthings/tree/master/docker

Good luck!


(A Smith) #717

@redloro -

Thanks for the quick response. STNP does not show any activity at all, except any events from the alarm panel. Here is a quick example:

[2017-12-15T14:55:44.341Z] [evl3] {“type”:“zone”,“partition”:1,“zone”:18,“state”:“open”}
[2017-12-15T14:55:44.343Z] [evl3] {“type”:“partition”,“partition”:1,“state”:“notready”,“alpha”:“FAULT 18 FOYER MOTION DETECTOR”}
[2017-12-15T14:55:46.850Z] [evl3] {“type”:“zone”,“partition”:1,“zone”:“18”,“state”:“closed”}
[2017-12-15T14:55:46.851Z] [evl3] {“type”:“partition”,“partition”:1,“state”:“ready”,“alpha”:“DISARMED Ready to Arm”}

Also, here is the config.json

{
“port”: 8080,
“authCode”: “*****”,
“rnet”: {
“c-series”: false,
“serialPort”: “/dev/usbser”,
“sources”: [
“Sonos”,
“Airplay”,
“Apple TV”,
“Source 4”,
“Source 5”,
“Source 6”
],
“controllerConfig”: {
“type”: “discover”,
“controllers”: [{
“controller”: 0,
“zones”: [
{“zone”: 0, “name”: “Family Room”},
{“zone”: 1, “name”: “Kitchen”},
{“zone”: 2, “name”: “Living Room”},
{“zone”: 3, “name”: “Patio”},
{“zone”: 4, “name”: “Dining Room”},
{“zone”: 5, “name”: “Office”}
]
}]
}
},
“mpr6z”: {
“serialPort”: “COM2”,
“baudRate”: 9600,
“sources”: [
“Sonos”,
“Airplay”,
“Apple TV”,
“Source 4”,
“Source 5”,
“Source 6”
],
“controllerConfig”: {
“type”: “discover”,
“controllers”: [{
“controller”: 1,
“zones”: [
{“zone”: 1, “name”: “Family Room”},
{“zone”: 2, “name”: “Kitchen”},
{“zone”: 3, “name”: “Living Room”},
{“zone”: 4, “name”: “Patio”},
{“zone”: 5, “name”: “Dining Room”},
{“zone”: 6, “name”: “Office”}
]
}]
}
},
“envisalink”: {
“address”: “192.168.1.190”,
“port”: “4025”,
“password”: “user”,
“securityCode”: “****”,
“dumpZoneTimer”: “0”,
“panelConfig”: {
“type”: “discover”,
“partitions”: [
{“partition”: 1, “name”: “Security Panel”}
],
“zones”: [
{“zone”: 10, “type”: “contact”, “name”: “Front Door”},
{“zone”: 11, “type”: “contact”, “name”: “Garage Entry Door”},
{“zone”: 12, “type”: “contact”, “name”: “Living Room Door”},
{“zone”: 13, “type”: “contact”, “name”: “Kitchen Door”},
{“zone”: 14, “type”: “contact”, “name”: “West Garage Door”},
{“zone”: 15, “type”: “contact”, “name”: “East Garage Door”},
{“zone”: 16, “type”: “motion”, “name”: “Living Room Motion”},
{“zone”: 17, “type”: “motion”, “name”: “Kitchen Motion”},
{“zone”: 16, “type”: “motion”, “name”: “Foyer Motion”}
]
}
},
“ad2usb”: {
“mode”: “serial”,
“securityCode”: “1234”,
“clearFaults”: true,
“serialPort”: “COM2”,
“address”: “192.168.2.22”,
“port”: “9001”,
“panelConfig”: {
“type”: “discover”,
“partitions”: [
{“partition”: 1, “name”: “Security Panel”}
],
“zones”: [
{“zone”: 1, “type”: “smoke”, “name”: “Smoke Detector”, “serial”: “0180036”},
{“zone”: 2, “type”: “contact”, “name”: “Front Door”, “serial”: “0180037”},
{“zone”: 3, “type”: “contact”, “name”: “Back Door”, “serial”: “0180038”},
{“zone”: 4, “type”: “contact”, “name”: “Kitchen Door”, “serial”: “0180039”},
{“zone”: 5, “type”: “contact”, “name”: “Kitchen Window”, “serial”: “0180040”}
]
}
},
“notify”: {
“address”: “192.168.50.250”,
“port”: “39500”
}
}


#718

Are you only running the evl plugin or did you also want to run the Russound, Monoprice and other plugins too??


(A Smith) #719

Only evl right now, but love the idea of what STNP can do, and may use it for others later.


#720

Ok - let’s start with a simplified version of config.json and then go from there… use the one included below…

Also - can the ST Hub actually send commands to the STNP?? Cause it looks like they may be on different subnets… the ST Hub is on 192.168.50.x and the EVL is on 192.168.1.x but where is the STNP??

{
	"port": 8080,
	"authCode": " ** ** * ",
	"envisalink": {
		"address": "192.168.1.190",
		"port": "4025",
		"password": "user",
		"securityCode": " ** ** ",
		"dumpZoneTimer": "0",
		"panelConfig": {
			"type ": "discover",
			"partitions": [{
				"partition ": 1,
				"name": "Security Panel"
			}],
			"zones": [{
					"zone": 10,
					"type": "contact",
					"name": "Front Door"
				},
				{
					"zone": 11,
					"type": "contact",
					"name": "Garage Entry Door"
				},
				{
					"zone": 12,
					"type": "contact",
					"name": "Living Room Door"
				},
				{
					"zone": 13,
					"type": "contact",
					"name": "Kitchen Door"
				},
				{
					"zone": 14,
					"type": "contact",
					"name": "West Garage Door"
				},
				{
					"zone": 15,
					"type": "contact",
					"name": "East Garage Door"
				},
				{
					"zone": 16,
					"type": "motion",
					"name": "Living Room Motion"
				},
				{
					"zone": 17,
					"type": "motion",
					"name": "Kitchen Motion"
				},
				{
					"zone": 16,
					"type": "motion",
					"name": "Foyer Motion"
				}
			]
		}
	},
	"notify": {
		"address": "192.168.50.250",
		"port": "39500"
	}
}

(George) #721

Hello again! I was finally able to get most everything working by just wiping out my rpi and starting from scratch as well as editing all the smart device and the app with the updated configs. So everything is now ahppy and working except for the stnp Service. I can only force it to work by doing forever server.js or node server.js at the prompt. I’m pretty sure I put everything back in the same place but I will send you what I have in a message so not to derail the thread. Thanks again! I don’t know if you setup the triggers yet but it is really cool now that it works from the App!


#722

@redloro I’ve been researching the service wrappers that you mentioned for Windows, it seems that qckwinsvc is the simplest one to use but i’m not quite sure how to configure it properly, i’ve installed it with both the envisalink.js and the server.js files and neither one seems to start the server the way doing it from the command line would. Any ideas on something i might be missing?

Thanks again


(A Smith) #723

@redloro -

Thank you for the continued assistance. I have played with this quite a bit, and seem to be making progress. While we did have our automation on different subnet, the way it is setup is they can still communicate. We communicate with all our other devices within the subnets fine.

I did move the ST hub to the same subnet to see, and have made a little progress, but now I am stumped more. I am getting an authentication error, and nothing is showing. Here is the error I am from STNP.

[2017-12-21T00:46:12.807Z] [stnp] ::ffff:192.168.1.191 GET /subscribe/192.168.1.191:39500
[2017-12-21T00:46:12.808Z] [stnp] Authentication error
[2017-12-21T00:46:12.954Z] [stnp] ::ffff:192.168.1.191 GET /plugins/envisalink/config/192.168.1.190:4025:user:user
[2017-12-21T00:46:12.955Z] [stnp] Authentication error
[2017-12-21T00:46:17.444Z] [stnp] ::ffff:192.168.1.191 GET /plugins/envisalink/discover
[2017-12-21T00:46:17.445Z] [stnp] Authentication error
[2017-12-21T00:46:57.380Z] [stnp] ::ffff:192.168.1.191 GET /subscribe/192.168.1.191:39500
[2017-12-21T00:47:02.161Z] [stnp] ::ffff:192.168.1.191 GET /plugins/envisalink/discover
[2017-12-21T00:47:02.164Z] [evl3] Completed panel discovery

I assume this is saying the authentication error is with the envisalink, so I attempted to log in to it directly through the browser with the user/user combination and can get in to it perfectly fine.

What am I missing?

PS - Once I get this working, where can we send “donations” :slight_smile:


(Ian Thomas) #724

I wanted to send a big thanks to @redloro

I recently bought a home with a hardwired Honeywell alarm system and wanted to use the sensors rather than the battery operated ones I had previously.

I have zero node js or groovy skills, but the instructions looked good, so I thought I would give it a try.

I purchased the Envisalink module and when I received it I installed and completed the setup in a couple of hours. The longest challenge was that it took me a while to figure out the STNP IP, which I had to find on the Envisalink network tab. I was mistakenly using the SmartThings Hub IP adddress!

This integration adds so much value to ST and my alarm system. A huge thank you.


(Gerry) #725

Hi @redloro. I’m hoping to use your project with my ST Vista 20P integration. I’m just getting going and had a few questions that I’m hoping you can answer.

Here is my Vista setup.

  • I have the usual door contacts, motions and smoke alarms. All sensors are just on partition 1 and work as you’d expect - Alarm goes off when the partition is armed.
  • I also have one Garage Door tilt sensor (just a contact I guess) that is on partition 2. Never armed. I just take notifications from that to perform notifications when the door is up. I first send a notification out at 5 minutes door up. Then 15 minutes until it drops. Then send final notificaiton that it’s closed

I’ll start with some simple questions.

  • Lets say the alarm is armed and a contact is opened setting off the alarm. Somehow I’d like to get notification that the alarm is now going off. From that, I’d like to send a TEXT and EMAIL to a list of contacts to notify them of the event (and the zone that caused it). Can that be done?
  • Or perhaps also send an alert out to the IOS ST app and notify it as well. If that can be done, what happens? Does the phone wake up and play a ringtone? I’ve not used the app yet so I have no idea.
  • Also. When the alarm is set off, I’d also like to run a scene (or whatever it’s called in ST) and turn all the lights on in the house. Can that be done?

That’s a start for now really. Appreciate the effort on the app! Thanks


(Michael Torgerson) #726

I have an odd problem I can’t figure out. My raspberry pi that I am running node.js on is plugged into a UPS and the raspberry pi is connected to a switch that is also connected to a UPS. My Vista 20p has a battery backup and stays running in the event of a power loss.

Every time I lose power, my existing server.js process hangs up and stops working. If I run forever stop server.js it tells me that it can’t find the pid.

If I manually start it over with forever start server.js then it starts running again with no issues.

Any ideas? I never could figure out how to get it to run if the raspberry pi reboots etc.


(Mark Storiale) #727

@redloro

Thanks so much for the project. I’ve been working on this for a while, but I’m stuck on the json file. I don’t know anything about json, so I am learning on the fly. I’ve edited the file for my setup and when I click beautify in json, I’m getting a syntax error. I know its something stupid, but I’m no familiar with it to know what to look for. Any help would be much appreciated. Safe and Happy New Year!!

Setup: Vista 20p, AD2USB, Raspberry Pi zero W

Config file currently in jsonmate

{
rt": 8080,
“authCode”: “secret-key”,
“ad2usb”: {
“mode”: “serial”,
“securityCode”: “1234”,
“clearFaults”: true,

"serialPort": "COM2",

"panelConfig": {  
  "type": "discover",
  "partitions": [
    {"partition": 1, "name": "Security Panel"}
  ],
  "zones": [
    {"zone": 1, "type": "smoke", "name": "Smoke Detector"},
    {"zone": 2, "type": "contact", "name": "Front Garage Door"},
    {"zone": 3, "type": "contact", "name": "Master Closet"},
    {"zone": 4, "type": "contact", "name": "Master Bathroom"},
    {"zone": 5, "type": "contact", "name": "Master Bedroom"},
    {"zone": 6, "type": "contact", "name": "Family Room"},
    {"zone": 7, "type": "contact", "name": "Slider"},
    {"zone": 8, "type": "contact", "name": "Kitchen"},
    {"zone": 9, "type": "contact", "name": "Living Room"},
    {"zone": 10, "type": "contact", "name": "Loft"},
    {"zone": 11, "type": "contact", "name": "Bedroom 1"},
    {"zone": 12, "type": "contact", "name": "Bedroom 2"},
    {"zone": 13, "type": "contact", "name": "Bedroom 3"}
  ]
}

},


(Gerry) #728
indent preformatted text by 4 spaces
{
"r": 8080,
"authCode": "secret - key", 
"ad2usb": {
	"mode": "serial",
	"securityCode": "1234",
	"clearFaults": true,

	"serialPort": "COM2",

	"panelConfig": {
		"type": "discover",
		"partitions": [{
			"partition": 1,
			"name": "Security Panel"
		}],
		"zones": [{
				"zone": 1,
				"type": "smoke",
				"name": "Smoke Detector"
			},
			{
				"zone": 2,
				"type": "contact",
				"name": "Front Garage Door"
			},
			{
				"zone": 3,
				"type": "contact",
				"name": "Master Closet"
			},
			{
				"zone": 4,
				"type": "contact",
				"name": "Master Bathroom"
			},
			{
				"zone": 5,
				"type": "contact",
				"name": "Master Bedroom"
			},
			{
				"zone": 6,
				"type": "contact",
				"name": "Family Room"
			},
			{
				"zone": 7,
				"type": "contact",
				"name": "Slider"
			},
			{
				"zone": 8,
				"type": "contact",
				"name": "Kitchen"
			},
			{
				"zone": 9,
				"type": "contact",
				"name": "Living Room"
			},
			{
				"zone": 10,
				"type": "contact",
				"name": "Loft"
			},
			{
				"zone": 11,
				"type": "contact",
				"name": "Bedroom 1"
			},
			{
				"zone": 12,
				"type": "contact",
				"name": "Bedroom 2"
			},
			{
				"zone": 13,
				"type": "contact",
				"name": "Bedroom 3"
			}
		]
	   }
    }
}

I’m struggling getting the code to be quoted above. Anyhow. Mismatched quotes and missing a bracket at end.


(Mark Storiale) #730

Thanks Gerry!! It worked like a charm.


(Mark Storiale) #731

Hey all. I’ve got everything set up, but I’ve run into a new problem.

My setup is a V20P, AD2USB, and a Raspberry Pi zero W.

When I fired up stnp, i got the error below
[2017-12-31T18:34:51.170Z] [ad2] AD2USB connect mode set to: serial
[2017-12-31T18:34:51.179Z] [ad2] AD2USB connection error: Error: Error: No such file or directory, cannot open COM2

One thing that was interesting was when I peformed the npm run install:ad2usb command, I got the errors below during the install

node-pre-gyp install --fallback-to-build

node-pre-gyp ERR! Tried to download(404): https://github.com/EmergingTechnologyA dvisors/node-serialport/releases/download/5.0.0/serialport-v5.0.0-node-v57-linux -arm.tar.gz
node-pre-gyp ERR! Pre-built binaries not found for serialport@5.0.0 and node@8.9 .3 (node-v57 ABI) (falling back to source compile with node-gyp)
make: Entering directory ‘/home/pi/downloads/smartthings-nodeproxy/node_modules/ serialport/build’

I went to the address it was trying to do the download from and it is a dead link.
Any help is most appreciated
HAPPY NEW YEAR!!


(A Smith) #732

@redloro

I made some progress over the holiday break, but am still not getting zones loaded in to ST. From everything I can see I would think it is working and everything is communicating correctly. Here is the STNP log;

Your environment has been set up for using Node.js .

smartthings-nodeproxy@1.0.0 start C:\SmartThings\smartthings-nodeproxy
node server.js

[2018-01-02T00:11:00.308Z] [stnp] SmartThings Node Proxy listening at http://:::8080
[2018-01-02T00:11:00.325Z] [stnp] Loaded plugin: envisalink
[2018-01-02T00:11:00.329Z] [evl3] Connected to Envisalink at 192.168.1.190:4025
[2018-01-02T00:11:04.586Z] [evl3] {“type”:“partition”,“partition”:1,“state”:“ready”,“alpha”:“DISARMED CHIME Ready to Arm”}
[2018-01-02T00:11:04.600Z] [stnp] Notify error: Error: connect EADDRNOTAVAIL 0.0.0.0:39500
[2018-01-02T00:11:39.051Z] [stnp] ::ffff:192.168.1.191 GET /subscribe/192.168.1.191:39500
[2018-01-02T00:11:46.221Z] [stnp] ::ffff:192.168.1.191 GET /plugins/envisalink/discover
[2018-01-02T00:11:46.225Z] [evl3] Completed panel discovery

Not sure what else to try on this one.


(Kajones02) #734

Hello all,

This is my first time posting a question on this forum as any question I have needed answered I have found. This forum is an awesome resource for all things Smartthings - thank you to the community!

I’ve read this entire thread, seen a couple people with the same issue, but still haven’t figured out a resolution so time to ask…

I’ve installed and gotten setup an Envisalink 4 on a Ademco 15P and have it working as it should
I’ve installed nodeJS v9.3.0 and STNP on a Raspberry P 3 running Raspian Stretch and the server appears to be working as it should
I’ve installed redloro’s smartapp and device type handlers. I can access the smartapp, input information and select discover zones. Everything seems to be working fine until this point, but after selecting done, my zones do not populate (they do not show up in my things). I have tried deleting and reinstalling the smarttapp and device type handlers from redloro’s GitHub depository. I have also enabled some of the debugging in the smartapp.

Here is my config.json
{
“port”: 8080,
“authCode”: “secret-key”,
“envisalink”: {
“address”: “192.168.1.125”,
“port”: “4025”,
“password”: “user”,
“securityCode”: “1234”,
“dumpZoneTimer”: “0”,
“panelConfig”: {
"type ": “discover”,
“partitions”: [
{
"partition ": 1,
“name”: “Security Panel”
}
],
“zones”: [
{
“zone”: 1,
“type”: “contact”,
“name”: “Front Door”
},
{
“zone”: 2,
“type”: “motion”,
“name”: “Living Room Motion”
},
{
“zone”: 3,
“type”: “contact”,
“name”: “Master Bedroom”
},
{
“zone”: 4,
“type”: “contact”,
“name”: “Kitchen / Back Door”
},
{
“zone”: 5,
“type”: “contact”,
“name”: “Dining”
},
{
“zone”: 6,
“type”: “contact”,
“name”: “Garage Entry”
}
]
}
},
“notify”: {
“address”: “192.168.1.94”,
“port”: “39500”
}
}

Here is my Smartthings log file:

cd496372-3173-4cce-8849-0d1d72ca68fd ‎9‎:‎00‎:‎44‎ ‎PM: trace Honeywell Security event: index:05, mac:B827EB6155D9, headers:Tk9USUZZIC9ub3RpZnkgSFRUUC8xLjENCkNPTlRFTlQtVFlQRTogYXBwbGljYXRpb24vanNvbg0KQ09OVEVOVC1MRU5HVEg6IDM5Mg0Kc3RucC1wbHVnaW46IGVudmlzYWxpbmsNCkhvc3Q6IDE5Mi4xNjguMS45NDozOTUwMA0KQ29ubmVjdGlvbjogY2xvc2U=, body:eyJ0eXBlICI6ImRpc2NvdmVyIiwicGFydGl0aW9ucyI6W3sicGFydGl0aW9uICI6MSwibmFtZSI6IlNlY3VyaXR5IFBhbmVsIn1dLCJ6b25lcyI6W3siem9uZSI6MSwidHlwZSI6ImNvbnRhY3QiLCJuYW1lIjoiRnJvbnQgRG9vciJ9LHsiem9uZSI6MiwidHlwZSI6Im1vdGlvbiIsIm5hbWUiOiJMaXZpbmcgUm9vbSBNb3Rpb24ifSx7InpvbmUiOjMsInR5cGUiOiJjb250YWN0IiwibmFtZSI6Ik1hc3RlciBCZWRyb29tIn0seyJ6b25lIjo0LCJ0eXBlIjoiY29udGFjdCIsIm5hbWUiOiJLaXRjaGVuIC8gQmFjayBEb29yIn0seyJ6b25lIjo1LCJ0eXBlIjoiY29udGFjdCIsIm5hbWUiOiJEaW5pbmcifSx7InpvbmUiOjYsInR5cGUiOiJjb250YWN0IiwibmFtZSI6IkdhcmFnZSBFbnRyeSJ9XX0=
cd496372-3173-4cce-8849-0d1d72ca68fd ‎9‎:‎00‎:‎44‎ ‎PM: trace [Honeywell Security] lanResponseHandler: [index:05, mac:B827EB6155D9, headers:Tk9USUZZIC9ub3RpZnkgSFRUUC8xLjENCkNPTlRFTlQtVFlQRTogYXBwbGljYXRpb24vanNvbg0KQ09OVEVOVC1MRU5HVEg6IDM5Mg0Kc3RucC1wbHVnaW46IGVudmlzYWxpbmsNCkhvc3Q6IDE5Mi4xNjguMS45NDozOTUwMA0KQ29ubmVjdGlvbjogY2xvc2U=, body:eyJ0eXBlICI6ImRpc2NvdmVyIiwicGFydGl0aW9ucyI6W3sicGFydGl0aW9uICI6MSwibmFtZSI6IlNlY3VyaXR5IFBhbmVsIn1dLCJ6b25lcyI6W3siem9uZSI6MSwidHlwZSI6ImNvbnRhY3QiLCJuYW1lIjoiRnJvbnQgRG9vciJ9LHsiem9uZSI6MiwidHlwZSI6Im1vdGlvbiIsIm5hbWUiOiJMaXZpbmcgUm9vbSBNb3Rpb24ifSx7InpvbmUiOjMsInR5cGUiOiJjb250YWN0IiwibmFtZSI6Ik1hc3RlciBCZWRyb29tIn0seyJ6b25lIjo0LCJ0eXBlIjoiY29udGFjdCIsIm5hbWUiOiJLaXRjaGVuIC8gQmFjayBEb29yIn0seyJ6b25lIjo1LCJ0eXBlIjoiY29udGFjdCIsIm5hbWUiOiJEaW5pbmcifSx7InpvbmUiOjYsInR5cGUiOiJjb250YWN0IiwibmFtZSI6IkdhcmFnZSBFbnRyeSJ9XX0=]
cd496372-3173-4cce-8849-0d1d72ca68fd ‎9‎:‎00‎:‎44‎ ‎PM: trace [Honeywell Security] lanResponseHandler: [index:15, mac:B827EB6155D9, ip:C0A8017B, port:1F90, requestId:d0389628-ae03-49ed-a425-4d299f292be0, headers:SFRUUC8xLjEgMjAwIE9LDQpYLVBvd2VyZWQtQnk6IEV4cHJlc3MNCkRhdGU6IFdlZCwgMDMgSmFuIDIwMTggMDM6MDA6NDQgR01UDQpDb25uZWN0aW9uOiBrZWVwLWFsaXZlDQpDb250ZW50LUxlbmd0aDogMA==, body:null]
cd496372-3173-4cce-8849-0d1d72ca68fd ‎9‎:‎00‎:‎44‎ ‎PM: trace Honeywell Security send command: /plugins/envisalink/discover
cd496372-3173-4cce-8849-0d1d72ca68fd ‎9‎:‎00‎:‎39‎ ‎PM: trace [Honeywell Security] lanResponseHandler: [index:16, mac:B827EB6155D9, ip:C0A8017B, port:1F90, requestId:de46c141-2610-4bcb-b24d-8d42baad8aae, headers:SFRUUC8xLjEgMjAwIE9LDQpYLVBvd2VyZWQtQnk6IEV4cHJlc3MNCkRhdGU6IFdlZCwgMDMgSmFuIDIwMTggMDM6MDA6MzkgR01UDQpDb25uZWN0aW9uOiBrZWVwLWFsaXZlDQpDb250ZW50LUxlbmd0aDogMA==, body:null]
cd496372-3173-4cce-8849-0d1d72ca68fd ‎9‎:‎00‎:‎39‎ ‎PM: trace [Honeywell Security] lanResponseHandler: [index:15, mac:B827EB6155D9, ip:C0A8017B, port:1F90, requestId:fa9b1ec2-ac9f-4433-8e5f-6a2666a2bd07, headers:SFRUUC8xLjEgMjAwIE9LDQpYLVBvd2VyZWQtQnk6IEV4cHJlc3MNCkRhdGU6IFdlZCwgMDMgSmFuIDIwMTggMDM6MDA6MzkgR01UDQpDb25uZWN0aW9uOiBrZWVwLWFsaXZlDQpDb250ZW50LUxlbmd0aDogMA==, body:null]
cd496372-3173-4cce-8849-0d1d72ca68fd ‎9‎:‎00‎:‎39‎ ‎PM: trace Honeywell Security send command: /plugins/envisalink/config/192.168.1.125:4025:user:0306
cd496372-3173-4cce-8849-0d1d72ca68fd ‎9‎:‎00‎:‎39‎ ‎PM: trace Honeywell Security send command: /subscribe/192.168.1.94:39500
cd496372-3173-4cce-8849-0d1d72ca68fd ‎9‎:‎00‎:‎39‎ ‎PM: debug getChildDevices(true), children=0
cd496372-3173-4cce-8849-0d1d72ca68fd ‎9‎:‎00‎:‎35‎ ‎PM: trace Honeywell Security event: index:06, mac:B827EB6155D9, headers:Tk9USUZZIC9ub3RpZnkgSFRUUC8xLjENCkNPTlRFTlQtVFlQRTogYXBwbGljYXRpb24vanNvbg0KQ09OVEVOVC1MRU5HVEg6IDkxDQpzdG5wLXBsdWdpbjogZW52aXNhbGluaw0KSG9zdDogMTkyLjE2OC4xLjk0OjM5NTAwDQpDb25uZWN0aW9uOiBjbG9zZQ==, body:eyJ0eXBlIjoicGFydGl0aW9uIiwicGFydGl0aW9uIjoxLCJzdGF0ZSI6InJlYWR5IiwiYWxwaGEiOiIqKioqRElTQVJNRUQqKioqICBSZWFkeSB0byBBcm0ifQ==
cd496372-3173-4cce-8849-0d1d72ca68fd ‎9‎:‎00‎:‎35‎ ‎PM: trace [Honeywell Security] lanResponseHandler: [index:06, mac:B827EB6155D9, headers:Tk9USUZZIC9ub3RpZnkgSFRUUC8xLjENCkNPTlRFTlQtVFlQRTogYXBwbGljYXRpb24vanNvbg0KQ09OVEVOVC1MRU5HVEg6IDkxDQpzdG5wLXBsdWdpbjogZW52aXNhbGluaw0KSG9zdDogMTkyLjE2OC4xLjk0OjM5NTAwDQpDb25uZWN0aW9uOiBjbG9zZQ==, body:eyJ0eXBlIjoicGFydGl0aW9uIiwicGFydGl0aW9uIjoxLCJzdGF0ZSI6InJlYWR5IiwiYWxwaGEiOiIqKioqRElTQVJNRUQqKioqICBSZWFkeSB0byBBcm0ifQ==]

And here is my node proxy log file:

pi@Raspi:~/smartthings-nodeproxy $ npm run start

smartthings-nodeproxy@1.0.0 start /home/pi/smartthings-nodeproxy
node server.js

[2018-01-03T03:00:31.114Z] [stnp] SmartThings Node Proxy listening at http://:::8080
[2018-01-03T03:00:31.142Z] [stnp] Loaded plugin: envisalink
[2018-01-03T03:00:31.148Z] [evl3] Connected to Envisalink at 192.168.1.125:4025
[2018-01-03T03:00:35.271Z] [evl3] {“type”:“partition”,“partition”:1,“state”:“ready”,“alpha”:“DISARMED Ready to Arm”}
[2018-01-03T03:00:39.163Z] [stnp] ::ffff:192.168.1.94 GET /subscribe/192.168.1.94:39500
[2018-01-03T03:00:39.311Z] [stnp] ::ffff:192.168.1.94 GET /plugins/envisalink/config/192.168.1.125:4025:user:1234:
[2018-01-03T03:00:44.751Z] [stnp] ::ffff:192.168.1.94 GET /plugins/envisalink/discover
[2018-01-03T03:00:44.760Z] [evl3] Completed panel discovery

Hopefully these formats are acceptable and this data is useful.
Any help you could provide would be greatly appreciated.

Thanks!

Keith