Announcement

Collapse
No announcement yet.

Problems with .81 on HS2

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

    Problems with .81 on HS2

    Hi Spud, it's a long story but the short version is:

    I updated from .52 to .81 a while back because I was having problems with email, so now I'm having problems with a ton of stuff. One of those involves Envisalink.

    It seems to be loosing its connection (see below for a snip of the log from a startup this AM --- I had a ton of these in my log when I got up today) Any ideas what might be causing it.....


    11/10/2013 4:24:32 AM Plug-In Finished initializing plug-in EnvisaLink
    11/10/2013 4:24:32 AM EnvisaLink ERROR 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 XXX.XXX.XXX.XXX:XXXX
    11/10/2013 4:24:11 AM EnvisaLink DEBUG Partition Device Found: P:2
    11/10/2013 4:24:11 AM EnvisaLink DEBUG Partition Device Found: P:1
    11/10/2013 4:24:11 AM EnvisaLink DEBUG Zone Device Found: Z:16
    11/10/2013 4:24:11 AM EnvisaLink DEBUG Zone Device Found: Z:20
    11/10/2013 4:24:11 AM EnvisaLink DEBUG Zone Device Found: Z:15
    11/10/2013 4:24:11 AM EnvisaLink DEBUG Zone Device Found: Z:27
    11/10/2013 4:24:11 AM EnvisaLink DEBUG Zone Device Found: Z:5
    11/10/2013 4:24:11 AM EnvisaLink DEBUG Zone Device Found: Z:6
    11/10/2013 4:24:11 AM EnvisaLink DEBUG Zone Device Found: Z:10
    11/10/2013 4:24:11 AM EnvisaLink DEBUG Zone Device Found: Z:9
    11/10/2013 4:24:11 AM EnvisaLink DEBUG Zone Device Found: Z:11
    11/10/2013 4:24:11 AM EnvisaLink DEBUG Zone Device Found: Z:3
    11/10/2013 4:24:11 AM EnvisaLink DEBUG Zone Device Found: Z:14
    11/10/2013 4:24:11 AM EnvisaLink DEBUG Zone Device Found: Z:19
    11/10/2013 4:24:11 AM EnvisaLink DEBUG Zone Device Found: Z:25
    11/10/2013 4:24:11 AM EnvisaLink DEBUG Zone Device Found: Z:4
    11/10/2013 4:24:11 AM EnvisaLink DEBUG Zone Device Found: Z:23
    11/10/2013 4:24:11 AM EnvisaLink DEBUG Zone Device Found: Z:8
    11/10/2013 4:24:11 AM EnvisaLink DEBUG Zone Device Found: Z:17
    11/10/2013 4:24:11 AM EnvisaLink DEBUG Zone Device Found: Z:22
    11/10/2013 4:24:11 AM EnvisaLink DEBUG Zone Device Found: Z:13
    11/10/2013 4:24:11 AM EnvisaLink DEBUG Zone Device Found: Z:28
    11/10/2013 4:24:11 AM EnvisaLink DEBUG Zone Device Found: Z:2
    11/10/2013 4:24:11 AM EnvisaLink DEBUG Zone Device Found: Z:1
    11/10/2013 4:24:11 AM EnvisaLink DEBUG Zone Device Found: Z:24
    11/10/2013 4:24:11 AM EnvisaLink DEBUG Zone Device Found: Z:18
    11/10/2013 4:24:11 AM EnvisaLink DEBUG Zone Device Found: Z:26
    11/10/2013 4:24:11 AM EnvisaLink DEBUG Zone Device Found: Z:21
    11/10/2013 4:24:11 AM EnvisaLink DEBUG Zone Device Found: Z:12
    11/10/2013 4:24:11 AM EnvisaLink DEBUG Zone Device Found: Z:7
    11/10/2013 4:24:11 AM Plug-In Initializing Plug-in: EnvisaLink

    #2
    Hi,

    This is the kind of error you get when the plugin cannot access the EnvisaLink server. Make sure the ip in the config page is correct, and that you don't have a firewall or AV blocking traffic to this ip.

    Can you access the envisalink local web page from a browser on your HS machine?

    Comment


      #3
      yes I can log in locally

      Yes, I can log in locally, but it looks like HS can't connect, see below for current status. I'm running 1.0.0.6, should I be on a different build?

      PS I can see the board from the EnvisaLink web site also

      PPS when I rebooted HS it connected - not sure what is going on - sigh
      Attached Files
      Last edited by norcoscia; November 10, 2013, 08:36 AM.

      Comment


        #4
        1.0.0.6 is fine

        so after reboot of HS it works?
        if you still get problems you can try to reboot the EnvisaLink board from web page.
        and if the problem still occurs, try to open a telnet session with EnvisaLink TPI. The EnvisaLink TPI server listen on port 4025, so the command is:

        telnet <envisalink_ip> 4025

        if everything ok, it should answer with the message: 5053CD

        Comment


          #5
          OK, thanks...

          OK, and I'll leave debug on and see if it catches anything, right now it seems to be fine. The problem is very random

          It is likely on the HS side - ever since I updated from .52 to .81 I have been having one problem after the next.

          Comment


            #6
            Debug error capture

            This was in my log, not sure it is important but wondering what caused it?

            11/11/2013 3:52:26 PM EnvisaLink DEBUG CommandAcknowledge 000
            11/11/2013 3:52:25 PM EnvisaLink INFO Reconnection OK
            11/11/2013 3:52:25 PM EnvisaLink DEBUG Stack: at System.String.InternalSubStringWithChecks(Int32 startIndex, Int32 length, Boolean fAlwaysCopy) at EnvisaLink.Communications.TpiResponse.Parse(String data) at EnvisaLink.Communications.Reciever.Run() at EnvisaLink.Communications.Communicator.ListenForData()
            11/11/2013 3:52:25 PM EnvisaLink ERROR Index and length must refer to a location within the string.Parameter name: length
            11/11/2013 3:52:25 PM EnvisaLink DEBUG PartitionReadyForceArmingEnabled 1
            11/11/2013 3:52:25 PM EnvisaLink DEBUG Request: Poll
            11/11/2013 3:51:48 PM Event Event Trigger "NetCam camera motion test"
            11/11/2013 3:50:26 PM EnvisaLink DEBUG CommandAcknowledge 000
            11/11/2013 3:50:25 PM EnvisaLink DEBUG Request: Poll
            11/11/2013 3:48:26 PM EnvisaLink DEBUG CommandAcknowledge 000

            Comment


              #7
              It means the plugin failed to parse one message, unfortunately plugin didn't log the data sent.
              Please install v1.0.0.8 which log more stuff, and post your logs again if this happens again.
              v1.0.0.8 is available here:
              http://board.homeseer.com/showthread...85#post1067585

              Comment


                #8
                OK, thx

                OK, up on v1.0.0.8 - I'll let you know if I see it again....

                Comment

                Working...
                X