Still seems to work, but logs are full of this:

2018-05-07 00:30:00 - DSC: Reconnecting To Server [dsc]
2018-05-07 00:30:00 - DSC Error: Data Arrival Init - Connection reset by peer [dsc]
2018-05-07 00:30:30 - DSC: Reconnecting To Server [dsc]
2018-05-07 00:30:30 - DSC Error: Data Arrival Init - Connection reset by peer [dsc]
2018-05-07 00:31:00 - DSC: Reconnecting To Server [dsc]
2018-05-07 00:31:00 - DSC Error: Data Arrival Init - Connection reset by peer [dsc]
2018-05-07 00:31:30 - DSC: Reconnecting To Server [dsc]
2018-05-07 00:31:30 - DSC Error: Data Arrival Init - Connection reset by peer [dsc]
2018-05-07 00:32:00 - DSC: Reconnecting To Server [dsc]
2018-05-07 00:32:00 - DSC Error: Data Arrival Init - Connection reset by peer [dsc]
2018-05-07 00:32:30 - DSC: Reconnecting To Server [dsc]
2018-05-07 00:32:30 - DSC Error: Data Arrival Init - Connection reset by peer [dsc]
2018-05-07 00:33:00 - DSC: Reconnecting To Server [dsc]
2018-05-07 00:33:00 - DSC Error: Data Arrival Init - Connection reset by peer [dsc]
2018-05-07 00:33:30 - DSC: Reconnecting To Server [dsc]
2018-05-07 00:33:30 - DSC Error: Data Arrival Init - Connection reset by peer [dsc]
2018-05-07 00:34:00 - DSC: Reconnecting To Server [dsc]
2018-05-07 00:34:00 - DSC Error: Data Arrival Init - Connection reset by peer [dsc]
2018-05-07 00:34:30 - DSC: Reconnecting To Server [dsc]
2018-05-07 00:34:30 - DSC Error: Data Arrival Init - Connection reset by peer [dsc]

Do I need to change any settings?

What's your setup (OS, versions, EVL, etc.).

There was a small change to the socketclient for DSC, no issues with my EVL2.  

 

I'll have to check when I get home to say for sure, but running on a pi2... raspbian that was updated a couple months ago and I know my envisalink isn't the newest one which I think is a 4. I wanna say mine is a 3.

---------------------------------------EDIT---------------------------------------------------------

Ok, it is a pi 2, raspbian 8 (Jessie) and it is an envisalink 3

Edited May 7, 20187 yr by danbutter
Verify

Not sure why the EVL would keep closing the connection.  Is there a windows machine you could try it on?

Or open the evl port through your router for me to try?

Running RPi3, Jessie, envisalink 3.  No issues.  I see the update and restart...everything connected fine.

I was able to reproduce this by trying to connect to the EVL twice.  My guess is you have two instances of NodeLink running.

The EVL only allows a single connection.

I guess that is possible. I had been trying to get the pi to startup things automatically...maybe I messed something up.

I went another route and tried to see how to update the envisalink firmware. I had never signed up for an account and it had never been online so it never updated. Went from 1.07 to 1.12 once online and I haven't seen the issue yet. Rebooted nodelink again and still clean logs. Could be coincidence.

Will check again in a couple days.