Change the AND to THEN IF.
Also, a good way to test this would be to create a virtual presence sensor and use it as the only condition. Then you don’t have to both leave for troubleshooting.
The wait and execute and whatever else needs to be delayed by the wait need to be in the same action, not separate actions. Make it look like:
Using location
> Wait 5 minutes
> Execute routine 'Away'
> Send notification ... blah blah, you get the point
1 Like
I am in the process of converting from RuleMachine over to CoRE and I understand there are some differences on how the logic flows. I have provided an image showing one of my pistons.
My problem is when the first part of the IF condition is false (illuminance level is above 100) and there is motion on the dining room, it keeps calling and executing the ELSE condition every time there is motion or if the light level changes.
I can see some advantage to doing this but it isn’t working so well in this piston.
Is there a way to stop this from happening?
Also, there there any detailed documentation that explains what some of the CoRE options are and how they work?
Thanks
There is an action restricion you can apply. Onlt execute on piston state change. Try with that.
1 Like
Thank you. It looks to have solved the problem.
I find that coming from RuleMachine is causing me more difficulty because I am thinking of how it works and applying it to CoRE which in some cases is a problem. I only have about 4-5 rules remaining to convert so hopefully once fully out of RuleMachine I won’t be so confused. Again, thanks.
1 Like
Can anyone assist me with setting up a piston to flash a certain color based on a trigger?
I’ve tried setting the color first and then running the flash condition but it reverts back to the soft white color while flashing.
Thanks in advance!
1 Like
Post a dashboard screenshot of what you have so far
1 Like
Add a Wait 15 seconds between the Flash and the Set color to “Soft White”. Flash takes almost 15 seconds, but the soft white happens right after flash starts, not after it ends.
2 Likes
@AlmostTan Yeah, what he said! Lol
2 Likes
Thanks so much, you are a god among mortals… Worked perfectly.
@bamarayne you too buddy, thanks!!
1 Like
Having to constantly guess what Tasks will execute sequentially vs. which will schedule device events and move on is a big (and will be ongoing) problem, usability-wise. Wouldn’t it be simpler for the engine to compute the length of that flash and insert the delay? That is, after all, what a user would expect. Especially given that the “normal” way to get multiple things going at once is to create another Action.
3 Likes
SDoes anyone know why this piston consistently fires at 15 minutes? I’ve set a “wait” task for 10 minutes, but I’ve tested this piston five or six times and the garage door always closes after 15 minutes instead of 10. It’s very strange. I don’t know why.
I’ve had lots of little problems with “stays” not registering accurately, if at all in some cases. I’ve actually removed it from everything at this point I think. Maybe just do If garage door is open, if true wait 10 minutes close, Then nothing, Else garage door is closed. Set the if true to cancel on piston change and only on state change, the last part makes sure it only runs if the door is open.
who’s dumbass? Looolll Did you check the piston schedule while active? It should have the timer count down. That should give you a better understanding.
1 Like
Lol, that’s me! Just edited my post because I realize my phone number was on it. Reason number two I’m a dumbass !
3 Likes
I am trying to get my hue bulbs to match a scene I created in the hue app. I used the HUE api to get the values of the bulb, but it doesn’t look like CoRE supports values this high:
"bri": 13,
"hue": 47126,
"sat": 253,
Hue in CoRE is measured in degrees, but within the hue app it is setting it as some other value…
Any advice on how to set these Values in CoRE?
Has anyone found an effective way to overcome the failed timed events? This is what plagued everyone late last year and now it is coming back. Probably due to SmartThings policy of killing anything that takes too long to execute. The platform, at least for me, is really slowing down. Last night I had to stop converting my RuleMachine apps over to CoRE because of long timeouts.
To me that looks like the weather tile failed in that it took so long. To me it looks like it fired and just took forever. Still could be a platform problem, but not the scheduler.
Just my quick read.
Is your color around blue? Green-blue-indigo? One of these? If so, you may be using a uint 16 bit range, 0-65535 where 65536 would correspond to full circle, 0 or 360 degrees.