CoRE and Piston Rules Engine, first design steps

[r4nd0m]

Didnt monitor this afternoon and I am mow able to see the scheduler timers associated with the invoking statement - all I have asked for. Awesome - blown away - donated cheers!!! Keep the good stuff coming.

[ady624 (I hate Mondays)]

After posting this in the wrong thread, here goes:

Okay, here’s the BIG news. v0.0.061.20160602 - Alpha test version - Minor bug fixes. Introducing the Follow-Up piston. Chain them together, delay them forever, do whatever you need with them

Follow-Up pistons are just like the Simple pistons. The only differences are:

• does not support triggers
• does not subscribe to anything

They can be initiated from other pistons via the Follow up with piston task. This task can be delayed just like any other using the Wait task in front of it, so you can technically say "IF (this) Then (that) Else (wait 5 min, follow up with piston).

Even better, you can follow up with the piston over and over… the follow up piston can follow up with another piston, even itself. Combine that with a global variable counter and you can have a complex solution where something initiates the counter, does things and follows up with a piston that can follow up with itself x times until either your expectations are met, or the counter hits 0, hence giving up… I guess, unlimited possibilities Enjoy.

[ady624 (I hate Mondays)]

Thank you

[Kevin_Prefer (Kevin)]

Where would one donate? I’d love to show my appreciation…

[Turb02 (Kavvy)]

@Kevin_Prefer

@ady624

After being asked by I don’t know, 10 people?!?, I added it to the other thread.

[OBSOLETE] [BETA MILESTONE 1] CoRE (Community's own Rules Engine)

UPDATE 8/12/2016: CoRE has moved on to Beta Milestone 2. Please kindly follow us here. In an attempt to fill the huge void left by the withdrawal of Rule Machine, a few brave community members started their journey to creating a new rule engine to rule them all. We’ve decided to call it CoRE, an abbreviation that stands for “Community’s own Rule Engine”, courtesy of @SBDOBRESCU (his idea, really). WARNING: This SmartApp is in an alpha BETA development stage and may be quirky. It may also change rapidly and drastically, involving a full reset of the app in order to upgrade. It is not recommend to install this SmartApp in a “production” environment, but we encourage people to try it out. IMPORTANT: This topic is here for general information and peer assistance. If you want to point out e…

When I get to my phone, Ill be donating too!

[krlaframboise (Kevin)]

Thanks for adding the dashboard, it works great.

Do you think at some point you might be able to add a formatting option for variables?

Examples:
{someDate:MM/dd/yyyy}
{someDecimal:#}
{anotherDecimal:#,##0.00}

[ady624 (I hate Mondays)]

LOL - I’d have to invent God Mode for that… way beyond expert

UPDATE: I should call this the my-momma-is-an-expert-and-I’m-better-than-her mode.

[ady624 (I hate Mondays)]

@ryan.ray

I might do that but I’m really just playing around at this point. At the pace you are going you will probably have the functionality done. My end goal is to be able to fire 1 piston from another.

Bam! Done. Use v0.0.061 LOL - I am so happy I decided to go with hexadecimal, or else I’d be running out of numbers 000-999… LOL Chrome and Firefox are eating dust…

[chickwebb]

@chickwebb

When I edit a piston, and tap Done, I end up not on the “main” CoRE page, but back at the list of smartapps page. In order to go back in and edit/create another piston, I am forced to tap on the CoRE icon there. It’s a bit annoying. I’m on Android. Am I the only one who’s seeing this behavior?

Follow up to this. When I create a new piston and hit “Done”, it goes back to the CoRE “home” page and not to the SmartApps page. And eventually the new piston shows up in the list, so that appears to function as expected. It’s only when you tap “Done” on an existing piston that it skips back over the “home” page to the SmartApps page.

[Drewbert34 (Fast, Good, Cheap...pick two.)]

@ady624

@ryan.ray

I might do that but I’m really just playing around at this point. At the pace you are going you will probably have the functionality done. My end goal is to be able to fire 1 piston from another.

Bam! Done. Use v0.0.061 LOL - I am so happy I decided to go with hexadecimal, or else I’d be running out of numbers 000-999… LOL Chrome and Firefox are eating dust…

I gave this a shot and received “You cannot currently add this” I believe it was.

[ady624 (I hate Mondays)]

What can’t you add? Hold on, making some changes to the follow up. Will allow any piston, ask for delay, and possibility to return resulting piston state to a variable. Also adding Execute piston which would not have the delay. Also, follow-up pistons should not schedule time events. It does as of now, bug.

[CAL7 (Charles)]

[quote=“chickwebb, post:2487, topic:46546”]
When I create a new piston and hit “Done”, it goes back to the CoRE “home” page and not to the SmartApps page.
[/quote]Just to add my $.02… I am certain this was new behavior, beginning roughly 7-10 days ago.

[ady624 (I hate Mondays)]

I’ll look into it. Got an Android tablet that acts like that.

Meanwhile, updated the Follow Up to have a delay and a variable too. So if anyone used that, please revisit that task.

Also added Execute piston (which does an immediate execution on the piston and can return the new state)

v0.0.062.20160602 - Alpha test version - Updated Follow Up and added Execute. Not fully tested yet.

[dshokouhi]

Hey guys what would be the best way to create a piston that will wait for my lock to be unlocked for at least 5 minutes before triggering any actions?

[ady624 (I hate Mondays)]

You can start with a condition…
If lock is locked then
Using devices
Wait 5 minutes
Do stuff
Cancel on piston state change

[ryan.ray]

Thanks for the quick fix. Looks good on my end. But my end goal of triggering on global variables may not be necessary with the new “Follow-up” pistons. I’m still playing around with those.

[dshokouhi]

@ady624

Cancel on piston state change

Thank you @ady624 I knew I was missing something!

[Drewbert34 (Fast, Good, Cheap...pick two.)]

@ady624

What can’t you add? Hold on, making some changes to the follow up. Will allow any piston, ask for delay, and possibility to return resulting piston state to a variable. Also adding Execute piston which would not have the delay. Also, follow-up pistons should not schedule time events. It does as of now, bug.

This:

[ady624 (I hate Mondays)]

You need to update the code. And it’s probably saying that because it was (at first) only allowing Follow-Up pistons and you haven’t yet created any. The latest version allows you to “execute” any piston. Execute is immediate, whereas Follow Up allows for a time delay (built-in wait). Also, the “Follow-Up” pistons never run on their own, only when executed by other pistons.

[Drewbert34 (Fast, Good, Cheap...pick two.)]

@ady624

You need to update the code. And it’s probably saying that because it was (at first) only allowing Follow-Up pistons and you haven’t yet created any. The latest version allows you to “execute” any piston. Execute is immediate, whereas Follow Up allows for a time delay (built-in wait). Also, the “Follow-Up” pistons never run on their own, only when executed by other pistons.

Gotcha!

So, if the follow up piston does not need to function seperately (other than to have seperate on / off selectability) than is it safe to say it no longer needs it’s own trigger?..only that of the lead app?

Hope that made sense.