Every once in a while I open up the NodeLink server interface and see if everything is ok. Today I took a look and saw quite a few errors. So I restarted NodeLink, then the Rpi, and then the ISY. However the error persists. The error is DSC Error: Data Arrival Init - Connection reset by peer [dsc1] 

Here is the most recent log:

2019-03-01 14:13:40 - ISY NodeLink Server v0.9.28 started
2019-03-01 14:13:40 - OS: Linux raspberrypi 4.14.98-v7+ #1200 SMP Tue Feb 12 20:27:48 GMT 2019 armv7l GNU/Linux
2019-03-01 14:13:40 - Mono version: 5.18.0.240 (tarball Wed Jan 16 09:28:29 UTC 2019)
2019-03-01 14:13:41 - Web config server started (http://10.0.1.69:8090)
2019-03-01 14:14:05 - ISY resolved to 10.0.1.19 ()
2019-03-01 14:14:05 - ISY Node Server config detected (profile 1)
2019-03-01 14:14:06 - ISY Warning: Duplicate node names exist on the ISY (Home)
2019-03-01 14:14:07 - ISY Warning: Duplicate program names exist on the ISY (Great Room Lights)
2019-03-01 14:14:07 - ISY Warning: Duplicate program names exist on the ISY (Late Entry)
2019-03-01 14:14:07 - ISY Warning: Duplicate program names exist on the ISY (Cottage Driveway Email ON)
2019-03-01 14:14:07 - ISY Warning: Duplicate program names exist on the ISY (ISP's Internet Address Cottage)
2019-03-01 14:14:07 - ISY Warning: Duplicate program names exist on the ISY (ISP's Internet Address)
2019-03-01 14:14:08 - ISY Warning: Duplicate program names exist on the ISY (Coffee Machine)
2019-03-01 14:14:08 - ISY Warning: Duplicate program names exist on the ISY (New Program)
2019-03-01 14:14:08 - ISY Warning: Duplicate program names exist on the ISY (Stars ON)
2019-03-01 14:14:08 - ISY Warning: Duplicate program names exist on the ISY (Test5)
2019-03-01 14:14:08 - ISY Warning: Duplicate program names exist on the ISY (Testing OFF)
2019-03-01 14:14:08 - ISY Warning: Duplicate program names exist on the ISY (Testing ON)
2019-03-01 14:14:08 - ISY Warning: Duplicate program names exist on the ISY (Timer2)
2019-03-01 14:14:08 - ISY Warning: Duplicate program names exist on the ISY (Weather)
2019-03-01 14:14:09 - Relay Server: Started on port 2405
2019-03-01 14:14:09 - DSC Error: Data Arrival Init - Connection reset by peer [dsc1]
2019-03-01 14:14:39 - DSC: Reconnecting To Server [dsc1]
2019-03-01 14:14:39 - DSC Error: Data Arrival Init - Connection reset by peer [dsc1]
2019-03-01 14:15:09 - DSC: Reconnecting To Server [dsc1]
2019-03-01 14:15:09 - DSC Error: Data Arrival Init - Connection reset by peer [dsc1]
2019-03-01 14:15:39 - DSC: Reconnecting To Server [dsc1]
2019-03-01 14:15:39 - DSC Error: Data Arrival Init - Connection reset by peer [dsc1]
2019-03-01 14:16:09 - DSC: Reconnecting To Server [dsc1]
2019-03-01 14:16:09 - DSC Error: Data Arrival Init - Connection reset by peer [dsc1]
2019-03-01 14:16:39 - DSC: Reconnecting To Server [dsc1]
2019-03-01 14:16:39 - DSC Error: Data Arrival Init - Connection reset by peer [dsc1]
2019-03-01 14:17:09 - DSC: Reconnecting To Server [dsc1]
2019-03-01 14:17:09 - DSC Error: Data Arrival Init - Connection reset by peer [dsc1]
2019-03-01 14:17:39 - DSC: Reconnecting To Server [dsc1]
2019-03-01 14:17:39 - DSC Error: Data Arrival Init - Connection reset by peer [dsc1]
2019-03-01 14:18:09 - DSC: Reconnecting To Server [dsc1]
2019-03-01 14:18:09 - DSC Error: Data Arrival Init - Connection reset by peer [dsc1]
2019-03-01 14:18:39 - DSC: Reconnecting To Server [dsc1]
2019-03-01 14:18:39 - DSC Error: Data Arrival Init - Connection reset by peer [dsc1]
2019-03-01 14:19:09 - DSC: Reconnecting To Server [dsc1]
2019-03-01 14:19:09 - DSC Error: Data Arrival Init - Connection reset by peer [dsc1]
2019-03-01 14:19:39 - DSC: Reconnecting To Server [dsc1]
2019-03-01 14:19:39 - DSC Error: Data Arrival Init - Connection reset by peer [dsc1]
2019-03-01 14:20:09 - DSC: Reconnecting To Server [dsc1]
2019-03-01 14:20:09 - DSC Error: Data Arrival Init - Connection reset by peer [dsc1]
2019-03-01 14:20:39 - DSC: Reconnecting To Server [dsc1]
2019-03-01 14:20:39 - DSC Error: Data Arrival Init - Connection reset by peer [dsc1]
2019-03-01 14:21:09 - DSC: Reconnecting To Server [dsc1]
2019-03-01 14:21:09 - DSC Error: Data Arrival Init - Connection reset by peer [dsc1]
2019-03-01 14:21:28 - DSC Error: Send Data - The socket has been shut down [dsc1]
2019-03-01 14:21:39 - DSC: Reconnecting To Server [dsc1]
2019-03-01 14:21:39 - DSC Error: Data Arrival Init - Connection reset by peer [dsc1]
2019-03-01 14:22:09 - DSC: Reconnecting To Server [dsc1]
2019-03-01 14:22:09 - DSC Error: Data Arrival Init - Connection reset by peer [dsc1]
2019-03-01 14:22:39 - DSC: Reconnecting To Server [dsc1]
2019-03-01 14:22:39 - DSC Error: Data Arrival Init - Connection reset by peer [dsc1]

I have the latest versions of NodeLink and Mono on my Rpi which is running Raspian 9 (Stretch ).

The error seems to occur every time any of the DSC alarm sensors is tripped. Despite this NodeLink is still passing the status of the sensor to the ISY (Open or Closed).

Any thoughts on how to resolve this?

 

The error is not with sensor trips, it's occuring every 30s which is NodeLink's ping check to verify the connection to the EVL is still alive.  

I would try restarting the EVL, it seems like it's closing the connection to NodeLink.