OK, @eibyer, thanks for the info/suggestions. I think of got it, and would appreciate your feedback whether it looks OK.
I’ve been doing so much testing that I’m out of dirty laundry, so I can’t do a real test right now. 
All three then statements will run in tandem. You want to “add action” after the first and keep doing that till done. Like this:
Ah, thanks @michaelahess, didn’t realize they all had to be combined. Back to the CoRE salt mines…
You can combine both, say have a light flash when triggered to show a load started, and start the timer, then have the light flash and maybe a tts event after the timer along with the sent message.
That sounds interesting, I’ll have to look into souping thing things up later.
So now I have the basic piston right, I hope.
And now I know that if I create separate groups of actions (as in my fist try) they all will run in parallel…did not understand that before.
Looks good. That button pushed trigger a virtual button or something triggered by the HEM power level? I haven’t been keeping up with this thread too well.
So essentially have a virtual switch for each activity and add the switches to on in the harmony app.
It’s an HEM DTH that @Mike_Maxwell developed that turns the HEM into two buttons, which are Pushed (=on) when a certain minimum watts setting is reached, and Held (=off) when it goes below that value.
It reads both clamps separately, so you have two buttons, one for each clamp. I have one HEM on my washer/dryer via this method.
So you can use the HEM as if it’s a two button device with either of two states for each button.
Pretty cool…
1 Like
Yes, they are setup when you link the harmony app to ST via Logitech Harmony (connect) app. They are active switches with status reporting from harmony, the ONLY reason to add the switch into the harmony activity is to speed up reporting back to ST, particularly if you want ST automations triggered off harmony activities (i.e. I have tv LED backlighting that adjusts brightness based upon TV status / time of day)
I take no credit in figuring this out, see below thread:
1 Like
Hi all, i’m pretty newbie with ST and With core also.
I just made some easy pistons with good results, but i miss a feature…
I like to know if it is possible to force the state of mobile presence, I like to create a button that change manually the presence state of a mobile phone. Because many time is stuck.
What i want to create is a sort of reset button without remove and add again the device from the list.
All the helps is appreciated.
Thanks a lot
L
No that isn’t possible. The ST presence of a phone is set in ST and has no switch capabilities.
Now what you can do is create a virtual switch and use that as your presence. Just create some logic to have your actual phone presence drive it but it still gives you the option to flip it.
In fact this is what I do. I use a more complex piston (uses my phone, life 360, iFTTT and also a motion sensor) based on @JDRoberts ideas. I also use @Mike_Maxwell’s uDHT so the virtual switch has presence properties to use in the pistons or even ST itself.
that work if you handle by yourself the system, but it is not possible for me stress my wife installing and manage apps on her cell phone.
Sometimes is happening that some device’s status looks stuck. When it happebd to me i do something e.g. reboot, open close ST app…
But i cannot ask to my wife and son.
Thats’ why i want to set them status manually if i get them stuck.
You wouldn’t have to have them manage anything. I too have a daughter and wife whom I don’t want to have to mess with stuff. I have installed Life 360 on their phones and then they never have to touch that. Same with iFTTT. It takes a total of 10 minutes.
And the virtual sensors in ST are not anything the need to do. For me, that “sensor” is toggle based on CoRE rules that run automagically. My family never needs to intervene and I can manually manage them from the ST app on my phone if ever needed.
However if you only want to use the ST phone presence you are stuck with not being able to manually update that and ST presence on phones is a known issue for being flaky.
Can someone explain why this piston may not be working as I’m not sure why it stopped working. Originally the piston only contained the first 2 conditions and everything worked fine. I added the second to last trigger condition a few days ago and every since this piston has not been working. It was a separate piston, but I was trying to combine it in a single piston. I’m guessing it has something to do with the trigger, but I’m not sure why. The last condition was added today while testing and it does not work either.
Hi all, in my endless quest to continue learning how to use this great app…could somebody give me some clues as to why this piston is not doing anything.
I’d at least expect it to change the mode from NIGHT to HOME, when the hub is in NIGHT mode and the button is pressed, irrespective of time of day, but it does nothing.
Thanks!
Never mind found it.
Mixing triggers with conditions will cause the triggers to become the sole subscribers to events, all conditions become “prerequisites” or “restrictions” to the triggers. Either you convert all important conditions (those that can trigger changes) to triggers, or you do away with the trigger (if you can use a condition instead). You could make the time trigger “time is after 4:50”
1 Like
Did you actually push a button #4 on the Minimote or change the Routine? According to that screen cap you didn’t. Both of those conditions are red, meaning false.
Thanks @ady624. I changed it to a condition and everything works.
1 Like
No harm asking the obvious I guess 
I didn’t run the routine, but I did push the button (and the IDE log shows the button as pushed)
However, having now tried running the routine, I see that the routine triggers the events…but he button push does not