I.e. get rid of your but-if and put the wait for false state, wait 5 minutes turn off.
Ahhh…I see what you are saying. But that is the part that is working. My problem is that the Condition is triggering even when False. I literally watched it in Core and it said the Condition was false and ran anyways. Its performing everything perfectly when running, but running even in False.
Just to update. Your comments were correct. Since I could not make the Hallway Switch to trigger the then IF, I made a separate Piston for Arming back again.
Is there a way to dismiss SHM alerts automatically each night say at 11:59 before my system goes into an Armed/Stay mode? I want everything to change to “Everything Ok” just before that so that I can get a better view of the nights activities in the morning. I have seen people do this with IFTTT but I’d rather something a little more streamlined. I’m truly trying to limit the amount of things I have to do outside of Pistons/Native Smartthings apps.
I’ve read that ST has the SHM interactions very limited, so I don’t think that’s currently possible. And it may make sense to require a human to dismiss SHM incidents? After all, it is intended to be a security system - and allowing them to be automated away - I can see as a huge potential issue.
Do you have anything more on this? I don’t know how you’d go about doing that with IFTTT, always wanting to learn.
Are you sure you don’t have another piston that is countering it?
Yeah, that was the first thing I checked. I do have something that controls those lights in a Movie Watching routine, but that is not active.
So in my original build it fired all the time even when the Condition was False. (This is what it used to do in Lighting Director which is why I changed it to Core)
Now in trying Bobbles’ build, it doesn’t fire at all.
The problem with the wait for false state in this case is that the lights will be turned on, and when the lights are on the piston will never be false.
Try changing the IF to a Trigger, such as Sensor Bar Motion CHANGES TO Active
Remove the light bar off condition. Leave the Then statement as is.
EDIT: Just saw your latest post, if you have another setting for movie mode, you may want to paste those details here so we can think about how we make them all work together.
I would have thought it would work.
In the IF statement each action is blue, as is the overall statement therefore that means the rule is true.
The only thing I could suggest is to make the THEN action as simple as possible to start with and then introduce the mode limitations.
i.e. Take out mode limitations to start with. Make both set levels the same 60% and give it a try. Then if this works, introduce the mode limitations and see what happens.
Just looking at one of my rules, I have the set colour first and then the set level. Not sure if that makes a difference.
The problem with the wait for false state in this case is that the lights will be turned on, and when the lights are on the piston will never be false.
So maybe you could find the bug in the original and tell me why it would fire even when the Trigger was False?
Aha! I am brand new to all of this and clearly don’t know the difference between a Trigger and a Condition. I just was using trial and error. When I start building it only gives me Conditions as an option. Where do I find Triggers?
I’m stumbling around and trying to write some CoRE pistons with mixed success. One particular piston is causing me two problems - the first quite likely because of misunderstanding or bogus assumptions on my part.
Simply stated, I want to turn on “Front Porch” at a random time within 15 minutes before/after sunset, and turn it off at 11:00pm. So, my piston basically looks like this:
IF
Time is around Sunset +/- 15 minutes
THEN
Using "Front Porch"
Turn On
Wait for Custom Time 11:00 PM
Turn Off
Seems simple enough. What I’m finding is that the piston always triggers 15 minutes before sunset and the “Turn Off” task never occurs. I’d assumed that the “around Sunset +/- 15 minutes” would schedule the event at some random time within that 30 minute period, but instead it appears it’s being scheduled at the earliest opportunity within that period. The “Custom Time” also requires that I specify days of the week, so I’m checking all of the days, though it seems that ought to be optional and not specifying a day would then default to “every day”.
I can get around half of the first problem by triggering AT Sunset instead of AROUND, and doing a Wait (Random) for 1-15 minutes, but that doesn’t allow for triggering BEFORE sunset.
I tried it with Time is Between and it seems random enough. Pick both Sunset and do your offsets.
Edit: For the specific Off time, you might have to get creative and do some math with variables to calculate the +/- offset & 11pm. It sounds good in my head but I don’t know if I can execute it LOL.
Edit2: Sorry, it doesn’t look like it is random at all. Still playing with possible workaround.