Connection error to envisalink about homebridge-envisalink

[RGKS]

I'm getting the same error. Have you been able to find the fix?

[olines]

I am also getting this error.

I have a DSC panel with Envisalink4.

[zegnas11]

My Envisalink4 arrived today. installed on DSC1616 panel. My homebridge is running on the Raspberry Pi3.

Here is the issue that is similar to (or same as) the above comments....

With homebridge-envisalink plugin, homebridge gets killed with the error "events.js:141
throw er; // Unhandled 'error' event
^

Error: connect ECONNRESET 192.168.1.60:4025

For now, while the plugin is active (not sure if I should remove it) I just commented out the config.json portion of the envisalink section, so the rest of the homebridge is operational. So far so good, would really love to have a working envisalink plugin and I dont have any programming skills. So am waiting....

Any fix is highly appreciated.

[lsmith07]

After installing the plugin (ver 0.1.3) for the first time 3 days ago, I too received this error. For me, it was caused by my host IP entry in config.json: I had "10.0.1.024" instead of "10.0.1.24". Once I corrected it the plugin loaded and homebridge stayed connected. If you haven't already, I suggest validating your Envisalink's IP address by entering it into your browser to log in with the user/user default credentials. You should do this anyhow to change the default password from "user" (just don't forget to update your config.json file after doing so). Also, you should set Envisalink's IP to static (or DHCP reserved), to avoid it changing and introducing a connection issue again. I also suggest updating the plugin to the latest version (0.1.4); it resolves a secondary issue I encountered after getting past this connection issue. Here's a link for obtaining Envisalink's IP address if the one you have is incorrect or has changed: http://www.eyezon.com/AccessingEnvisalinkApplicationNoteEZ.pdf.

[dustindclark]

Closing out really old issue that is not recreatable on current version of NodeAlarmProxy and HomeBridge. Please re-open if this issue persists.