Announcement

Collapse
No announcement yet.

Better Zwave Management

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

  • Better Zwave Management

    Last night my Zwave Schlage BE468CAM619 (Camelot) lock failed to lock at its designated night time. The event produced the following errors in the log:
    10/11/2018 10:01:00 PM,Event,Event Trigger "ZWave Lock Garage"
    10/11/2018 10:01:00 PM,Device Control,Device: 6-Z-Wave Garage Door Lock to Lock (255)
    10/11/2018 10:01:08 PM,Z-Wave Error,Failed sending Z-Wave command to device: 6-Z-Wave Garage Door Lock

    I didn't notice this failure until this morning. When I went to test it, manually and via the event that failed, it worked fine:
    Manual:
    Oct-12 11:01:11 AM Device Control Device: 6-Z-Wave Garage Door Lock to Lock (255) by/from: CAPI Control Handler
    Oct-12 11:01:14 AM Z-Wave Device: 6-Z-Wave Garage Door Lock Set to 255
    Oct-12 11:01:38 AM Device Control Device: 6-Z-Wave Garage Door Lock to Unlock (0) by/from: CAPI Control Handler
    Oct-12 11:01:39 AM Z-Wave Device: 6-Z-Wave Garage Door Lock Set to 0

    Via Event:
    Oct-12 11:23:02 AM Z-Wave Device: 6-Z-Wave Garage Door Lock Set to 0
    Oct-12 11:23:00 AM Device Control Device: 6-Z-Wave Garage Door Lock to Unlock (0) by/from: CAPI Control Handler
    Oct-12 11:22:49 AM Z-Wave Device: 6-Z-Wave Garage Door Lock Set to 255
    Oct-12 11:22:47 AM Device Control Device: 6-Z-Wave Garage Door Lock to Lock (255)
    Oct-12 11:22:47 AM Event Event Trigger "ZWave Lock Garage"
    Oct-12 11:22:47 AM Event Event ZWave Lock Garage triggered by the event page 'Run' button.

    Two questions, is there anyway to get more information regarding this lock failure and what caused it? (2) Is there an event for one of the Zwave lock devices that will allow me to capture this error in the future so I can provide some notification?

    Thanks
    Gary

    Current Date/Time: 10/12/2018 11:10:37 AM
    HomeSeer Version: HS3 Pro Edition 3.0.0.445
    Operating System: Microsoft Windows 10 Pro - Work Station
    System Uptime: 0 Days 11 Hours 5 Minutes 13 Seconds
    IP Address: 192.168.1.83
    Number of Devices: 262
    Number of Events: 92
    Available Threads: 800
    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
    2.0.57.0: BLBackup
    2.0.62.0: BLOnkyo
    1.0.4.0: BLShutdown
    2.18.1.0: MCSSPRINKLERSP
    30.0.0.36: RFXCOM
    3.0.6551.16959: UltraGCIR3
    3.0.0.40: X10
    3.0.1.218: Z-Wave

  • #2
    Schlage BE469 locks have an associated "System Notification" child device for reporting errors - if the BE468 has one, that's likely the place it would have shown up - was there any change there? If so, you an event that watches for a change to the "System Notification" child device.

    Comment


    • #3
      Door locks are notorious for just this type of behavior. I used BLLogMonitor to detect the error you reported above and implemented some retry logic.This worked most of the time. I have Kwikset door locks and they too periodically report this error and fail to lock/unlock.My hope is that the new ZWave Plus door locks resolve this issue but currently HS3 does not support the protocol for ZWave Plus locks.

      Bob

      Comment


      • #4
        Thanks to both of you for your feedback, greatly appreciated. Yes, the "System Notification" device does have an event for "Invalid/Error" state, however its date and time shows to never have been set. There are at least 4 other Lock devices that have that same "Invalid or Error State", so I set up an event for all of them so I will see what happens. Whatya think?

        Gary


        Click image for larger version  Name:	uc?id=1jE9mX1MyUwuqwA4_4NNv-UIBZvXHR2sJ.jpg Views:	1 Size:	53.5 KB ID:	1252849

        Comment

        Working...
        X