Announcement

Collapse
No announcement yet.

Constantly Disconecting

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Constantly Disconecting

    I have installed a new HS3 instance and installed your plug in. The log file is showing a repeated disconnect and reconnect. I had your plug in working in HS 2
    Apr-27 4:43:35 PM EnvisaLink ERROR Receiver::Run() A socket error has occured: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. Apr-27 4:43:35 PM EnvisaLink INFO Reconnection OK Apr-27 4:43:35 PM EnvisaLink INFO Trying to reconnect to: 192.168.199.33:4025 Apr-27 4:43:24 PM EnvisaLink INFO Connection Lost, will try to reconnect in 10 seconds Apr-27 4:43:24 PM EnvisaLink ERROR Receiver::Run() A socket error has occured: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. Apr-27 4:43:24 PM EnvisaLink INFO Reconnection OK Apr-27 4:43:24 PM EnvisaLink INFO Trying to reconnect to: 192.168.199.33:4025 Apr-27 4:43:13 PM EnvisaLink INFO Connection Lost, will try to reconnect in 10 seconds Apr-27 4:43:13 PM EnvisaLink ERROR Receiver::Run() A socket error has occured: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. Apr-27 4:43:13 PM EnvisaLink INFO Reconnection OK Apr-27 4:43:13 PM EnvisaLink INFO Trying to reconnect to: 192.168.199.33:4025 Apr-27 4:43:02 PM EnvisaLink INFO Connection Lost, will try to reconnect in 10 seconds Apr-27 4:43:02 PM EnvisaLink ERROR Receiver::Run() A socket error has occured: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. Apr-27 4:43:02 PM EnvisaLink INFO Reconnection OK Apr-27 4:43:02 PM EnvisaLink INFO Trying to reconnect to: 192.168.199.33:4025 Apr-27 4:42:51 PM EnvisaLink INFO Connection Lost, will try to reconnect in 10 seconds Apr-27 4:42:51 PM EnvisaLink ERROR Receiver::Run() A socket error has occured: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. Apr-27 4:42:51 PM EnvisaLink INFO Reconnection OK Apr-27 4:42:51 PM EnvisaLink INFO Trying to reconnect to: 192.168.199.33:4025 Apr-27 4:42:40 PM EnvisaLink INFO Connection Lost, will try to reconnect in 10 seconds Apr-27 4:42:40 PM EnvisaLink ERROR Receiver::Run() A socket error has occured: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. Apr-27 4:42:40 PM EnvisaLink INFO Reconnection OK Apr-27 4:42:40 PM EnvisaLink INFO Trying to reconnect to: 192.168.199.33:4025 Apr-27 4:42:29 PM EnvisaLink INFO Connection Lost, will try to reconnect in 10 seconds Apr-27 4:43:35 PM EnvisaLink INFO Connection Lost, will try to reconnect in 10 seconds

  • #2
    Originally posted by JHughes View Post
    I have installed a new HS3 instance and installed your plug in. The log file is showing a repeated disconnect and reconnect. I had your plug in working in HS 2
    Apr-27 4:43:35 PM EnvisaLink ERROR Receiver::Run() A socket error has occured: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. Apr-27 4:43:35 PM EnvisaLink INFO Reconnection OK Apr-27 4:43:35 PM EnvisaLink INFO Trying to reconnect to: 192.168.199.33:4025 Apr-27 4:43:24 PM EnvisaLink INFO Connection Lost, will try to reconnect in 10 seconds Apr-27 4:43:24 PM EnvisaLink ERROR Receiver::Run() A socket error has occured: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. Apr-27 4:43:24 PM EnvisaLink INFO Reconnection OK Apr-27 4:43:24 PM EnvisaLink INFO Trying to reconnect to: 192.168.199.33:4025 Apr-27 4:43:13 PM EnvisaLink INFO Connection Lost, will try to reconnect in 10 seconds Apr-27 4:43:13 PM EnvisaLink ERROR Receiver::Run() A socket error has occured: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. Apr-27 4:43:13 PM EnvisaLink INFO Reconnection OK Apr-27 4:43:13 PM EnvisaLink INFO Trying to reconnect to: 192.168.199.33:4025 Apr-27 4:43:02 PM EnvisaLink INFO Connection Lost, will try to reconnect in 10 seconds Apr-27 4:43:02 PM EnvisaLink ERROR Receiver::Run() A socket error has occured: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. Apr-27 4:43:02 PM EnvisaLink INFO Reconnection OK Apr-27 4:43:02 PM EnvisaLink INFO Trying to reconnect to: 192.168.199.33:4025 Apr-27 4:42:51 PM EnvisaLink INFO Connection Lost, will try to reconnect in 10 seconds Apr-27 4:42:51 PM EnvisaLink ERROR Receiver::Run() A socket error has occured: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. Apr-27 4:42:51 PM EnvisaLink INFO Reconnection OK Apr-27 4:42:51 PM EnvisaLink INFO Trying to reconnect to: 192.168.199.33:4025 Apr-27 4:42:40 PM EnvisaLink INFO Connection Lost, will try to reconnect in 10 seconds Apr-27 4:42:40 PM EnvisaLink ERROR Receiver::Run() A socket error has occured: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. Apr-27 4:42:40 PM EnvisaLink INFO Reconnection OK Apr-27 4:42:40 PM EnvisaLink INFO Trying to reconnect to: 192.168.199.33:4025 Apr-27 4:42:29 PM EnvisaLink INFO Connection Lost, will try to reconnect in 10 seconds Apr-27 4:43:35 PM EnvisaLink INFO Connection Lost, will try to reconnect in 10 seconds
    I had a similar error when I had network issues in 2015. I helped another user and found he had an IP conflict. He had his Envisalink set for a static IP and another device had grabbed the IP through DHCP while his Envisalink was offline. You might look carefully at your network configuration.

    Can you access the adapter's local web page: http://envisalink?
    Randy Prade
    Aurora, CO
    Prades.net

    PHLocation - Pushover - EasyTrigger - UltraECM3 - Ultra1Wire3 - Arduino

    Comment


    • #3
      I had similar problems when it was in my workshop connected to the network via a ancient 10/100 Mbps mini Netgear switch. As soon as I took that out it resolved the issue. I was also getting the IP conflict suggestion, but that wasn't accurate. Now it's in the production location and wired into my main Netgear switch all is good.
      cheeryfool

      Comment


      • #4
        Originally posted by cheeryfool View Post
        I had similar problems when it was in my workshop connected to the network via a ancient 10/100 Mbps mini Netgear switch. As soon as I took that out it resolved the issue. I was also getting the IP conflict suggestion, but that wasn't accurate. Now it's in the production location and wired into my main Netgear switch all is good.
        My network issues in 2015 were due to a bad switch as well.
        Randy Prade
        Aurora, CO
        Prades.net

        PHLocation - Pushover - EasyTrigger - UltraECM3 - Ultra1Wire3 - Arduino

        Comment


        • #5
          Make sure that the EnvisaLink plugin in your HS2 system is disabled. Only one connection to the board is possible.

          Comment


          • #6
            Thank you. Did not realize I still had HS2 connected.

            Comment


            • #7
              Originally posted by JHughes View Post
              Thank you. Did not realize I still had HS2 connected.
              I use nodelink to act as a repeater, that way you can connect multiple clients and devices to nodelink (e.g. DSC apps you see in the app store).

              This can also be done with mpp's dscServer.jar but the setup of it is a pain as it needs a UI on first run.

              Comment

              Working...
              X