SmartThings Community

[RELEASE] Honeywell / Ademco Vista 20P Integration

honeywell
dth_security
smartapp_security
project_security
alarmdecoder

(Alwineinger) #840

Successfully up and running with a 21iP, an Envisilink 4, and a Synology NAS (node js 0.10 – my NAS doesn’t support the newer versions of Node).

Took me forever to figure out how to autostart STNP when the Synology boots. In the Synology Control Panel>Task Scheduler, create an event-based user script. Needs to run as root. Script should look like:

#! /bin/sh
cd /volume1/Server/Node/smartthings-nodeproxy
forever start server.js

where ‘/volume1/Server/Node/smartthings-nodeproxy’ is your file path to wherever you installed STNP


#841

Hi @redloro, this is working worderfully in my setup, any plans to add new addons, Yeelight WiFi bulbs will be a great addition! Maybe in collaboration with https://github.com/davidcreager/smartthings-smartbulbs


(Dave) #844

Hi @redloro! I’m new to SmartThings and specifically got a EVL-4 to work with my old Honeywell Vista 15P. This integration definitely stood out as one of the first few plugins that I wanted to add on! Sadly, I’m running into issues.

Below is what I’m seeing:

  • I was able to install STNP on my QNAP container, and I can see that it’s communicating with my EVL4 correctly as it’s getting messages on status, etc.
  • I also was able to install the SmartApp and configured it to connect to my EVL4 and STNP
  • I can see in the STNP log that the SmartApp is communicating to it and triggering a discovery
  • The part that isn’t working for me is that I can’t seem to see any Things for the various sensors and zones under My Home in the phone app. I read through previous posts, and am not sure where I’m going wrong. It seems like I can’t find any children since I’m seeing “getChildDevices(true), children=0”
  • The odd part is that I can trigger Arming of the panel through SHM fine, it’s literally just not seeing any of the devices in Things.

So read through all the posts and really got no idea why nothing is showing up in Things. It seems like some folks have had this issue in the past but it wasn’t clear what the resolution was or the ones mentioned didn’t work for me. Tried restarting my ST Hub and EVL-4 and STNP server, and nothing has made a difference. Any help would be really appreciated as I’m completely stuck here…

Here’s my config.json with some information sensored:

{
“port”: 8880,
“authCode”: “********”,
“envisalink”: {
“address”: “10.0.0.9”,
“port”: “4025”,
“password”: “user”,
“securityCode”: “****”,
“panelConfig”: {
“type”: “discover”,
“partitions”: [
{
“partition”: 1,
“name”: “Security Panel”
}
],
“zones”: [
{
“zone”: 1,
“type”: “contact”,
“name”: “Front and Garage Doors”
},
{
“zone”: 3,
“type”: “contact”,
“name”: “Back Door”
},
{
“zone”: 5,
“type”: “contact”,
“name”: “Windows”
}
]
}
},
“notify”: {
“address”: “10.0.0.23”,
“port”: “39500”
}
}

Here’s a snippet from STNP server:
> smartthings-nodeproxy@1.0.0 start /smartthings-nodeproxy
> node server.js

[2018-03-08T03:50:50.301Z] [stnp] SmartThings Node Proxy listening at http://0.0.0.0:8880                                                                                                                               
[2018-03-08T03:50:50.322Z] [stnp] Loaded plugin: envisalink                                                                                                                                                             
[2018-03-08T03:50:50.327Z] [evl3] Connected to Envisalink at 10.0.0.9:4025                                                                                                                                              
[2018-03-08T03:50:52.085Z] [evl3] {"type":"partition","partition":1,"state":"ready","alpha":"SYSTEM LO BAT"}                                                                                                            
[2018-03-08T03:50:56.044Z] [evl3] {"type":"partition","partition":1,"state":"ready","alpha":"DISARMED CHIME   Ready to Arm"}                                                                                            
[2018-03-08T03:50:56.424Z] [stnp] 10.0.0.23 GET /plugins/envisalink/config/10.0.0.9:4025:user:****                                                                                                                      
[2018-03-08T03:50:56.555Z] [stnp] 10.0.0.23 GET /subscribe/10.0.0.23:39500                                                                                                                                              
[2018-03-08T03:51:00.008Z] [evl3] {"type":"partition","partition":1,"state":"ready","alpha":"SYSTEM LO BAT"}                                                                                                            
[2018-03-08T03:51:01.623Z] [stnp] 10.0.0.23 GET /plugins/envisalink/discover                                                                                                                                            
[2018-03-08T03:51:01.626Z] [evl3] Completed panel discovery                                                                                                                                                             
[2018-03-08T03:51:03.993Z] [evl3] {"type":"partition","partition":1,"state":"ready","alpha":"DISARMED CHIME   Ready to Arm"}                                                                                            
[2018-03-08T03:51:06.828Z] [evl3] {"type":"zone","partition":1,"zone":1,"state":"open"}                                                                                                                                 
[2018-03-08T03:51:06.829Z] [evl3] {"type":"partition","partition":1,"state":"notready","alpha":"FAULT 01"}                                                                                                              
[2018-03-08T03:51:10.671Z] [evl3] {"type":"partition","partition":1,"state":"notready","alpha":"SYSTEM LO BAT"}                                                                                                         
[2018-03-08T03:51:12.873Z] [evl3] {"type":"zone","partition":1,"zone":"1","state":"closed"}                                                                                                                             
[2018-03-08T03:51:12.873Z] [evl3] {"type":"partition","partition":1,"state":"ready","alpha":"DISARMED CHIME   Ready to Arm"}                                                                                            
[2018-03-08T03:51:16.832Z] [evl3] {"type":"partition","partition":1,"state":"ready","alpha":"SYSTEM LO BAT"}  

And here’s the ST Live Log:

37fcd5aa-eca7-4aef-bf29-b5a2e30131c7 9:51:02 PM: trace Body: null
37fcd5aa-eca7-4aef-bf29-b5a2e30131c7 9:51:02 PM: trace Headers: [HTTP/1.1 200 OK:, X-Powered-By:Express, Date:Thu, 08 Mar 2018 03, Connection:keep-alive, Content-Length:0]
37fcd5aa-eca7-4aef-bf29-b5a2e30131c7 9:51:02 PM: trace SmartThings Node Proxy: index:15, mac:00089BEA78D1, ip:0A000008, port:22B0, requestId:ddaf3ade-ae05-43da-ab3e-f4e5fec618b4, headers:SFRUUC8xLjEgMjAwIE9LDQpYLVBvd2VyZWQtQnk6IEV4cHJlc3MNCkRhdGU6IFRodSwgMDggTWFyIDIwMTggMDM6NTE6MDEgR01UDQpDb25uZWN0aW9uOiBrZWVwLWFsaXZlDQpDb250ZW50LUxlbmd0aDogMA==, body:
37fcd5aa-eca7-4aef-bf29-b5a2e30131c7 9:51:02 PM: trace Honeywell Security send command: /plugins/envisalink/discover
37fcd5aa-eca7-4aef-bf29-b5a2e30131c7 9:50:57 PM: trace Body: null
37fcd5aa-eca7-4aef-bf29-b5a2e30131c7 9:50:57 PM: trace Headers: [HTTP/1.1 200 OK:, X-Powered-By:Express, Date:Thu, 08 Mar 2018 03, Connection:keep-alive, Content-Length:0]
37fcd5aa-eca7-4aef-bf29-b5a2e30131c7 9:50:57 PM: trace SmartThings Node Proxy: index:16, mac:00089BEA78D1, ip:0A000008, port:22B0, requestId:8e70e400-ca31-4ad3-9665-a7052f0fdb0c, headers:SFRUUC8xLjEgMjAwIE9LDQpYLVBvd2VyZWQtQnk6IEV4cHJlc3MNCkRhdGU6IFRodSwgMDggTWFyIDIwMTggMDM6NTA6NTYgR01UDQpDb25uZWN0aW9uOiBrZWVwLWFsaXZlDQpDb250ZW50LUxlbmd0aDogMA==, body:
37fcd5aa-eca7-4aef-bf29-b5a2e30131c7 9:50:57 PM: trace Body: null
37fcd5aa-eca7-4aef-bf29-b5a2e30131c7 9:50:57 PM: trace Headers: [HTTP/1.1 200 OK:, X-Powered-By:Express, Date:Thu, 08 Mar 2018 03, Connection:keep-alive, Content-Length:0]
37fcd5aa-eca7-4aef-bf29-b5a2e30131c7 9:50:57 PM: trace SmartThings Node Proxy: index:15, mac:00089BEA78D1, ip:0A000008, port:22B0, requestId:12cf3cbc-df69-4885-a4ae-2ee716030748, headers:SFRUUC8xLjEgMjAwIE9LDQpYLVBvd2VyZWQtQnk6IEV4cHJlc3MNCkRhdGU6IFRodSwgMDggTWFyIDIwMTggMDM6NTA6NTYgR01UDQpDb25uZWN0aW9uOiBrZWVwLWFsaXZlDQpDb250ZW50LUxlbmd0aDogMA==, body:
37fcd5aa-eca7-4aef-bf29-b5a2e30131c7 9:50:57 PM: trace Honeywell Security send command: /plugins/envisalink/config/10.0.0.9:4025:user:****
37fcd5aa-eca7-4aef-bf29-b5a2e30131c7 9:50:57 PM: trace Honeywell Security send command: /subscribe/10.0.0.23:39500
37fcd5aa-eca7-4aef-bf29-b5a2e30131c7 9:50:57 PM: debug getChildDevices(true), children=0

And here’s screen shots of the SmartApp:



(jason) #845

I am at a loss. I believe I went through all the appropriate steps but it is not working. I have EVL4 setup and I can access my security system via their website. I have raspberry pi3 set up with node v6.13.1 and npm v3.10.10. In my /home/pi directory, i have config.json, package.json, and server.js. I also have a node_modules folder and a plugins folder with envisalink.js located inside.

In my config.json file, I changed the envisalink IP address and password and my alarm panel code lines in the envisalink section. I also added all my zones and the code seems to be formatted correctly when checked online. At the bottom, I changed the IP address for my smartthings hub in the notify section.

At the very top, I may be confused with what goes in the smartthings node proxy section. I left the port at 8080 and changed the secret-key to my password for smartthings. Is that correct, or what is my auth code to access STNP?

When I run node server.js, it says listening at 8080. Loaded plugin envisalink. Connected to envisalink. Then it says connection error undefined and envisalink connection closed. This just repeats forever.


(Cryptic) #846

I feel something has changed. I had a working install. With all the devices added into Smarthings with status updates. Then I stopped getting zone updates. The node proxy shows all the updates and the log shows that Smarthings is subscribed. Then a few weeks ago. No updates in the app. Removed all devices and tried to readd them. No devices readded.


(Cryptic) #847

AuthCode is just a random simple password. It is for the SmartThings app to communicate with the Node Proxy.

Use your browser to open the IP address of the Envisalink to make sure you can connect via the web. I believe the default password and username is simply ‘user’.


(jason) #848

Ok, so i have made some progress. I am not exactly sure what went wrong before, but i went through double checking everything and making some changes to passwords, etc.

So, when I put my envisalink IP in a browser, i get my security panel via webpage. When i put my STNP IP address in a browser, i get {“status”:“SmartThings Node Proxy running”}. I added the honeywell smartapp and device handlers and got all my things to show up in the smartthings app. (I was having some issues for whatever reason with it not showing up, but now randomly got it).

The problem I am having is that I can not control my security panel with the buttons in the smartthings app. when I click to arm system, it shows this in my pi3 command prompt:
pi@Pi3:~ $ node server.js
[2018-03-11T14:02:41.379Z] [stnp] SmartThings Node Proxy listening at http://:::8080
[2018-03-11T14:02:41.429Z] [stnp] Loaded plugin: envisalink
[2018-03-11T14:02:41.445Z] [evl3] Connected to Envisalink at 192.168.1.151:8080
[2018-03-11T14:03:17.346Z] [stnp] ::ffff:192.168.1.160 GET /plugins/envisalink/armAway
[2018-03-11T14:03:17.398Z] [evl3] Error: ignoring invalid message code from Envisalink: HTTP/1.1 404 Not Found, data: HTTP/1.1 404 Not Found
[2018-03-11T14:03:17.399Z] [evl3] Error: ignoring invalid message code from Envisalink: Connection: close, data: Connection: close
[2018-03-11T14:03:17.399Z] [evl3] Error: ignoring invalid message code from Envisalink: Content-Type: text/html, data: Content-Type: text/html
[2018-03-11T14:03:17.400Z] [evl3] Error: ignoring invalid message code from Envisalink:

File not Found

, data:

File not Found


[2018-03-11T14:03:17.416Z] [evl3] Envisalink connection closed.
[2018-03-11T14:03:21.433Z] [evl3] Connected to Envisalink at 192.168.1.151:8080
[2018-03-11T14:04:06.486Z] [evl3] Envisalink connection error: undefined
[2018-03-11T14:04:06.488Z] [evl3] Envisalink connection closed.
[2018-03-11T14:04:10.503Z] [evl3] Connected to Envisalink at 192.168.1.151:8080

I also just tried redoing the honeywell smartapp and rediscovering my devices. I am getting some other error in my pi3 command prompt about favicon.ico and authentication error:
pi@Pi3:~ $ node server.js
[2018-03-11T14:07:40.510Z] [stnp] ::ffff:192.168.1.160 GET /plugins/envisalink/discover
[2018-03-11T14:07:40.560Z] [evl3] Completed panel discovery
[2018-03-11T14:07:47.120Z] [stnp] ::ffff:192.168.1.253 GET /favicon.ico
[2018-03-11T14:07:47.121Z] [stnp] Authentication error
[2018-03-11T14:08:11.482Z] [evl3] Envisalink connection error: undefined
[2018-03-11T14:08:11.487Z] [evl3] Envisalink connection closed.
[2018-03-11T14:08:15.500Z] [evl3] Connected to Envisalink at 192.168.1.151:8080

I am also still getting the same previous error when trying to arm or do anything with my panel in the smartthings app.


(Cryptic) #849

The envisalink port should be 4025.


(jason) #850

4025 doesnt work when i test on a browser. 8080 gets me in from the browser.


(Cryptic) #851

Two different ports are used. One is for the web interface. The other one the proxy connects to directly. The proxy does not connect to the web interface of the envisalink.


(jason) #852

Ah. That seems to work now. Thank you very much for your help!


(Cryptic) #853

So. My issue was I was running MQTT bridge on a different port. When the node proxy reported the zones to ST; ST thought it was an incoming message from the Bridge. Disabled the bridge and the zones now get passed on.

One other person stated they had issues with more then one lan service running.


(Dave) #854

I’m still stuck here … anyone able to help? The only other things that I’m running are my Insteon lights device handler, Lock Manager smartapp, and Core smartapp. I don’t think any of those should be conflicting with this.


(jason) #855

well I thought I was good, and it is for the most part, but it seems as though none of my devices are activating when the alarm is set. If my alarm is disarmed, then all the contacts and motion sensors open and close correctly as I test them. However, when I set the alarm to away or stay, then none of my motion sensors or contact show open when I open a door or walk in front of a motion sensor.


(James Stewart) #856

I am trying to figure out if this is working properly for me. If I launch via terminal, it all works…Arm, Disarm, Notifications, etc. However if I close the terminal window, it no longer responds. Is this correct?


(jason) #857

I believe that is correct. The terminal window running server.js needs to always be running.


(Dave) #858

Heard there was a smartthings outage today so that could be why as well.

@redloro or anyone able to answer my issue above around not seeing any zones in Things after panel discovery, but being able to trigger arm and disarm? Been over a week and haven’t made any progress… Would really appreciate if someone that experienced this issue previously could give some tips on how they solved it.


(jason) #859

Unfortunately I am not someone with experience on this topic at all for solutions. However, I did have this issue earlier with my setup, but I don’t know exactly what solved my problem. I basically suggest to switch things around and back to see if it fixes itself. I would change the config file to manual and run that and then change it back to discover and stuff like that to see what happens. I know I did that and eventually it just worked.


(jason) #860

So not only am I still having the issue with my alarm system devices not working when my system is armed (comment 835 above), but now I also am having smartthings not showing proper information. when I arm my alarm via Honeywell panel, it does not show it being armed in smartthings app. It still shows disarmed.


(Dave) #861

Hi @kajones02! It looks like I’m getting the same error as you. Did you ever get a resolution to your issue of Things not showing up?

@jmfrankie Yep I tried changing the auth code, port 8888, toggles for discovery, etc. to no avail. I also tried switching to manual and back to discovery with no luck with getting anything to show up in my Things. Maybe I’m doing something stupid… I opened the config.json and changed it to the following:

{
  "port": 8888,
  "authCode": "secret-key",
  "envisalink": {
    "address": "10.0.0.9",
    "port": "4025",
    "password": "user",
    "securityCode": "****",
    "dumpZoneTimer": "0",
    "panelConfig": {
      "type": "manual",
      "partitions": [
        {
          "partition": 1,
          "name": "Security Panel"
        }
      ],
      "zones": [
        {
          "zone": 1,
          "type": "contact",
          "name": "Front or Garage Doors"
        },
        {
          "zone": 3,
          "type": "contact",
          "name": "Back Door"
        },
        {
          "zone": 5,
          "type": "contact",
          "name": "Windows"
        }
      ]
    }
  },
  "notify": {
    "address": "10.0.0.23",
    "port": "39500"
  }
}

After doing that I restarted the STNP server, opened the smart app and saved with the discovery toggle on and off, but no new Things showed up in either toggle or with manual or discovery specified in the config.json. Did I miss anything?