Should just be a config file change.
Thanks - this is working well for me and I appreciate your help.
1 Like
This is a bit unrealated so I created another topic but....
I installed this and had it working perfectly (along with HubConnect) and 2 days ago the app and all my DSC devices disappeared from Hubitat (HubConnect too).
The Envisalink code and the drivers are still there but the published app is gone.
Argggg. I am moving from ST for stability reasons and looks like I'm getting the bad side of HE now 
Again today the Envisalink devices are gone. Smart now 
so I back up every time I've made a change so I restored and everything is back.
The only thing I can't seem to figure out is what makes the bridge re-establish the TPI connection?
I've tired Init, On, Poll in HE and restart of the EVL3 software but I can't get ONLINE again in the Envisalink UI.
Logs inb Init:
dev:1072021-01-02 11:24:58.068 errorjava.lang.IllegalArgumentException: null on line 1064 (telnetStatus)
dev:1072021-01-02 11:24:58.060 errorjava.lang.IllegalArgumentException: null on line 1019 (parse)
dev:1072021-01-02 11:24:57.844 errorjava.lang.IllegalArgumentException: null on line 1019 (StatusReport)
dev:112021-01-02 11:24:53.657 infoOffice Motion: Reset to motion inactive after 61 seconds
dev:1072021-01-02 11:24:47.852 errorjava.lang.IllegalArgumentException: null on line 1019 (parse)
Looks like I'm screwed. Recreated the app again and it connects!
I can't seem to figure out how to delete all the old devices, the delete box is greyed out. Tried a few things in the forum suggestions but no luck so far.
You appear to be using Doug’s native option, correct? If so, I’m not sure I can be much help on it. Not sure how to delete things if that option is grayed out.
Yes, DSC for EVL3. Seemed to be the one that was suggested when I first got on the forum.
Hey Brian,
I think I am like 95% good with setting up my Vista 20P through a node proxy using your method. I am still unable to see any sensors in the app. When I watch the node server.js run it shows this:
[2021-01-06T16:49:52.053Z] [evl4] {"type":"partition","partition":1,"state":"ready","alpha":"DISARMED Ready to Arm"}
[2021-01-06T16:49:52.054Z] [stnp] Notify server address and port not set!
Any idea where its looking for the server address and port? I believe it is set correctly in the app and the config.json.
In your config.json for smartthings-nodeproxy, do you have a notify section? If not, configure that to be IP of your HE and port 39501. You'll have to restart smartthings-nodeproxy after this change.
The bottom of my config looks like this:
},
"notify": {
"address": "192.168.1.16",
"port": "39501"
}
}
If that works, I can look to add this functionality into the HE App.
1 Like
Thanks! That took care of the node. Now I see the status in the device but it did not create sensors and wont let me arm from the app. I tried to turn the discover button off, go out of the app, then back in with no luck. Anything else I could try?
Could it have something to do with this:
[2021-01-06T18:58:35.566Z] [stnp] ::ffff:192.168.1.220 GET /subscribe/192.168.1.220:39501
[2021-01-06T18:58:35.567Z] [stnp] Authentication error
I am guessing you have authentication turned on on your hub? If so, there will be changes required to smartthings-nodeproxy to support auth.
Easier to turn it off? Where do I find the setting?
I turned off Hub Security with no luck. The Authentication error only shows up when I attempt to auto discover the devices.
Is there something I could use to check if the necessary authenication is open? The Hubitat log shows:
app:662021-01-07 12:02:18.431 pm warnConnection refused (Connection refused)
app:662021-01-07 12:02:18.422 pm debugHoneywell Security: send command: /plugins/envisalink/config/192.168.1.187:4025:user:****
I've double checked all of my ip, mac, and passwords and they all match. Restarted the service and the hub. Maybe there is something I can add to the config file? I'm looking for any troubleshooting help.
This might tell you if you can get a connection. Run it from your docker host and use your Hub IP:
$ curl -vvv http://192.168.1.16:39501
* Expire in 0 ms for 6 (transfer 0xbfc880)
* Trying 192.168.1.16...
* TCP_NODELAY set
* Expire in 200 ms for 4 (transfer 0xbfc880)
* Connected to 192.168.1.16 (192.168.1.16) port 39501 (#0)
> GET / HTTP/1.1
> Host: 192.168.1.16:39501
> User-Agent: curl/7.64.0
> Accept: */*
>
< HTTP/1.1 200 OK
< Date: Thu, 07 Jan 2021 19:53:16 GMT
< Connection: Close
< Server: Jetty(9.4.31.v20200723)
<
* Closing connection 0This is what I get:
pi@raspberrypi:~ $ curl -vvv http://192.168.1.220:39501
- Expire in 0 ms for 6 (transfer 0x587880)
- Trying 192.168.1.220...
- TCP_NODELAY set
- Expire in 200 ms for 4 (transfer 0x587880)
- Connected to 192.168.1.220 (192.168.1.220) port 39501 (#0)
GET / HTTP/1.1
Host: 192.168.1.220:39501
User-Agent: curl/7.64.0
Accept: /
< HTTP/1.1 200 OK
< Date: Thu, 07 Jan 2021 20:03:13 GMT
< Connection: Close
< Server: Jetty(9.4.31.v20200723)
<
- Closing connection 0
pi@raspberrypi:~ $
Is there a script to see if my proxy is accepting connections? Seems like I have 3 devices that use IP's. My Evisalink 192.168.1.187, Hubitat 192.168.1.220, and my Rpi 192.168.112. I use my Rpi address as the proxy address I presume?
I do know that your Envisalink can only talk to one device at once, so if you have two instances of smartthings-nodeproxy running somewhere (i.e. having multiple telnet sessions open to the Envisalink), it will cause similar issues.
This is the only instance I can find. I still don’t understand which device is trying to authenticate. I get the status on the alarm panel, I see the status in the Honeywell app in Hubitat, but can’t send it any commands. When I go in the Honeywell app and use the Discover devices switch that’s when the authentication error comes up. Which device is trying to authenticate with which device? Also weird, if I change the proxy IP in the Honeywell App I don’t get the error. Even if it’s a ghost device. I Really appreciate all of the insight.
