I have a simple Trigger that runs an action. It does not appear to respect the Mode restriction. I have deleted and recreated with no change in behavior. I'm not sure if it ever followed the restriction in the past but it definitely isn't doing it now. @bravenel, please advise.
Restrictions in actions are also evaluated. Do you have restrictions defined there? I ask because I have several triggered rules with actions that are running fine.
Ok was hoping it was something simple like having a conflicting restriction in your action. 
As a work around try creating a triggered rule with mode as the condition.
The fact that it shows (Restricted) in its name suggests that it is in fact in a Restriction. That uses the exact same test. I cannot reproduce this behavior, using the exact same Restriction and running an action. Can you turn on Logs and show where this Trigger is logging that it's doing something, as it would if it is triggered.
1 Like
Found the problem.....by looking at the logs 
I reverted my database at one point and it brought back an app that I forgot about. This app was also triggering a similar set of actions that I replaced with the RM rule.
Whenever you have a problem with Hubitat Elevation, the first thing to do is to look at the Logs. Rules and triggers always log every event they see and whether a rule is true/false or a trigger triggered, unless they are restricted.
Logs are your friend, and with Past Logs, you can almost always find the answer in them.
3 Likes
Is this Rule logging new?....because for some reason I remember wishing it was there in the past and not having it
@bravenel so now that I look at the logs I'm seeing this when the action is executed (the action screenshot is posted a few posts up). These are all Hue bulbs. I deleted and recreated the action and tested again with the same error.
Nope, it's always been there.
An error from the device? Don't know about that one.
Maybe an @mike.maxwell question then?
@mike.maxwell @bravenel
After further testing I see that this error only occurs when using "Capture".
It doesn't seem to matter what type of light I select. I tried with one of my Lutron dimmers with the same result.
I added the Capture option to the trigger that called the action and got a similar error as well,
Yep, seeing the same error.
Found it. Typo. Will be fixed in next release.
1 Like
This means that you are the only person that has even tried to use capture/restore recently. Those typos have been there since 1.1.4.
Or they are probably in the same boat as me....didn't know it was broken.
I only realized because I had an extended power outage yesterday and none of my lights reverted to their proper temps. If nor for that, I would have been none the wiser.
Thanks for looking into it.
