Announcement

Collapse
No announcement yet.

Unable to read data from the transport connection:

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

    Unable to read data from the transport connection:

    EVL4 with firmware 208 (01.05.208 )
    HS4 Pro Edition 4.2.19.0 (Windows)
    Plug-in 3.0.0.42


    I rebooted my EVL 4 to see if this helps, but has anyone run into this error saying the device has not responded in time in case it isn't a one-off? I noticed some of my events which fire due to state changes on my DSC alarm panel are no longer firing. Stopping/starting the plug-in itself seemed to not change the behavior.

    ERROR Receiver::Run() A socket error has occured: Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.


    #2
    Update, rebooting the EVL4 and rebooting the HomeSeer box didn't change things. Need to dig a bit deeper I suppose.

    Comment


      #3
      This error means the plugin cannot connect to the EVL board. Are you sure the IP Address set in the config page is correct? can you access the board local web interface by pasting this url in a browser?

      Comment


        #4
        Originally posted by spud View Post
        This error means the plugin cannot connect to the EVL board. Are you sure the IP Address set in the config page is correct? can you access the board local web interface by pasting this url in a browser?
        I am and I can. No change in IP as it is set via DHCP reservation. The EVL4 web interface is accessible.

        Comment


          #5
          Can you set the log level to debug and post all the logs you get when you start the plugin?
          Any firewall on your HS machine?
          Do you have any other software that connects to the EVL board?

          Comment


            #6
            I run HS4 on Windows, so only the built-in Firewall I haven't made any recent changes to. I'm unaware of anything else I'm using which interacts with the EVL4 other than Envisalink's software itself. From the logs it looks like after the 3rd "Poll" event is when it fails each time.

            Nov-24 14:41:35 INFO EnvisaLink version 3.0.0.42
            Nov-24 14:41:38 DEBUG Partition Device Found: P:1
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:21
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:22
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:23
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:24
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:25
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:26
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:27
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:28
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:29
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:30
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:31
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:32
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:33
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:34
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:35
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:36
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:37
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:38
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:39
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:40
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:41
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:42
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:43
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:44
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:45
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:46
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:47
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:48
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:49
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:50
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:51
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:52
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:53
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:54
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:55
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:56
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:57
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:58
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:59
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:60
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:61
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:62
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:63
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:64
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:1
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:2
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:3
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:4
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:5
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:6
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:7
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:8
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:9
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:10
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:11
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:12
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:13
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:14
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:15
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:16
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:17
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:18
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:19
            Nov-24 14:41:40 DEBUG Zone Device Found: Z:20
            Nov-24 14:41:41 DEBUG Request: NetworkLogin <REDACTED>
            Nov-24 14:41:41 DEBUG Request: TimeStampControl 1
            Nov-24 14:41:41 DEBUG Request: Poll
            Nov-24 14:41:41 DEBUG Request: StatusReport
            Nov-24 14:41:41 DEBUG LoginInteraction 3
            Nov-24 14:43:41 DEBUG Request: Poll
            Nov-24 14:45:41 DEBUG Request: Poll
            Nov-24 14:46:11 ERROR Receiver::Run() A socket error has occured: Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
            Nov-24 14:46:11 DEBUG Stack: at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
            at EnvisaLink.Communications.Reciever.Run()
            Nov-24 14:46:11 INFO Connection Lost, will try to reconnect in 10 seconds
            Nov-24 14:46:22 INFO Trying to reconnect to: 192.168.1.201:4025
            Nov-24 14:46:22 INFO Reconnection OK
            Nov-24 14:46:22 DEBUG Request: NetworkLogin <REDACTED>
            Nov-24 14:46:22 DEBUG Request: TimeStampControl 1
            Nov-24 14:46:22 DEBUG Request: StatusReport
            Nov-24 14:46:22 DEBUG Request: Poll
            Nov-24 14:46:22 DEBUG LoginInteraction 3
            Nov-24 14:48:22 DEBUG Request: Poll
            Nov-24 14:50:22 DEBUG Request: Poll
            Nov-24 14:50:52 ERROR Receiver::Run() A socket error has occured: Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
            Nov-24 14:50:52 DEBUG Stack: at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
            at EnvisaLink.Communications.Reciever.Run()
            Nov-24 14:50:52 INFO Connection Lost, will try to reconnect in 10 seconds
            Nov-24 14:51:03 INFO Trying to reconnect to: 192.168.1.201:4025
            Nov-24 14:51:03 INFO Reconnection OK
            Nov-24 14:51:03 DEBUG Request: NetworkLogin <REDACTED>
            Nov-24 14:51:03 DEBUG Request: TimeStampControl 1
            Nov-24 14:51:03 DEBUG Request: StatusReport
            Nov-24 14:51:03 DEBUG Request: Poll
            Nov-24 14:51:03 DEBUG LoginInteraction 3
            Nov-24 14:53:03 DEBUG Request: Poll
            Nov-24 14:55:03 DEBUG Request: Poll
            Nov-24 14:55:33 ERROR Receiver::Run() A socket error has occured: Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
            Nov-24 14:55:33 DEBUG Stack: at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
            at EnvisaLink.Communications.Reciever.Run()
            Nov-24 14:55:33 INFO Connection Lost, will try to reconnect in 10 seconds

            Comment


              #7
              I made no changes and the errors continued throughout yesterday. Suddenly around 9:20AM yesterday, everything started working again. I logged into the EVL4 interface and I see my firmware has gone from 208 to 210.

              The firmware change log shows a pretty obvious relation.

              https://forum.eyezon.com/viewtopic.p...71acc3a91aea13

              Updated 2023-11-30

              Envisalink 4
              Version 1.5.210 - DSC Only
              - TPI login timeout bug fixed.

              Version 1.5.208 - Release only for Sidekick users AND new customers with factory firmware
              - Improved response to STP probes
              - Improved handling of networks with high global Ethernet traffic (port flapping)
              - Better integration of Sidekick with CSR software
              - Fixing bug in SA build (formally UNO) where local page would not show zone openings
              - Improvements to UI response when running on LTE only
              - TPI login alerts removed. Long deprecated.‚Äč

              Comment


                #8
                From reading this thread it appears there ended up being two compounding errors, so different users were seeing slightly different errors. One was for TPI login issues, and one was for passwords longer than 8 characters.

                https://forum.eyezon.com/viewtopic.p...71acc3a91aea13

                Comment

                Working...
                X