I don’t know how long notifications typically get to show up in the app, but there’s a whole chain of events there, each with its possibility of introducing delays, from CoRE getting an event (which I’ve seen delays of minutes sometimes), executing the logic (during which it reads data from the ST database, devices, etc.), sending the command (I’ve seen this taking over 1 second sometimes - one line of code, over 1 second - it does “external” stuff outside of my control), then the notifications service processing the request, your phone “refreshing” in time, and - if using push - push services actually working - my wife was not able to receive Push notifications for some while.
On a different note, the only difference between Basic and Simple is that the Basic does not show an Else statement, nor does it run one (if, for whatever reason, it exists). So - at least in theory - Basic does less. And the code is the exact same. I believe this is typical behavior with ST, I would do the test several times and then draw a conclusion. You’ll find that occasionally, things may get a bit sluggish and then work just fine the next try over…
I’ve a global variable showing that I can’t find anywhere? I did change the name of one I think and the old name still showing. Checked all Pistons I was messing around with but can’t locate, any ideas?
At this time, once a global variable has been created, it cannot be deleted. Dashboard may help in the future, but right now, I am using a persistent store, so the variable… well… persists 
Is there a different way to do this? Id like to get to a deeper understanding with more complex variables and what not:
This works, but I am wanting to learn other ways to do things.
CoRE, from the outside, looks a lot harder and more complex to understand than RM was, but I find it easier to to set up compound actions.
FANTASTIC work @ady624!!
This probably already exist, but since this is the case, where do we view a list of our custom variables?
I saw you talking about it eventually making it to the dashboard, would there be a “view custom variables” area?
I’ll show them under the piston view, where you can see the graphical piston at this time. You can still see the variables in the UI, under each piston, although the ST UI is much slower to deal with.
The Global Variables in the main CoRE page shows a list of all @ variables created.
The Local Variables in the piston page shows a list of all custom variables (no prefix) and the system variables ($ prefix).
Thank you, I think it’s just different and can be as easy as RM if you don’t start tinkering with variables and stuff. It can’t really be easy and extremely powerful at the same time, but we can try to get it there.
Okay, so the news everyone was waiting for: I am getting an Echo. THANK YOU.
No really, that’s not THE news. THIS is the news:
v0.0.06e.20160606 - Alpha test version - Added “Ask Alexa Macro” and “Piston” capabilities. Minor fixes for condition descriptions and event authorization/eligibility.
You’ll need to wait for @MichaelS to publish an Ask Alexa update before you can actually test that “Ask Alexa Macro” capability. I think this will be AWESOME You can trigger pistons by voice. Ouch!
On the “Piston” capability… you can have a piston wait for another piston and execute once that other piston executed. For stability reasons, I have made the “triggered piston” be quiet about it, so if you have piston 1 running, piston 2 trigger on piston 1 having executed, piston 2 won’t send a piston executed event, to avoid some loop conditions. This is not final and may be allowed in a later release, just testing with it for now and trying to not get ST hammered.
Well the thing is, “I” Think its easier than RM, and more powerful too.
Looking forward to its integration with “Ask Alexa”
EDIT: Is it still recommended to enter into the pistons and “Done” them out with every version update?
At the request of a couple of other users I started exploring the use of variables last night.
- i like that the Boolean is included. For anyone using that in RM, you can basically transfer your rules directly to a piston.
- I really like the counting ability of the variables. That is an incredibly powerful tool.
@ady624, the app is amazing. I’m exploring it, but just really waiting for beta before I implement it more. I just have to much to rebuild to risk it in alpha.
Great job
I think the only thing left at this point in time is the “stays” trigger. I may be able to finish those today.
Anything else I’m missing here?
Capture and restore
Most of the times, yes. Just safer. But I don’t think it’s necessary with this update. But yeah, as a general rule, if something doesn’t work after an update, the first thing to do is go to the piston and click Done again. That should fix “most” of the problems.
Forgive my ignorance, is drops functional?
That’s been there for a while now, it’s just that it’s called Save state to local store / Load state from local store. Also the global versions.
Should I rename these to Capture to local store / Restore from local store ?? I think so…
- yes, it makes it easier to find / identify - plus it would be a nice way to remember RM by
- no way, I like Save/Load better
0 voters
Not so much for a way to remember RM, I’m just looking for real world verbiage… Lol… And unfortunately RM managed to grab up a few of those lol.
Fyi, a lot of folks got burned bad by Bruce and what he did… What you’re doing is amazing. You and Michael are changing the landscape of ST to an amazing thing.
Thank you. @MichaelS is a pleasure to work with and VERY willing to go the length. I like that.
Just wish Alexa was available in the UK 
I’m mobile right now but I noticed after the latest update, a piston fired that had no way of being true due to it’s “if” being sunset and its around noon right now.
Ive just changed it to “then” for the action, but this piston has been fine since I created it
Hmmm… keep an eye on that please.