Announcement

Collapse
No announcement yet.

Lighting randomly turning off 10 minutes after event turns them on

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

    Lighting randomly turning off 10 minutes after event turns them on

    Not sure how long this has been going on since they are all outside lights, and with daylight lasting longer, I just noticed.

    this is happening on several lights, but I'll pick one for example.

    I have an event that turns on my porch lights 20 minutes before sunset. (here around 8:38pm)... then another event that turns them off at 11pm.

    What is happening is that the lights are turning off on their own about 10 minutes after going on, then again (on/off) later. Then the actual OFF even occurs, but the lights are already off. Log below.

    I have searched high and low to find another event that might be firing, but i can't find anything. And again, this is happening with at least 4 lights that I know of that are part of different outside events. And these aren't all the same type of devices either.

    One commonality is that it seems to be happening almost exactly 10 minutes after the light goes on.

    Please help me troubleshoot... i'm stumped.. (as a side note, i swear i'm having deja vu on this, but can't find it anywhere)

    Click image for larger version  Name:	image.png Views:	0 Size:	203.6 KB ID:	1620657


    Date/time=6/17/2023 11:05:44 PM Pacific Daylight Time
    Version=HS4 Standard Edition 4.2.18.5 (Windows)
    License=Registered
    License ID=665973
    MyHS Subscription=Lite
    MyHS Subscription Backup Interval=No Backup
    MyHS Subscription Max Cameras=1
    Confguration File=C:\Program Files (x86)\HomeSeer HS3\Data\HomeSeerData.json
    In Virtual Machine=No MFG: gigabyte technology co., ltd.
    Antivirus=Windows Defender
    OS=Microsoft Windows 10 Pro - Work Station
    OS Version=10.0.19045
    Uptime=18 Days 11 Hours 1 Minute 33 Seconds
    User/Access=thomasgruver@hotmail.com (Admin)
    Lan IP=172.21.64.1 (GruverServer2)
    Client IP=192.168.1.184 (MININT-UUP21CL.localdomain)
    WAN IP=66.235.1.31 ()
    Device Count=903
    Event Count=156
    Last Event Ran=Environmental : Internet Status Check, Ran at 6/17/2023 11:02:34 PM
    # of unique event scripts=5
    Connected Speaker Clients=GRUVERSERVER2 (192.168.1.60):WALL BONUS BACKUP #1, GRUVERSERVER2 (192.168.1.176):WALL TABLET - ENTRYWAY, GRUVERSERVER2 (192.168.1.240):BACKUP, GRUVERSERVER2 (192.168.1.198):BONUS ROOM TABLET, GRUVERSERVER2 (192.168.1.211):KITCHENDELL, GRUVERSERVER2 (192.168.1.243):MASTER BEDROOM FIRE TABLET, GRUVERSERVER2 (192.168.1.199):WORKOUT ROOM LENOVO TABLET, GRUVERSERVER2 (192.168.1.126):GREAT ROOM NEW FIRE
    Processor:=Intel64 Family 6 Model 60 Stepping 3 at 3.07 GHz
    Modules/Threads=119 Modules, 161 Threads
    Available Threads=1023
    System Load=200 Processes, 74% Load
    Free/Total Memory=7.75 GBytes / 15.86 GBytes (49% free)
    Free/Total Virtual Memory=9.07 GBytes / 18.24 GBytes (50% free)
    HomeSeer Memory Used=153 Mbytes
    Plugin Memory Used=15 EXE Plug-Ins using 816 Mbytes
    Plugins Installed=AK Weather 4.0.2.65,BLBackup 2.0.61.0,BLDenon 2.0.58.0,BLLogMonitor 2.0.16.0,BLShutdown 1.0.5.0,BLUPS 2.0.26.0,EasyTrigger 3.0.0.73,Ecobee 4.0.15.0,HS MyQ 4.0.14.0,MeiHarmonyHub 3.1.0.16,Sonos 3.1.0.60,Tuya 4.0.30.0,Vista Alarm 3.0.1.5,Wemo 4.0.3.0,Z-Wave 3.0.2.0​

    #2
    it does sound like you have a (group) off event someplace. I usually find on my system that's the case when that happens to me.

    The new feature added in HS4 helps me find events that are tied to devices by clicking on the device and choosing Events option in the header.

    If I don't locate it there then I use Jon00's HS4 Event Viewer and search for keywords and that usually finds it. It gets hard on an older system with an older operator such as myself keeping track of devices and events anymore

    Comment


      #3
      Omg, I found it. I did actually check all the events but missed a timer event that didn't show up because it didn't actually have the devices in it, it was just activating a member event. Weirdly that other event didn't show up in the log the way I would have expected. Thanks for your help.

      Comment

      Working...
      X