Lights Turning on "by themselves"

Hello,

I have create a single rule. 60 minutes before sunset, turn on ~20 lights (2 of them shown). This works, however, something is turning on the lights at ~6:50am the following day.

So, I deleted this rule and it still happened. Rebooted hub and problem went away.

Gave it a few days and it didn't happen. Recreated the rule yesterday and what do you know? Problem is back. It turns on the lights at the correct time and then again, around 6:50 in the AM. Might be important to note that the sun rose at 5:17 so it doesn't coincide with sunrise with or without the 60 minutes.

Just out of curiosity, what time was sunset? Or rather Sunset - 60 ?

S.

is the date and time and timezone correct in your hub?
Is there anything in the logs when this happens?
Did you check in the driver of one of the light and see what it's "used by". it will list your rules that use the lights.

Was it all the lights that turned on?

Go to your "Devices" tab, then select one of the devices that turned on. Scroll to the bottom and see what's listed in "In Use By"

You could also check the logs and see if something is triggering them within HE

Was it all the lights that turned on?
Yes, similar to my "home" mode

Scroll to the bottom and see what's listed in "In Use By"
For this example for my cabinet lights:
In use by
IFTTT (only used for scenes/custom response)
Cabinet Lights (Group 2.1)

Another example for Lutron Caseta
IFTTT Integration
Google Home
Guest Mode (Scene-1.2)
Home (Scene-1.2)
Movie Mode (Scene-1.2)
Night Mode (Scene-1.2)
TV Time (Scene-1.2)

is the date and time and timezone correct in your hub?
Yes, I have it set to CST and appears to be correct

Just out of curiosity, what time was sunset? Or rather Sunset - 60 ?
Sunset was at 20:23, so again, wouldn't be 60 minutes

So, two completely separate systems affected so it has to be down to HE. Unfortunately, no eureka moment .. yet :slight_smile:

FWIW, I did do my due diligence and searched. Found one person that had a similar issue and ended up in radio silence after she said she deleted the offending rule

I have set this back up again (no.. no back button :slight_smile: )

Going to reboot the hub now and test in the morning. Fingers crossed but my be a bona fide buggo

IFTTT Integration

Do you have your IFTTT applets with notifications on? If not, maybe turn those on to ensure it triggers only when you want it to. In addition to that, if possible leave a machine logged into HE so you can review the logs

2 Likes

IFTTT shows when applets are run, even without notifications. "Home" was set at 18:24 yesterday via Google Home and 20:18 by HE today.

As for logging, I will leave my PC on for the night and see what happens. I'm on 192...*/logs to see what happens between now and then.

Appreciate all the suggestions :slight_smile:

Side Note:

Under System Events, is it normal to see sunsetTime and sunriseTime even though only one of those events is in-use?

You can go to past logs, you don't need to keep the computer running. If you have too many things logging, you won't be able to go back that far anyway. Shut off logging in all devices and automations except for the things affected by this "bug" and you will be able to go back further in time. I typically get two days from my logs now.

Yes, those events are created by every hub whether or not any Apps subscribe to them.

Just found this from last night/this morning

v:172020-06-01 06:50:12.576 am infoKayla Bedroom was turned on

dev:772020-06-01 06:50:11.765 am infoChris 3 was turned on

dev:742020-06-01 06:50:11.716 am infoCHRIS 2 was turned on

dev:732020-06-01 06:50:11.557 am infoCHRIS 1 was turned on

dev:112020-06-01 06:50:11.002 am inforcvd: OUTPUT,6,1,65.00

dev:142020-06-01 06:50:10.956 am infoDining Room was turned on

dev:762020-06-01 06:50:10.504 am infoChris Room switch was turned on

dev:112020-06-01 06:50:09.954 am inforcvd: OUTPUT,2,1,100.00

dev:162020-06-01 06:50:09.904 am infoFront Porch was turned on

dev:112020-06-01 06:50:08.957 am inforcvd: OUTPUT,12,1,100.00

dev:182020-06-01 06:50:08.902 am infoLiving Room was turned on

dev:112020-06-01 06:50:07.714 am inforcvd: OUTPUT,9,1,53.00

dev:152020-06-01 06:50:07.622 am infoUpstairs Hallway was turned on

dev:22020-06-01 06:50:07.356 am infoCabinet 4 was turned on

dev:42020-06-01 06:50:07.166 am infoCabinet 3 was turned on

dev:32020-06-01 06:50:07.102 am infoCabinet 2 was turned on

dev:682020-06-01 06:50:07.061 am infoUtil Light 1 was turned on

dev:52020-06-01 06:50:06.700 am infoCabinet 1 was turned on

dev:62020-06-01 06:50:06.115 am infoCabinet Lights switch was turned on

dev:112020-06-01 06:50:04.459 am inforcvd: OUTPUT,7,1,65.00

dev:132020-06-01 06:50:04.349 am infoChandeleir was turned on

dev:222020-06-01 06:50:04.204 am infoFamily 3 was turned on

dev:212020-06-01 06:50:04.061 am infoFamily 2 was turned on

dev:202020-06-01 06:50:03.918 am infoFamily 1 was turned on

dev:232020-06-01 06:50:03.716 am infoFamily Room switch was turned on

dev:112020-06-01 06:50:02.739 am inforcvd: OUTPUT,4,1,100.00

dev:122020-06-01 06:50:02.703 am infoKitchen was turned on

Do you have a Caseta scene setup in the Lutron app? Or any other integration that’s tied directly into your Caseta bridge?

No, but that's why I posted the Osrams. Other items that aren't tied to anything but HE are coming on.

It just did it again at 06:50 ....grr

Time to contact Hubitat? Not sure where that 08:26 trigger came from but nothing turned on at that time/only 06:50

actSubTypeMain.1 enum Activate scenes
actSubTypeMain.2 enum Set dimmer level
actTypeMain.1 enum Activate Scenes, Adjust Shades or Fans
actTypeMain.2 enum Set Dimmers and Bulbs
atSunsetOffset1 number -60
dimAMain.2 capability.switchLevel Front Porch
dimLAMain.2 text 100
origLabel text Evening - Lights On
sceneActMain.1 enum ["71"]
tCapab1 enum Certain Time
time1 enum Sunset

House (Location) sunsetTime beforeSunsetHandler false
Application State
Name Value
actionDone true
actionListMain [1, 2]
actionsMain {1={wait=null, delay=, modes={}, method=getActivateScene, rule=0, cond=0}, 2={wait=null, delay=, modes={}, method=getSetDimmer, rule=0, cond=0}}
actLabelIndent
actNdx 3
allVars {}
allVarsO []
cancelCapab false
capabActDone false
capabDone true
capabsfalse {1.false={}}
capabstrue {1.true=When time is Sunset-60 minutes, 2.true={}}
certainTimes []
connectors {}
editCondIf
gvList []
hasAll false
hasCompleteRule false
hasCondition false
hasDevice
hasElse false
hasRuleAct false
hasWaitEvent false
howMany 0
howManyT 6
inIf false
inRepeat false
installed true
installedCapabs [Telnet, Polling, PushableButton, ColorMode, TemperatureMeasurement, Notification, Battery, SwitchLevel, ColorTemperature, SpeechSynthesis, Initialize, Switch, PresenceSensor, Configuration, Light, Actuator, ColorControl, ContactSensor, Refresh, RelativeHumidityMeasurement, ChangeLevel, AudioVolume, Sensor]
lastEvtDate 02-Jun-2020
lastEvtDevId
lastEvtName Triggered
lastEvtTime 08:26 AM
lastEvtValue
locationBlocked []
lvList []
ndx.false 1
ndx.true 2
nestedBlockMain []
nestedIfMain []
nestedInIf []
nestedLabel []
nestedRepIf []
nestedSkipAllMain []
paramNdx 1
paramsDone false
prevState {PB=true}
private true
repeating []
ruleNdx 1
selectActionsParams {thisStr=Main, label=Evening - Lights On}
simpleCond false
skippingMain false
subscribedVariables []
timeTriggers []
timeTriggersW {}
token 0
trigCustoms []
varUseList {}
waitB {}
waitBL {}
waitBV {}
waitCondNdx 1
waitConds []
waitEvents []

Moving to @support_team