DSC not working after transfer to new computer

Posted on
Sun Jul 16, 2017 6:22 am
pgershon offline
Posts: 344
Joined: Jul 10, 2004

DSC not working after transfer to new computer

DSC/Envisalink-3 moved to new computer and stopped working. See error messages below. Not sure what is going on:

Code: Select all
Jul 16, 2017, 8:17:30 AM
   Error                           script error: «script» doesn’t understand the “GetsxmStation” message. (-1708)
   DSC Alarm                       Initializing communication at address: 192.168.1.191:4025
   DSC Alarm                       Communication established
   DSC Alarm Error                 Connection RX Error: connection failed ([Errno 54] Connection reset by peer)
   DSC Alarm Error                 Connection TX Error: socket connection failed: [Errno 32] Broken pipe
   Error                           plugin "DSC Alarm 2.1.0" (pid 47914) unexpectedly stopped -- restarting in 5 seconds
   Reloading plugin "DSC Alarm 2.1.0"
   Starting plugin "DSC Alarm 2.1.0" (pid 47919)
   DSC Alarm                       Log level preferences are set to "Normal".
   Started plugin "DSC Alarm 2.1.0"
   DSC Alarm                       Initializing communication at address: 192.168.1.191:4025
   DSC Alarm                       Communication established
   DSC Alarm Error                 Connection RX Error: connection failed ([Errno 54] Connection reset by peer)
   DSC Alarm Error                 Connection TX Error: socket connection failed: [Errno 32] Broken pipe
   Error                           plugin "DSC Alarm 2.1.0" (pid 47919) unexpectedly stopped -- restarting in 20 seconds
   Error                           script error: «script» doesn’t understand the “GetsxmStation” message. (-1708)
   Reloading plugin "DSC Alarm 2.1.0"
   Starting plugin "DSC Alarm 2.1.0" (pid 47920)
   DSC Alarm                       Log level preferences are set to "Normal".
   Started plugin "DSC Alarm 2.1.0"
   DSC Alarm                       Initializing communication at address: 192.168.1.191:4025
   DSC Alarm                       Communication established
   DSC Alarm Error                 Connection RX Error: connection failed ([Errno 54] Connection reset by peer)
   DSC Alarm Error                 Connection TX Error: socket connection failed: [Errno 32] Broken pipe
   Error                           plugin "DSC Alarm 2.1.0" (pid 47920) unexpectedly stopped -- restarting in 20 seconds

Posted on
Sun Jul 16, 2017 6:27 am
pgershon offline
Posts: 344
Joined: Jul 10, 2004

Re: DSC not working after transfer to new computer

I rebooted the Envisalink on its webpage software and that fixed the issue.

Posted on
Wed Jul 26, 2017 7:27 pm
pgershon offline
Posts: 344
Joined: Jul 10, 2004

Re: DSC not working after transfer to new computer

So I need to reactivate this. The problem came back after about 1 week of working Any ideas what would cause this problem to recur? Perhaps a temporary power failure?

Posted on
Wed Jul 26, 2017 11:30 pm
Korey offline
User avatar
Posts: 564
Joined: Jun 04, 2008
Location: Henderson, NV

Re: DSC not working after transfer to new computer

Looks like network issues.

--
Korey

Posted on
Thu Jul 27, 2017 1:56 am
durosity offline
User avatar
Posts: 3809
Joined: May 10, 2012
Location: Newcastle Upon Tyne, Ye Ol' England.

Re: DSC not working after transfer to new computer

I seem to recall you get that message if something else is already connected to the Envisalink which can only handle one connection at a time (which is annoying as i now have 2.. one for Indigo and one for HomeBridge-Envisalink) so you might wanna check your old machine isn't establishing a connection. You could also try power-cycling your alarm system to reset the envisalink.

Computer says no.

Posted on
Sat Aug 05, 2017 3:45 pm
johnfdl offline
Posts: 136
Joined: May 18, 2017
Location: Atlanta, GA USA

Re: DSC not working after transfer to new computer

Also, remember, only one system can be connected to Envisalink. So when I transferred from one system to another, my Envisalink kept failing with the new system because it was still connected to the old one. Just throwing that out there in case it helps.

Page 1 of 1

Who is online

Users browsing this forum: No registered users and 1 guest

cron