Any logs? Is your motion sensor trigger happy?
Also, a lighter piston would be:
IF
motion is active
Then
Light on
Else
Wait 3 minutes
Light off
1 Like
Can someone help me find out why this variable action restriction isnāt working
The action restriction is not shown, but I only want the action to execute if the variable is equal to 1. I tried different data types but still didnāt work.
Thatās what I changed it to with a TCP and now Iām all set 
1 Like
I canāt figure out why this would be true now. Shouldnāt it be false? Dashboard says true. The conditions in the app say false. There is motion currently and itās not in between the time frameā¦
Yeah maybe I need docs 
I thought triggers were only to avoid ANDs.
Looks like the āOnly execute when variable matchesā works for system variables, but isnāt working for Local/Global variables
Is this a piston restriction or an action restriction?
Unfortunatelly, the task you ask of individual actions are scheduled just like the rest of actions. This means they are āexecutedā later, which means the values you set wonāt be available to the next condition being evaluated. This is to be able to handle 20s timeoutsā¦
It is a Action restriction.
Iām a but confused by the explanation.
I tried something else and it looks to be working if I set a variable on the conditionās true or false evaluation.
Iām still trying to figure out how to get my bedtime fade routine running. When I use fade to, it is quite unpredictable. It was set up so that if there is no motion, begin to fade. But if there is motion, I want the fade to cancel and the light to go back to 80%.
Since it didnāt work with the āsimpleā methodā¦ I went complicated. This one works better, but itās unpredictable still. It faded properly on first try yesterdayā¦ then didnāt work for a while, then at night I messed with the level of the lamp manually and the fade kicked back to working. So it seems like maybe this is getting out of sync or something.
Hereās what I tried this time. Iām still looking for just the best way to get that reliable fade with fade cancellation.
So I thought I would close the loop on this question/discussion. The best you can do with my use case is 2 pistons. The first piston being used to calculate the average temperature and save it to a global variable. And then the second piston has several triggers with individual actions. And with the way the triggers are setup only one can possibly be true when the average temperature changes.
House - Calc Avg Temp
House Fans - Auto-Adjust
I tried getting it down to one piston but that isnāt possible because variables (global or local) arenāt available to later conditions within the same piston.
I may not be understanding your verbiage correctly. With that in mind, are you saying that if you save a state and then attempt to recall that state within the same piston, that it will not function?
I tried doing the same using a variable with string data type and it worked when I used it in the send SMS action, so I donāt understand why the variable I set earlier on will not work as a action restriction variable 
I am having an issue getting CoRE working at all.
I want to leave Rule Machine behind, so I installed the app, enabled OAUTH, and set off to make my first piston.
A very simple one to test. "When The time is xx:xx then turn on outlet."
Wont work. I can turn on and off via Smartthings app just fine, but CoRE will not turn it on at the time I am designating. Any ideas?
Its the Smartthings Smart Outlet.
can you show screenshot of piston?
What Iām saying is that if you save a state or attribute to a variable it can not be used in a later condition within the same piston. It can be used within an action that occurs after the initial action of saving but not a condition within the same piston. The act of saving is an action which all actions are scheduled to occur after all of the conditions have been evaluated.
So in your example saving the state is an action and the recall that state is an action. This should function as long as the recall is after the save. In my use case I was trying to use the save in a later condition within the same piston.
I hope this helps and @ady624 correct me if Iām wrong.
2 Likes
This is because the act of setting the string data type is an action. All actions occur after all conditions have been evaluated. The act of sending the SMS is also an action which Iām assuming followed the act of setting the string data type. So thatās why that worked. Action restriction are a part of the conditions evaluation so the string data type isnāt set when itās evaluating the condition (with action restriction).
@ady624, again please correct me if Iām wrong.
2 Likes
