Announcement

Collapse
No announcement yet.

2 Envisalink instances - 2nd instance not reconized by events

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

  • 2 Envisalink instances - 2nd instance not reconized by events

    Hello,
    I have 2 instances of Envisalink. One labeled "EnvisaLink" which is at my house and a second labeled "EvisaLink 1711" at my garage. Both EnvisaLink cards are connected to separate DSC panels. Communication is over the internet, both locations have Z-Net boxes.

    I have the event setup to detect "if EnvisaLink - EnvisaLink 1711: Receive Message" = trigger type - "Entry Delay In Progress" from the DSC panel to turn on all the lights at the garage (See attached file named Event.jpg) . The issue - when the entry delay occurs at my house "EnvisaLink" or the garage "EnvisaLink 1711" the garage lights are triggered to go on. I need it to trigger on just "EnvisaLink 1711" not "EnvisaLink" at my house.

    Below is from my log file. I do not see it distinguish between "EnvisaLink" and "EnvisaLink 1711" both DSC systems are partition 1.

    Apr-16 6:38:54 PM EnvisaLink INFO Partition 1 status change: Entry Delay in Progress

    Thanks for you help.

    System Info:

    Current Date/Time: 4/16/2018 8:27:20 PM
    HomeSeer Version: HS3 Pro Edition 3.0.0.425
    Operating System: Microsoft Windows 10 Pro - Work Station
    System Uptime: 0 Days 4 Hours 19 Minutes 22 Seconds
    IP Address: 192.168.2.103
    Number of Devices: 181
    Number of Events: 14
    Available Threads: 200
    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: Windows Defender

    Enabled Plug-Ins
    3.0.0.56: DSC Security
    3.0.0.39: EnvisaLink
    3.0.0.39: EnvisaLink
    1.1.17344.311: MyQ
    3.0.0.21: Sonos
    3.0.6678.32449: UltraECM3
    3.0.1.190: Z-Wave
    Attached Files

  • #2
    It's a bug! Thank you for reporting it.

    It should be fixed in version 3.0.0.40 available here. Please test it and let me know.

    Comment


    • #3
      Thank you for the quick response. I will test it. Thanks

      Comment


      • #4
        Tested - .40 release fixed it. Thank you

        Comment

        Working...
        X