Announcement

Collapse
No announcement yet.

Envisalink Connection Attempt Failed

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

  • Envisalink Connection Attempt Failed

    I would really appreciate some help with this error:

    "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 192.168.0.19:4025"

    I am using the latest version of HS3 and the .31 version of the plugin which I believe is current.

    It was working and I don't think I made any changes to the plugin config. Envisalink seems to be working according to the Eyezon web page. It is just no longer communicating with the plugin.

    I'm lost and don't know where to start looking to troubleshoot.

    Thanks for any help.
    Last edited by cd-card-biz; October 25th, 2016, 11:53 AM.

  • #2
    it means the plugin can't connect to 192.168.0.19

    make sure this the correct IP
    try to disable any firewall/antivirus on your HS3 server
    then restart the plugin

    Comment


    • #3
      well, that was easy.

      The IP of my Envsalink had changed.

      Thanks so much for your quick reply Spud!

      Comment


      • #4
        Originally posted by spud View Post
        it means the plugin can't connect to 192.168.0.19

        make sure this the correct IP
        try to disable any firewall/antivirus on your HS3 server
        then restart the plugin
        Hey Spud,
        I'm getting this same error at random times:
        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

        I have verified with my router that the Envisalink IP and the IP in the plugin are the same. I haven't made any changes to anything and it is the same IP as it was when it was setup. I'm using an S6 Hometroller and only have Defender installed, not AV. I restarted the hometroller this morning at around 6AM PST and the error occurred at 9:21am PST.
        Any idea what could have caused this?
        Current Date/Time: 3/1/2018 10:00:28 AM
        HomeSeer Version: HS3 Pro Edition 3.0.0.420
        Operating System: Microsoft Windows Embedded Standard - Work Station
        System Uptime: 0 Days 4 Hours 6 Minutes 50 Seconds
        IP Address: 192.168.0.18
        Number of Devices: 705
        Number of Events: 363
        Available Threads: 199
        HSTouch Enabled: True
        Event Threads: 0
        Event Trigger Eval Queue: 0
        Event Trigger Priority Eval Queue: 0
        Device Exec Queue: 0
        HSTouch Event Queue: 0
        Email Send Queue: 0
        Anti Virus Installed:

        Enabled Plug-Ins
        2.0.22.0: BLOccupied
        1.0.3.0: BLShutdown
        3.1.1.24385: Blue-Iris
        3.0.0.44: EasyTrigger
        3.0.0.22: Ecobee
        3.0.0.39: EnvisaLink
        3.0.1.109: PHLocation
        0.0.0.38: Pushover 3P
        3.1.0.22: Sonos
        3.0.6104.19146: UltraRachio3
        3.0.0.83: weatherXML
        3.0.1.200: Z-Wave
        Thank you,
        HS3 3.0.0.500 &HSTouch Designer 3.0.71 with 782 Devices, 479 Events
        Plugin's:
        BLBackup, BLOccupied, BLShutdown, EasyTrigger, Ecobee,
        EnvisaLink DSC, PHLocation, Pushover, SONOS, Blue Iris, UltraRachio3,
        weatherXML, Jon00 Alexa Helper, Network Monitor, Z-Wave 3.0.1.252

        Comment

        Working...
        X