Trial and error is good, as long as you’re not my doctor 
It imports the data to the variables.
Do you think you could supply a capture of your variables so I can see what yours looks like? Most of mine show (empty)
It will populate once the subscribed events happen.
I agree. There should be more info… but finding the time is almost impossible… I’ve been working on a project for a month that is taking up all of my time… I’m hoping to have that done in a couple of days…
In my spare time in trying to put together some stuff for CoRE… but I can’t find any spare time…
When you refresh the device it will populate most of them.
They would be in the local variables - you cannot set system ($) variables - you get to control the prefix if you want, and you can add an @ to make the global.
Hmm! I tried this also but I don’t see anything that I don’t see on the dashboard variables.
OK guys, I have a piston that says something when someone gets home through my sonos speakers. I am using the Speak Text and Resume so that if music is playing it will resume. However, it didn’t resume. And when I pressed play it played the text sentence again. Any ideas?
Kill it with fire?
Hi guys,
Is there a way to run the tasks of a piston manually?
Thanks.
Yes.
Open your app to the piston you want to activate.
Scroll down that page until you see “Simulate” (allows you to test the actions manually).
Tap “Simulate” and the piston actions should fire.
Thank you for your response.
When I tapped it, it said:
“Preparing to simulate piston…
Current piston state is: false
Simulation ended in 141ms
New piston state is: false
…
Commands executed
No commands have been executed.
…”
And none of my tasks were performed
You’re now talking above my pay grade, but undoubtedly someone will chime in. Quite the intelligent, helpful and friendly bunch around here.
Before answering your question, I tested my response in CoRE. Everything fired as should have, so something else is amiss. The group often asks for a screen shot of your piston as a way of diagnosing the issue.
Terribly sorry I can’t help you more. I’m pretty new to all of this.
Here’s what you do…
Create a virtual toggle switch.
In the piston have this as one of your triggers…
IF
Using the virtual toggle switch
> changes to on
THEN
Run your piston.
Now, go into your ST routines tab.
Create a routine that only turns on the virtual toggle switch (I say use the toggle that way you only have to turn it on… it automatically goes back to off)
Now, on your phone activate your widgets.
When you want to run the piston manually, just open your phone… go to the widgets… and press the routine you created above.
Boom! Your piston runs.
Thanks anyway.
Thank you. That makes sense.
I wish CORE worked a bit like the ST routines though. The piston run manually when we tap it, or run automatically when the triggers or conditions meet.
By the way, I have a piston that do certain tasks when my wife’s phone changes to PRESENT. It never runs, and it is very hard to test because I have to take her phone with me and drive out of the house far enough and come back home. If you have a better way to test, please let me know.
I have thought about using a simulated presence sensor. But if I used my phone’s presence instead of hers in the condition part, the piston fired, but when I changed back to her phone, it stopped firing. If you were me, how would you debug that?
Thanks.
The first thing I would do is create a virtual presence sensor and add that to the piston as a second trigger. Use or between the two. Then turn it off and on and see what happens.
Then, I would delete and rebuild the piston from scratch.
Then, I don’t know… are you using the stock ST presence on the phone? Or a 3rd party app like life360?
I use the stock ST presence. I have another piston that also uses her phone’s presence as a condition, and that one works fine.