No announcement yet.

Deleting Unused Zones Causing Error Msg in Log

  • Filter
  • Time
  • Show
Clear All
new posts

  • Deleting Unused Zones Causing Error Msg in Log

    To reduce Device listing clutter, I deleted zones that are not used (37 out of 64 zones).
    When I have HS do an EnvisaLink Action: Partition Disarm, I get an error entry for each of the 36 zones in the log saying "Error cannot find zone xx". For some seconds, other posts to the log for other actions that occurred are not logged. I don't get these errors for other EnvisaLink commands; arming, etc.

    Is this normal?... Is there a fix other than recreating all the zones?
    Last edited by Jayhawk; August 22nd, 2019, 07:01 AM. Reason: Deleting Unused Zones Causing Error Msg in Log - SOLVED

  • #2
    It looks like a bug.
    Could you set the log level to Debug from the config page, and capture the problem. Thanks


    • #3
      Attached extracts from HS3 Log and Envisalink Plugin Log



      MESSAGE BOARD (copy/paste section below to message board posts)

      Current Date/Time: 8/20/2019 9:28:19 PM
      HomeSeer Version: HS3 Pro Edition
      Operating System: Microsoft Windows 7 Home Premium - Work Station
      System Uptime: 2 Days 2 Hours 0 Minutes 58 Seconds
      IP Address:
      Number of Devices: 490
      Number of Events: 202
      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: Microsoft Security Essentials
      In Virtual Machine: No MFG: lenovo
      Enabled Plug-Ins BLRadar drhsIpPlugIn EnvisaLink
      1.2019.211.1740: MyQ Tasker Plugin TPLinkSmartHome
      3.0.6841.27363: UltraRachio3 UPB Z-Wave


      • #4
        The Envsalink log includes plugin startup which also shows the missing zones. Also it shows several disarm actions with the missing zone errors but I didn't have debug level on until the end of the log.


        • #5
          Please test version available in the beta section, it should fix this problem.


          • #6
            It is fixed per my testing... "can't find zone xx" log appears only at plugin startup in the both logs and no longer when I disarm.
            THANKS!! Awesome support!