No announcement yet.

Understanding the log entry to track a device's errant behaviour

  • Filter
  • Time
  • Show
Clear All
new posts

    Understanding the log entry to track a device's errant behaviour

    I have en event that performs a two-step process to shut down my pool
    When executed,
    it first shuts off the pool heater (Z-wave device)
    waits 20 minutes (for the heater to cool down)
    then shuts off the pool pump (Z-wave device)

    However, in viewing the log from last night, I noticed this entry and can't figure out what caused it
    Sep-12 11:04:21 PM Z-Wave Device: Outside Pool Controls Pool Heater z Set to ON
    It was in the middle of the pool-shutdown event, when the pool heater had already been turned off by the event.
    The physical switch is outside in my cabana, so I know no one could have manually turned it on.
    It appears to have turned on right before my pump was shut down (not a good sequence, of course - hence my investigation).

    Any suggestions are welcome

    Current Date/Time: 9/13/2020 11:24:33 AM
    HomeSeer Version: HS3 ZEE S2 Edition
    Linux version: Linux HomeTrollerZeeS2V5 4.9.35-v7+ #1014 SMP Fri Jun 30 14:47:43 BST 2017 armv7l GNU/Linux System Uptime: 8 Days 23 Hours 13 Minutes 22 Seconds
    IP Address:
    Number of Devices: 242
    Number of Events: 220
    Available Threads: 399
    HSTouch Enabled: True
    Event Threads: 1
    Event Trigger Eval Queue: 0
    Event Trigger Priority Eval Queue: 0
    Device Exec Queue: 0
    HSTouch Event Queue: 0
    Email Send Queue: 0

    Enabled Plug-Ins CM15A EasyTrigger EnvCan Z-Wave

    I have only seen this type of behavior when I had a node that was failing. It is a place to start. Most of my failures have been on switches if that helps. The old jasco switches have a short life.


      I appreciate the share.
      My pool season ends today with the closing of it, so that switch goes out of use for the next 6-7 months.
      But I've noted that for watching in the Spring.