I made a rule that keeps my hall light on at different brightnesses during the evening/night hours. I noticed that the light comes back on during the day after i use the physical switch to turn it off. I can't figure out why it's coming back on.
and here's the Action/Trigger log:
Did you check the device that is coming back on and make sure there are no other rules that might be turning it on. On the devices page you can see every app that the device is linked to.
Also you might do some more searching, I thought I might have read something about issues with sunrise sunset in RM5, but I am not sure. I haven't had any issues with that so I really didn't read what it was about.
I will investigate this...
Would you please post a screenshot of the portion of App Status page for Event Subscriptions (gear icon on the app page upper right).
Event Subscriptions:
I just ran into another issue with the same rule -- not sure if it's related. The light did not turn on tonight as I expected. I see the "Predicate False" as part of the name at the top of the page, but inside the Predicate Conditions box shows [TRUE]
What happens when you refresh the page? Or, hit Update Rule, and see what happens.
Reloading the page didnt change anything. Clicking Update Rule did make the Predicate False go away.
Does the Update Rule get ran automatically when clicking Done on the same page? I'm not sure I ever ran the Update Rule but I am sure I've clicked Done.
Update does the something as Done without leaving the page. These are not dynamic pages, so don't worry too much about the display details being updated or not. Usually they will be in sync. But, for example, the Apps page is not dynamic either, so it may show Predicate False, when it is true, just because it hasn't been refreshed since the state changed.
Here's a different rule that is also running with predicate false:
Notice it detected that I raised the dimmer of my kitchen lights near 8:30pm and ran the rule.
dev:4612021-07-25 08:46:37.628 pm debugKitchen Lights: SwitchMultilevelReport(value: 87, targetValue: null, duration: null)
dev:4612021-07-25 08:46:37.427 pm debugKitchen Lights: Unhandled: SwitchMultilevelSet(dimmingDuration:null, value:null)
dev:4612021-07-25 08:46:36.973 pm debugKitchen Lights: SwitchMultilevelReport(value: 87, targetValue: null, duration: null)
dev:4612021-07-25 08:46:34.840 pm debugKitchen Lights: SwitchMultilevelReport(value: 87, targetValue: null, duration: null)
dev:4612021-07-25 08:46:33.186 pm debugKitchen Lights: SwitchMultilevelReport(value: 87, targetValue: null, duration: null)
app:6822021-07-25 08:46:33.071 pm infoAction: Poll: Aubrey’s Ceiling Light, Kitchen Table Light
dev:4612021-07-25 08:46:32.338 pm debugKitchen Lights: CentralSceneNotification(keyAttributes:0, sceneNumber:2, sequenceNumber:36)
app:6762021-07-25 08:46:06.950 pm infoDelay Over: Dim: Kitchen Lights, Kitchen Table Light: 0
[...]
dev:4612021-07-25 08:31:11.905 pm debugKitchen Lights: SwitchMultilevelReport(value: 87, targetValue: null, duration: null)
dev:4612021-07-25 08:31:11.373 pm debugKitchen Lights: SwitchMultilevelReport(value: 87, targetValue: null, duration: null)
dev:4612021-07-25 08:31:11.373 pm debugKitchen Lights: CentralSceneNotification(keyAttributes:1, sceneNumber:2, sequenceNumber:35)
dev:4612021-07-25 08:31:08.575 pm debugKitchen Lights: SwitchMultilevelReport(value: 87, targetValue: null, duration: null)
app:6762021-07-25 08:31:06.925 pm infoTurn off Kitchen Lights at night: Predicate Conditions false
app:6762021-07-25 08:31:06.898 pm infoAction: Dim: Kitchen Lights, Kitchen Table Light: 0 --> fade: 30 --> delayed: 0:15:00
app:6762021-07-25 08:31:06.856 pm infoTurn off Kitchen Lights at night Triggered
dev:4612021-07-25 08:31:06.758 pm debugKitchen Lights: SwitchMultilevelReport(value: 87, targetValue: null, duration: null)
the event subscriptions for this one are:
PLEASE use screenshots for logs, not copy/paste.
Look at the Application State on the App Status page, and tell me what the value is for 'stPrimed'. I bet that now it is false. It's not possible to know what went on prior to 8:31 with this rule, and why the predicate was true then (as evidenced by the rule being triggered then. But at the end of that 8:31 sequence, the predicate became false, so presumably the lights are not turning on after that, correct?
Another thing you could do to help figure this out: Open the rule and hit Stop. Then hit Update Rule. Then look at the Application State for "stPrimed". Then see if the rule triggers when you turn on the Kitchen Lights. Have the Logs open for this entire sequence. I want to see just the logs for the rule, which you can filter at the top of the Logs page by clicking on the rule name. Start with a fresh logs page.
Are you sure you hit Done after you finished setting this rule up? There is no Event Subscription to Sunrise, which there would be if you had hit Done, since you have a condition that uses Sunrise. I just set up a rule just like yours, and there is such an Event Subscription. If you change a rule, and don't hit Done, it won't create the proper subscriptions, Scheduled Jobs, and state initialization.
stPrimed is true.
after stopping and updating, stPrimed is false.
i changed the light level and the rule is not turning off the light (a good thing for this rule).
only one entry for that filter:
i am not positive I hit Done. I would have guessed i did. In either case, after clicking Done, the sunrise subscription does show up.
I guess me not clicking 'Done' could be the cause. I can't be sure.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
Download the Hubitat app
