SmartThings Community

[RELEASE] Honeywell / Ademco Vista 20P Integration

honeywell
dth_security
smartapp_security
project_security
alarmdecoder

(Eric Mc Donald) #735

Just got STNP working on Ubuntu 17.04 with my Vista20P - Thank you!

For any Ubuntu folks - I installed Node with the following - I needed to install nodejs-legacy to get the actual “npm run start” to work (evidently installing npm doesn’t actually install the “node” binary).

sudo apt install npm
sudo apt-get install nodejs-legacy


(Patrick Nijsters) #736

Having moderate success getting the 48 zones from my Vista 20 panel to show up through the Envisalink 4 connection. Everything is talking to each other but I can’t get the full 48 zones to show up. Debug logging tells me that I’m hitting the infamous 20 seconds Java time-out issue. This now yields a result where discovery creates somewhere between 15-24 child devices but never makes it to the full 48 zones I have connected to this panel. Did anybody else hit the Java timeout exception with larger panels? If so: any way around this issue?


(ᵇᶥᵍ ШΞΒȘГẬŚ (Webstas)) #737

Has anyone tried setting this up on Centos 7?
i have it up and running manually but i cant get the service to run


(ᵇᶥᵍ ШΞΒȘГẬŚ (Webstas)) #738

Disregard, Node is located in /usr/bin not /usr/local/bin that was causing my issue


#739

Did you set the Node script path to the fully qualified location of server.js?


#740

Hey there… this means that the

"authCode": "secret-key"

in your config.json does not match the auth code you entered in the SmartApp. Make sure those are the same and keep it simple… ie. don’t use crazy characters as that could be the issue.


#741

Nope never run into this issue… but you do have a couple options:

  1. Manually add the devices/zones… just look at the format of the zones that are created and replicate… it follows a pretty simple model.

  2. Put the first 24 zones in the config.json and run discovery in the SmartApp. Once all 24 zones are discovered, edit the SmartApp to not delete the existing child zones when discovery runs. Then put the other 24 zones in the config.json and re-run discovery in the SmartApp… that should get you all 48 zones.


#742

Hmmmm everything looks good… and when you pull down the devices list on the Things tab you don’t see the new zones?? And you have the custom device handlers installed for all the device types? If that’s the case, we need to add debug to the SmartApp where the zones are supposed to get created…


(bfr31tas) #743

I’m having the same issue.
For some reason, when I start to fill the information, as soon as I choose the plugin (envisalink or ad2usb) all the settings return to some original value. The App is not saving the values, thus the authentication error…


(Kajones02) #744

That is correct, nothing from the alarm panel is showing up in the Things tab. I’ve installed all four custom device handlers. Here is the log including logging for adding and updating partitions and zones. Please let me know your thoughts because I am stumped. Thanks!

735b7280-3d37-4e27-8799-4f41106b2c0f ‎6‎:‎20‎:‎59‎ ‎PM: trace Body: [partitions:[[partition:1, name:Security Panel]], type :discover, zones:[[name:Front Door, type:contact, zone:1], [name:Living Room Motion, type:motion, zone:2], [name:Master Bedroom, type:contact, zone:3], [name:Kitchen / Back Door, type:contact, zone:4], [name:Dining, type:contact, zone:5], [name:Garage Entry, type:contact, zone:6]]]
735b7280-3d37-4e27-8799-4f41106b2c0f ‎6‎:‎20‎:‎54‎ ‎PM: trace Body: null
735b7280-3d37-4e27-8799-4f41106b2c0f ‎6‎:‎20‎:‎54‎ ‎PM: trace Headers: [HTTP/1.1 200 OK:, X-Powered-By:Express, Date:Sun, 07 Jan 2018 00, Connection:keep-alive, Content-Length:0]
735b7280-3d37-4e27-8799-4f41106b2c0f ‎6‎:‎20‎:‎54‎ ‎PM: trace SmartThings Node Proxy: index:15, mac:B827EB6155D9, ip:C0A8017B, port:1F90, requestId:34361176-a101-4593-a657-e8945b761548, headers:SFRUUC8xLjEgMjAwIE9LDQpYLVBvd2VyZWQtQnk6IEV4cHJlc3MNCkRhdGU6IFN1biwgMDcgSmFuIDIwMTggMDA6MjA6NTQgR01UDQpDb25uZWN0aW9uOiBrZWVwLWFsaXZlDQpDb250ZW50LUxlbmd0aDogMA==, body:
735b7280-3d37-4e27-8799-4f41106b2c0f ‎6‎:‎20‎:‎54‎ ‎PM: trace [Honeywell Security] lanResponseHandler: [index:15, mac:B827EB6155D9, ip:C0A8017B, port:1F90, requestId:34361176-a101-4593-a657-e8945b761548, headers:SFRUUC8xLjEgMjAwIE9LDQpYLVBvd2VyZWQtQnk6IEV4cHJlc3MNCkRhdGU6IFN1biwgMDcgSmFuIDIwMTggMDA6MjA6NTQgR01UDQpDb25uZWN0aW9uOiBrZWVwLWFsaXZlDQpDb250ZW50LUxlbmd0aDogMA==, body:null]
735b7280-3d37-4e27-8799-4f41106b2c0f ‎6‎:‎20‎:‎59‎ ‎PM: trace Body: null
735b7280-3d37-4e27-8799-4f41106b2c0f ‎6‎:‎20‎:‎59‎ ‎PM: trace Headers: [HTTP/1.1 200 OK:, X-Powered-By:Express, Date:Sun, 07 Jan 2018 00, Connection:keep-alive, Content-Length:0]
735b7280-3d37-4e27-8799-4f41106b2c0f ‎6‎:‎20‎:‎59‎ ‎PM: trace SmartThings Node Proxy: index:15, mac:B827EB6155D9, ip:C0A8017B, port:1F90, requestId:14c11ebc-80a5-4837-a88c-1b30936d44d2, headers:SFRUUC8xLjEgMjAwIE9LDQpYLVBvd2VyZWQtQnk6IEV4cHJlc3MNCkRhdGU6IFN1biwgMDcgSmFuIDIwMTggMDA6MjA6NTkgR01UDQpDb25uZWN0aW9uOiBrZWVwLWFsaXZlDQpDb250ZW50LUxlbmd0aDogMA==, body:
735b7280-3d37-4e27-8799-4f41106b2c0f ‎6‎:‎20‎:‎59‎ ‎PM: trace [Honeywell Security] lanResponseHandler: [index:15, mac:B827EB6155D9, ip:C0A8017B, port:1F90, requestId:14c11ebc-80a5-4837-a88c-1b30936d44d2, headers:SFRUUC8xLjEgMjAwIE9LDQpYLVBvd2VyZWQtQnk6IEV4cHJlc3MNCkRhdGU6IFN1biwgMDcgSmFuIDIwMTggMDA6MjA6NTkgR01UDQpDb25uZWN0aW9uOiBrZWVwLWFsaXZlDQpDb250ZW50LUxlbmd0aDogMA==, body:null]
735b7280-3d37-4e27-8799-4f41106b2c0f ‎6‎:‎20‎:‎59‎ ‎PM: trace Honeywell Security event: index:01, mac:B827EB6155D9, headers:Tk9USUZZIC9ub3RpZnkgSFRUUC8xLjENCkNPTlRFTlQtVFlQRTogYXBwbGljYXRpb24vanNvbg0KQ09OVEVOVC1MRU5HVEg6IDM5MQ0Kc3RucC1wbHVnaW46IGVudmlzYWxpbmsNCkhvc3Q6IDE5Mi4xNjguMS45NDozOTUwMA0KQ29ubmVjdGlvbjogY2xvc2U=, body:eyJ0eXBlICI6ImRpc2NvdmVyIiwicGFydGl0aW9ucyI6W3sicGFydGl0aW9uIjoxLCJuYW1lIjoiU2VjdXJpdHkgUGFuZWwifV0sInpvbmVzIjpbeyJ6b25lIjoxLCJ0eXBlIjoiY29udGFjdCIsIm5hbWUiOiJGcm9udCBEb29yIn0seyJ6b25lIjoyLCJ0eXBlIjoibW90aW9uIiwibmFtZSI6IkxpdmluZyBSb29tIE1vdGlvbiJ9LHsiem9uZSI6MywidHlwZSI6ImNvbnRhY3QiLCJuYW1lIjoiTWFzdGVyIEJlZHJvb20ifSx7InpvbmUiOjQsInR5cGUiOiJjb250YWN0IiwibmFtZSI6IktpdGNoZW4gLyBCYWNrIERvb3IifSx7InpvbmUiOjUsInR5cGUiOiJjb250YWN0IiwibmFtZSI6IkRpbmluZyJ9LHsiem9uZSI6NiwidHlwZSI6ImNvbnRhY3QiLCJuYW1lIjoiR2FyYWdlIEVudHJ5In1dfQ==
735b7280-3d37-4e27-8799-4f41106b2c0f ‎6‎:‎20‎:‎54‎ ‎PM: trace Honeywell Security send command: /plugins/envisalink/config/192.168.1.50:4025:user:1234
735b7280-3d37-4e27-8799-4f41106b2c0f ‎6‎:‎20‎:‎54‎ ‎PM: trace Honeywell Security send command: /subscribe/192.168.1.94:39500
735b7280-3d37-4e27-8799-4f41106b2c0f ‎6‎:‎20‎:‎54‎ ‎PM: debug getChildDevices(true), children=0
735b7280-3d37-4e27-8799-4f41106b2c0f ‎6‎:‎20‎:‎59‎ ‎PM: trace Honeywell Security send command: /plugins/envisalink/discover
735b7280-3d37-4e27-8799-4f41106b2c0f ‎6‎:‎20‎:‎59‎ ‎PM: trace [Honeywell Security] lanResponseHandler: [index:01, mac:B827EB6155D9, headers:Tk9USUZZIC9ub3RpZnkgSFRUUC8xLjENCkNPTlRFTlQtVFlQRTogYXBwbGljYXRpb24vanNvbg0KQ09OVEVOVC1MRU5HVEg6IDM5MQ0Kc3RucC1wbHVnaW46IGVudmlzYWxpbmsNCkhvc3Q6IDE5Mi4xNjguMS45NDozOTUwMA0KQ29ubmVjdGlvbjogY2xvc2U=, body:eyJ0eXBlICI6ImRpc2NvdmVyIiwicGFydGl0aW9ucyI6W3sicGFydGl0aW9uIjoxLCJuYW1lIjoiU2VjdXJpdHkgUGFuZWwifV0sInpvbmVzIjpbeyJ6b25lIjoxLCJ0eXBlIjoiY29udGFjdCIsIm5hbWUiOiJGcm9udCBEb29yIn0seyJ6b25lIjoyLCJ0eXBlIjoibW90aW9uIiwibmFtZSI6IkxpdmluZyBSb29tIE1vdGlvbiJ9LHsiem9uZSI6MywidHlwZSI6ImNvbnRhY3QiLCJuYW1lIjoiTWFzdGVyIEJlZHJvb20ifSx7InpvbmUiOjQsInR5cGUiOiJjb250YWN0IiwibmFtZSI6IktpdGNoZW4gLyBCYWNrIERvb3IifSx7InpvbmUiOjUsInR5cGUiOiJjb250YWN0IiwibmFtZSI6IkRpbmluZyJ9LHsiem9uZSI6NiwidHlwZSI6ImNvbnRhY3QiLCJuYW1lIjoiR2FyYWdlIEVudHJ5In1dfQ==]
‎6‎:‎21‎:‎19‎ ‎PM: info Waiting on events.


#745

That’s weird… iOS or Android?? Anyone else having this issue??

For kicks just set the

"authCode": "secret-key"

in config.json and see if it works (secret-key is the default value).


#746

This is weird… it’s making it all the way to line 132 in the SmartApp and supposedly calling processEvent()… let’s add some more debug and re-run the test to figure this out.

Replace line 162 to line 192 with this:

private processEvent(evt) {
  log.debug "Honeywell Security processEvent: ${evt.stringValue}"
  if (evt.type == "discover") {
    log.debug "Honeywell Security processEvent with type=discover"
    addChildDevices(evt.partitions, evt.zones)
  }
  if (evt.type == "zone") {
    updateZoneDevices(evt.zone, evt.state)
  }
  if (evt.type == "partition") {
    updatePartitions(evt.partition, evt.state, evt.alpha)
    updateAlarmSystemStatus(evt.state)
  }
}

private addChildDevices(partitions, zones) {
  log.debug "Honeywell Security addChildDevices with partitions=${partitions.stringValue}"
  partitions.each {
    def deviceId = 'honeywell|partition'+it.partition
    if (!getChildDevice(deviceId)) {
      addChildDevice("redloro-smartthings", "Honeywell Partition", deviceId, hostHub.id, ["name": "Honeywell Security", label: "Honeywell Security", completedSetup: true])
      log.debug "Honeywell Security added partition device: ${deviceId}"
    } else {
      log.debug "Honeywell Security partition device not added: ${deviceId}"
    }
  }

  log.debug "Honeywell Security addChildDevices with zones=${zones.stringValue}"
  zones.each {
    def deviceId = 'honeywell|zone'+it.zone
    if (!getChildDevice(deviceId)) {
      it.type = it.type.capitalize()
      addChildDevice("redloro-smartthings", "Honeywell Zone "+it.type, deviceId, hostHub.id, ["name": it.name, label: it.name, completedSetup: true])
      log.debug "Honeywell Security added zone device: ${deviceId}"
    } else {
      log.debug "Honeywell Security zone device not added: ${deviceId}"
    }
  }
}

(Kajones02) #747

Thanks for all of the help redloro. Here are the logs after running the amended code.

834a7f89-fc99-481d-b8f7-2f911389e6f8 ‎7‎:‎59‎:‎56‎ ‎AM: trace Body: [partitions:[[partition:1, name:Security Panel]], type :discover, zones:[[name:Front Door, type:contact, zone:1], [name:Living Room Motion, type:motion, zone:2], [name:Master Bedroom, type:contact, zone:3], [name:Kitchen / Back Door, type:contact, zone:4], [name:Dining, type:contact, zone:5], [name:Garage Entry, type:contact, zone:6]]]
834a7f89-fc99-481d-b8f7-2f911389e6f8 ‎7‎:‎59‎:‎56‎ ‎AM: trace SmartThings Node Proxy: index:05, mac:B827EB6155D9, headers:Tk9USUZZIC9ub3RpZnkgSFRUUC8xLjENCkNPTlRFTlQtVFlQRTogYXBwbGljYXRpb24vanNvbg0KQ09OVEVOVC1MRU5HVEg6IDM5MQ0Kc3RucC1wbHVnaW46IGVudmlzYWxpbmsNCkhvc3Q6IDE5Mi4xNjguMS45NDozOTUwMA0KQ29ubmVjdGlvbjogY2xvc2U=, body:eyJ0eXBlICI6ImRpc2NvdmVyIiwicGFydGl0aW9ucyI6W3sicGFydGl0aW9uIjoxLCJuYW1lIjoiU2VjdXJpdHkgUGFuZWwifV0sInpvbmVzIjpbeyJ6b25lIjoxLCJ0eXBlIjoiY29udGFjdCIsIm5hbWUiOiJGcm9udCBEb29yIn0seyJ6b25lIjoyLCJ0eXBlIjoibW90aW9uIiwibmFtZSI6IkxpdmluZyBSb29tIE1vdGlvbiJ9LHsiem9uZSI6MywidHlwZSI6ImNvbnRhY3QiLCJuYW1lIjoiTWFzdGVyIEJlZHJvb20ifSx7InpvbmUiOjQsInR5cGUiOiJjb250YWN0IiwibmFtZSI6IktpdGNoZW4gLyBCYWNrIERvb3IifSx7InpvbmUiOjUsInR5cGUiOiJjb250YWN0IiwibmFtZSI6IkRpbmluZyJ9LHsiem9uZSI6NiwidHlwZSI6ImNvbnRhY3QiLCJuYW1lIjoiR2FyYWdlIEVudHJ5In1dfQ==
834a7f89-fc99-481d-b8f7-2f911389e6f8 ‎7‎:‎59‎:‎56‎ ‎AM: trace Body: null
834a7f89-fc99-481d-b8f7-2f911389e6f8 ‎7‎:‎59‎:‎56‎ ‎AM: trace Headers: [HTTP/1.1 200 OK:, X-Powered-By:Express, Date:Sun, 07 Jan 2018 13, Connection:keep-alive, Content-Length:0]
834a7f89-fc99-481d-b8f7-2f911389e6f8 ‎7‎:‎59‎:‎56‎ ‎AM: trace SmartThings Node Proxy: index:15, mac:B827EB6155D9, ip:C0A8017B, port:1F90, requestId:e1ebb2aa-2571-46cc-9a24-3f1e9ec4a838, headers:SFRUUC8xLjEgMjAwIE9LDQpYLVBvd2VyZWQtQnk6IEV4cHJlc3MNCkRhdGU6IFN1biwgMDcgSmFuIDIwMTggMTM6NTk6NTYgR01UDQpDb25uZWN0aW9uOiBrZWVwLWFsaXZlDQpDb250ZW50LUxlbmd0aDogMA==, body:
834a7f89-fc99-481d-b8f7-2f911389e6f8 ‎7‎:‎59‎:‎56‎ ‎AM: trace [Honeywell Security] lanResponseHandler: [index:15, mac:B827EB6155D9, ip:C0A8017B, port:1F90, requestId:e1ebb2aa-2571-46cc-9a24-3f1e9ec4a838, headers:SFRUUC8xLjEgMjAwIE9LDQpYLVBvd2VyZWQtQnk6IEV4cHJlc3MNCkRhdGU6IFN1biwgMDcgSmFuIDIwMTggMTM6NTk6NTYgR01UDQpDb25uZWN0aW9uOiBrZWVwLWFsaXZlDQpDb250ZW50LUxlbmd0aDogMA==, body:null]
834a7f89-fc99-481d-b8f7-2f911389e6f8 ‎7‎:‎59‎:‎56‎ ‎AM: trace Honeywell Security send command: /plugins/envisalink/discover
834a7f89-fc99-481d-b8f7-2f911389e6f8 ‎7‎:‎59‎:‎52‎ ‎AM: trace Body: null
834a7f89-fc99-481d-b8f7-2f911389e6f8 ‎7‎:‎59‎:‎52‎ ‎AM: trace Headers: [HTTP/1.1 200 OK:, X-Powered-By:Express, Date:Sun, 07 Jan 2018 13, Connection:keep-alive, Content-Length:0]
834a7f89-fc99-481d-b8f7-2f911389e6f8 ‎7‎:‎59‎:‎52‎ ‎AM: trace SmartThings Node Proxy: index:16, mac:B827EB6155D9, ip:C0A8017B, port:1F90, requestId:34d77885-ceed-4c7d-b0ef-fde21d71458a, headers:SFRUUC8xLjEgMjAwIE9LDQpYLVBvd2VyZWQtQnk6IEV4cHJlc3MNCkRhdGU6IFN1biwgMDcgSmFuIDIwMTggMTM6NTk6NTEgR01UDQpDb25uZWN0aW9uOiBrZWVwLWFsaXZlDQpDb250ZW50LUxlbmd0aDogMA==, body:
834a7f89-fc99-481d-b8f7-2f911389e6f8 ‎7‎:‎59‎:‎52‎ ‎AM: trace [Honeywell Security] lanResponseHandler: [index:16, mac:B827EB6155D9, ip:C0A8017B, port:1F90, requestId:34d77885-ceed-4c7d-b0ef-fde21d71458a, headers:SFRUUC8xLjEgMjAwIE9LDQpYLVBvd2VyZWQtQnk6IEV4cHJlc3MNCkRhdGU6IFN1biwgMDcgSmFuIDIwMTggMTM6NTk6NTEgR01UDQpDb25uZWN0aW9uOiBrZWVwLWFsaXZlDQpDb250ZW50LUxlbmd0aDogMA==, body:null]
834a7f89-fc99-481d-b8f7-2f911389e6f8 ‎7‎:‎59‎:‎51‎ ‎AM: trace Body: null
834a7f89-fc99-481d-b8f7-2f911389e6f8 ‎7‎:‎59‎:‎51‎ ‎AM: trace Headers: [HTTP/1.1 200 OK:, X-Powered-By:Express, Date:Sun, 07 Jan 2018 13, Connection:keep-alive, Content-Length:0]
834a7f89-fc99-481d-b8f7-2f911389e6f8 ‎7‎:‎59‎:‎51‎ ‎AM: trace SmartThings Node Proxy: index:15, mac:B827EB6155D9, ip:C0A8017B, port:1F90, requestId:ae409319-7cbc-442f-8aee-9be247fa8d34, headers:SFRUUC8xLjEgMjAwIE9LDQpYLVBvd2VyZWQtQnk6IEV4cHJlc3MNCkRhdGU6IFN1biwgMDcgSmFuIDIwMTggMTM6NTk6NTEgR01UDQpDb25uZWN0aW9uOiBrZWVwLWFsaXZlDQpDb250ZW50LUxlbmd0aDogMA==, body:
834a7f89-fc99-481d-b8f7-2f911389e6f8 ‎7‎:‎59‎:‎51‎ ‎AM: trace [Honeywell Security] lanResponseHandler: [index:15, mac:B827EB6155D9, ip:C0A8017B, port:1F90, requestId:ae409319-7cbc-442f-8aee-9be247fa8d34, headers:SFRUUC8xLjEgMjAwIE9LDQpYLVBvd2VyZWQtQnk6IEV4cHJlc3MNCkRhdGU6IFN1biwgMDcgSmFuIDIwMTggMTM6NTk6NTEgR01UDQpDb25uZWN0aW9uOiBrZWVwLWFsaXZlDQpDb250ZW50LUxlbmd0aDogMA==, body:null]
834a7f89-fc99-481d-b8f7-2f911389e6f8 ‎7‎:‎59‎:‎51‎ ‎AM: trace Honeywell Security send command: /plugins/envisalink/config/192.168.1.50:4025:user:1234
834a7f89-fc99-481d-b8f7-2f911389e6f8 ‎7‎:‎59‎:‎51‎ ‎AM: trace Honeywell Security send command: /subscribe/192.168.1.94:39500
834a7f89-fc99-481d-b8f7-2f911389e6f8 ‎7‎:‎59‎:‎51‎ ‎AM: debug getChildDevices(true), children=0


(bfr31tas) #748

I’m on iOS. I dont know if this can point you in the right direction, but if I change the input type of the sensitive information (eg “security code”) from “password” to “text”, it works normally…
Thanks in advance for the help.


(OGM) #749

Hi again Redloro,

So here are my findings and the solution:

In contrast to the rest of the sensors, Type 12 sensors do not create zone events, but instead partition events, mainly in form of alpha notifications (example log below)

[2018-01-15T02:06:08.853Z] [evl3] {“type”:“partition”,“partition”:1,“state”:“notready”,“alpha”:“CHECK 09 DRIVEWAY DOOR”}

Since the zones themselves are never reported as zone events, they are never updated in the SmartApp. I thought a possible solution as parsing the partition events for “CHECK” keyword, and then calling the update zone function with the zone reported in there.

The complication is, since this is an alpha report, there is no specific “cleared” notification. If this is the only notification in the alpha keypad, then it goes in ready mode, or if there are other notifications (cycling every 4 seconds), the “check” note disappears from the list. So the “cleared” logic there can be time based and/or waiting for “system ready”.

Looking at envisalink forums for this behavior, I found another solution, which is to convert all the monitor zones into regular zones (e.g. 03 periphery) and move them to partition 2 which is never armed. This way they are reported as regular zones, but never trigger an alarm on Vista 20p.

In the path of least resistance, I went with moving them to a new partition, which seemed to accomplish the intended task. BUT, it seems there is a strange behavior with 2 partitions, when I arm partition 1 but not 2, there is a 70% chance that partition 1 disarms itself in less than 30 mins. To be honest, I could not find a reason why (the logs just indicate that a disarm request was received), but I removed the master password from the SmartApp and the behavior stopped. This is fine by me, as I prefer SmartThings to not have arming/disaming access anyways…

Thanks again for the s/w! It is much appreciated.


(Tom Quinn) #750

All,
worked with a buddy of mine and got this all setup, it works pretty slick!

I’m curious though, I have multiple partitions, and am struggling with status updates, a door reports open, then seconds later closed (while still open) and oscillates back and forth. I’ve found this is because something is not properly identifying the zone to partition mapping, which I haven’t figured out how to do.

Is there a magic command in the config file to identify what partition a zone belongs to, so it would ignore notifications of a zone with an incorrect partition?

Here’s some logs, you can see zone 1 and 11 are marked “open” in partition 1, then “closed” in partition 3, causing the smart things state to waffle…

Jan 15 19:04:36 rsbpialarmserver nodejs[392]: [2018-01-16T02:04:36.479Z] [evl3] {“type”:“zone”,“partition”:1,“zone”:1,“state”:“open”}
Jan 15 19:04:38 rsbpialarmserver nodejs[392]: [2018-01-16T02:04:38.482Z] [evl3] {“type”:“zone”,“partition”:1,“zone”:11,“state”:“open”}
Jan 15 19:04:39 rsbpialarmserver nodejs[392]: [2018-01-16T02:04:39.484Z] [evl3] {“type”:“zone”,“partition”:3,“zone”:“1”,“state”:“closed”}
Jan 15 19:04:39 rsbpialarmserver nodejs[392]: [2018-01-16T02:04:39.485Z] [evl3] {“type”:“zone”,“partition”:3,“zone”:“11”,“state”:“closed”}
Jan 15 19:11:17 rsbpialarmserver nodejs[392]: [2018-01-16T02:11:17.639Z] [evl3] {“type”:“zone”,“partition”:1,“zone”:11,“state”:“open”}
Jan 15 19:11:19 rsbpialarmserver nodejs[392]: [2018-01-16T02:11:19.141Z] [evl3] {“type”:“zone”,“partition”:3,“zone”:“11”,“state”:“closed”}
Jan 15 19:11:19 rsbpialarmserver nodejs[392]: [2018-01-16T02:11:19.642Z] [evl3] {“type”:“zone”,“partition”:1,“zone”:1,“state”:“open”}
Jan 15 19:11:23 rsbpialarmserver nodejs[392]: [2018-01-16T02:11:23.148Z] [evl3] {“type”:“zone”,“partition”:3,“zone”:“1”,“state”:“closed”}
Jan 15 19:11:27 rsbpialarmserver nodejs[392]: [2018-01-16T02:11:27.156Z] [evl3] {“type”:“zone”,“partition”:1,“zone”:1,“state”:“open”}
Jan 15 19:11:28 rsbpialarmserver nodejs[392]: [2018-01-16T02:11:28.656Z] [evl3] {“type”:“zone”,“partition”:1,“zone”:“1”,“state”:“closed”}
Jan 16 09:23:27 rsbpialarmserver nodejs[392]: [2018-01-16T16:23:27.669Z] [evl3] {“type”:“zone”,“partition”:1,“zone”:1,“state”:“open”}
Jan 16 09:23:28 rsbpialarmserver nodejs[392]: [2018-01-16T16:23:28.169Z] [evl3] {“type”:“zone”,“partition”:3,“zone”:“1”,“state”:“closed”}
Jan 16 09:23:29 rsbpialarmserver nodejs[392]: [2018-01-16T16:23:29.171Z] [evl3] {“type”:“zone”,“partition”:1,“zone”:11,“state”:“open”}
Jan 16 09:23:31 rsbpialarmserver nodejs[392]: [2018-01-16T16:23:31.675Z] [evl3] {“type”:“zone”,“partition”:3,“zone”:“11”,“state”:“closed”}
Jan 16 09:26:20 rsbpialarmserver nodejs[392]: [2018-01-16T16:26:20.932Z] [evl3] {“type”:“zone”,“partition”:1,“zone”:11,“state”:“open”}
Jan 16 09:26:21 rsbpialarmserver nodejs[392]: [2018-01-16T16:26:21.933Z] [evl3] {“type”:“zone”,“partition”:1,“zone”:“11”,“state”:“closed”}
Jan 16 09:26:28 rsbpialarmserver nodejs[392]: [2018-01-16T16:26:28.443Z] [evl3] {“type”:“zone”,“partition”:1,“zone”:1,“state”:“open”}
Jan 16 09:26:29 rsbpialarmserver nodejs[392]: [2018-01-16T16:26:29.945Z] [evl3] {“type”:“zone”,“partition”:3,“zone”:“1”,“state”:“closed”}


#751

Shiny and new at this! I’ve come over from Vera. I have a Vista 15P, an EVL3, and I’m using a spare PC as my Node Proxy. I’m inexperienced enough at this that I only now know what Node Proxy is!

I’m working my way through your installation. I’ve gotten as far as “typing: npm run start” when I hit a wall.
So, here’s my config.json:

{
“port”: 8080,
“authCode”: “secret-key”,
“envisalink”: {
“address”: “192.168.1.254”,
“port”: “4025”,
“password”: “user”,
“securityCode”: “1234”,
“dumpZoneTimer”: “5”,
“panelConfig”: {
“type”: “discover”,
“partitions”: [
{
“partition”: 1,
“name”: “Security Panel”
}
],
“zones”: [
{
“zone”: 1,
“type”: “smoke”,
“name”: “Smoke Detector”
},
{
“zone”: 2,
“type”: “contact”,
“name”: “Front Door”
},
{
“zone”: 3,
“type”: “contact”,
“name”: “Back Door”
},
{
“zone”: 4,
“type”: “contact”,
“name”: “Kitchen Door”
},
{
“zone”: 5,
“type”: “contact”,
“name”: “Kitchen Window”
}
]
}
},
“notify”: {
“address”: “192.168.1.202”,
“port”: “39500”
}
}

SO - I followed your instructions, typed: npm run start, and got this:

c:\home\smartthings-nodeproxy\plugins>npm run start

smartthings-nodeproxy@1.0.0 start c:\home\smartthings-nodeproxy
node server.js

[2018-01-19T15:55:16.545Z] [stnp] SmartThings Node Proxy listening at http://:::8080
module.js:540
throw err;
^

Error: Cannot find module 'serialport’
at Function.Module._resolveFilename (module.js:538:15)
at Function.Module._load (module.js:468:25)
at Module.require (module.js:587:17)
at require (internal/module.js:11:18)
at Object. (c:\home\smartthings-nodeproxy\plugins\ad2usb.js:21:18)
at Module._compile (module.js:643:30)
at Object.Module._extensions…js (module.js:654:10)
at Module.load (module.js:556:32)
at tryModuleLoad (module.js:499:12)
at Function.Module._load (module.js:491:3)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! smartthings-nodeproxy@1.0.0 start: node server.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the smartthings-nodeproxy@1.0.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\witha\AppData\Roaming\npm-cache_logs\2018-01-19T15_55_16_561Z-debug.log

c:\home\smartthings-nodeproxy\plugins>

Help please? Also, that “secret-key” in config.json… Will I be changing that in a future step? I DO have the proper security code, just changed to 1234 for viewing.


(Eric Vasilisin) #753

Can’t seem to get all zones to show. Have 10 out of 64. Can anyone help?


#754

Just a note - I deleted everything in the created directories and started over, this time leaving everything in the config.json file (except the “//” stuff) and it seems to have worked.


#755

Well I got to the end! Go me! :slight_smile: Did everything the Installation said. I’m here:

“Done! Note that all the zones defined in config.json will be loaded 10 seconds after the SmartApp is configured and all the devices should show up under your Things. If the zones/devices do not show up, simply open the SmartApp again and hit done to force a refresh of the zones/devices.”

Nope. I got nothin’! :slight_smile: Help?