Announcement

Collapse
No announcement yet.

plug in setup help

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

  • plug in setup help

    Hello,

    I am new to HS3 and trying to get everything setup. I have a DSC panel with an EVL3 that has functioned flawlessly for years.

    I have been unable to get the plugin up and running and was looking for some help.

    There doesn't seem to be much to the setup so I'm scratching my head here. I am able to login to my evl3 either using http://envisalink or its local ip address, which is 192.168.1.8. It shows as being online and all parameters are green with firmware 1.12.180. I have tried setting it up using 192.168.1.8, and also as 192.168.1.008, which is how it is presented when I login to the board and go to the network page.

    When i go to set up the plug in, I use the evl3 ip address, and the same 4 digit pin i use to login to the board. I specified the number of partitions and zones and successfully named all of the zones.

    Homeseer successfully created all of the appropriate devices. I see the root device, but the user access device status is unknown, and partition 1 status is not ready. This never changes regardless of the DSC panel's actual status.

    Every time I make a change in the envisalink config page, I disable and reenable the plugin.

    Nothing seems to work. Am I missing something obvious?

    Thanks in advance for the help.

  • #2
    could you set the log level to debug and post the logs you get when you enable the plugin.

    the password you are supposed to set in the config page is the one you use to access http://envisalink (default one is is "user")

    Comment


    • #3
      Thanks spud for the quick reply.

      I am using the same password as i use to log in to the panel.

      Here is the log when i enable the plug in. It keeps repeating the same thing.


      Aug-24 10:28:43 AM EnvisaLink INFO Connection Lost, will try to reconnect in 10 seconds
      Aug-24 10:28:43 AM EnvisaLink DEBUG Stack: at System.Net.Sockets.NetworkStream.Read (System.Byte[] buffer, Int32 offset, Int32 size) [0x00000] in :0 at EnvisaLink.Communications.Reciever.Run () [0x00000] in :0
      Aug-24 10:28:43 AM EnvisaLink ERROR Receiver::Run() A socket error has occured: Read failure
      Aug-24 10:28:43 AM EnvisaLink INFO Reconnection OK
      Aug-24 10:28:43 AM EnvisaLink INFO Trying to reconnect to: 192.168.1.8:4025

      Comment


      • #4
        Do you have another program connecting to the EVL3? The EVL3 allows only one connection.

        Are you on Linux or Windows?
        To troubleshoot, try to disable any AV and firewall running on your HS3 machine.

        and please post the logs from the very beginning (i.e from the line that tells the plugin version)

        Comment


        • #5
          I don't know of anything else connecting to the EVL3. It is professionally monitored by eyez on. I access it through their interface but am not currently logged in, nor am I logged in to the panel itself.

          I am using a hometroller SEL, so LINUX and no firewall.

          Here is the complete log after re-enabling the plug in:


          Date/Time Pri Type/Error Message/Source
          Aug-24 10:52:34 AM EnvisaLink INFO Connection Lost, will try to reconnect in 10 seconds
          Aug-24 10:52:34 AM EnvisaLink DEBUG Stack: at System.Net.Sockets.NetworkStream.Read (System.Byte[] buffer, Int32 offset, Int32 size) [0x00000] in :0 at EnvisaLink.Communications.Reciever.Run () [0x00000] in :0
          Aug-24 10:52:34 AM EnvisaLink ERROR Receiver::Run() A socket error has occured: Read failure
          Aug-24 10:52:34 AM EnvisaLink INFO Reconnection OK
          Aug-24 10:52:34 AM EnvisaLink INFO Trying to reconnect to: 192.168.1.8:4025
          Aug-24 10:52:23 AM EnvisaLink INFO Connection Lost, will try to reconnect in 10 seconds
          Aug-24 10:52:23 AM EnvisaLink DEBUG Stack: at System.Net.Sockets.NetworkStream.Read (System.Byte[] buffer, Int32 offset, Int32 size) [0x00000] in :0 at EnvisaLink.Communications.Reciever.Run () [0x00000] in :0
          Aug-24 10:52:23 AM EnvisaLink ERROR Receiver::Run() A socket error has occured: Read failure
          Aug-24 10:52:23 AM EnvisaLink INFO Reconnection OK
          Aug-24 10:52:23 AM EnvisaLink INFO Trying to reconnect to: 192.168.1.8:4025
          Aug-24 10:52:11 AM Plug-In Finished initializing plug-in EnvisaLink
          Aug-24 10:52:11 AM EnvisaLink INFO Connection Lost, will try to reconnect in 10 seconds
          Aug-24 10:52:11 AM EnvisaLink DEBUG Stack: at System.Net.Sockets.NetworkStream.Read (System.Byte[] buffer, Int32 offset, Int32 size) [0x00000] in :0 at EnvisaLink.Communications.Reciever.Run () [0x00000] in :0
          Aug-24 10:52:11 AM EnvisaLink ERROR Receiver::Run() A socket error has occured: Read failure
          Aug-24 10:52:11 AM EnvisaLink DEBUG Zone Bypassed Device Found: B:8
          Aug-24 10:52:11 AM EnvisaLink DEBUG Zone Bypassed Device Found: B:7
          Aug-24 10:52:11 AM EnvisaLink DEBUG Zone Bypassed Device Found: B:6
          Aug-24 10:52:11 AM EnvisaLink DEBUG Zone Bypassed Device Found: B:5
          Aug-24 10:52:11 AM EnvisaLink DEBUG Zone Bypassed Device Found: B:4
          Aug-24 10:52:11 AM EnvisaLink DEBUG Zone Bypassed Device Found: B:3
          Aug-24 10:52:11 AM EnvisaLink DEBUG Zone Bypassed Device Found: B:2
          Aug-24 10:52:11 AM EnvisaLink DEBUG Zone Bypassed Device Found: B:1
          Aug-24 10:52:11 AM EnvisaLink DEBUG Zone Device Found: Z:8
          Aug-24 10:52:11 AM EnvisaLink DEBUG Zone Device Found: Z:7
          Aug-24 10:52:11 AM EnvisaLink DEBUG Zone Device Found: Z:6
          Aug-24 10:52:11 AM EnvisaLink DEBUG Zone Device Found: Z:5
          Aug-24 10:52:11 AM EnvisaLink DEBUG Zone Device Found: Z:4
          Aug-24 10:52:11 AM EnvisaLink DEBUG Zone Device Found: Z:3
          Aug-24 10:52:11 AM EnvisaLink DEBUG Zone Device Found: Z:2
          Aug-24 10:52:11 AM EnvisaLink DEBUG Zone Device Found: Z:1
          Aug-24 10:52:10 AM EnvisaLink DEBUG Partition Device Found: P:1
          Aug-24 10:52:07 AM EnvisaLink INFO EnvisaLink version 3.0.0.38
          Aug-24 10:52:07 AM Info Plugin EnvisaLink has connected. IP:127.0.0.1:52930

          Comment


          • #6
            if you go to the network page here: http://envisalink/3

            what do you see in the "EnvisaLink TPI Status" section?

            Comment


            • #7
              ONLINE
              Client: 192.168.1.43
              Enable TPI Session Alerts CHANGE

              Reboot Envisalink

              Firmware Version: 01.12.180 - MAC: 001C2A0088BD

              Comment


              • #8
                Originally posted by sohcrates View Post
                ONLINE
                Client: 192.168.1.43
                Enable TPI Session Alerts CHANGE

                Reboot Envisalink

                Firmware Version: 01.12.180 - MAC: 001C2A0088BD
                well, it means there is program running on 192.168.1.43 that is already connected to the EVL3.

                if 192.168.1.43 is the IP of your SEL, try to kill any "mono HSPI_ENVISALINK.exe" process that could be stuck, or even better reboot it.

                Comment


                • #9
                  I knew it was something simple, but boy do I feel silly. Even sillier than usual. I got out of HS2 a few years ago out of frustration, before many things evolved, and before the advent of HS3. I replaced HS2 with vera, and was happy with it for a long time, but it was being left behind. So now I am back to HS3 and it seems much better. So far I am very happy. In the transition, I had failed to unplug the vera. So that IP address was the vera. Shut it down, rebooted the hometroller, and we are in business. Sorry to be a dope and thanks for the help spud.

                  Comment

                  Working...
                  X