@ady624 is the Energizer Code Slinger !!! keeps going, and going… amazing work guy !
custom made for Adrian
5 Likes
I was trying to see if you can send a push notification upon execution of piston.
Yes, either have that piston send the push, or have another piston with a Piston capability condition do it.
I’m not sure where the option is for push?
Any action, either device or location, tap on Add task and them scroll down to find Send push notification. When controlling devices, the device specific commands are listed first. Then virtual commands follow (non device-implemented commands) with full circles. You have a lot of options in there, push, sms, notification (shows up in the ST app), contacts, erc
Argh! That Mambo No. 5 always gets me! I keep searching for the piston I just created and I cannot find it! This is the third time 
1 Like
Are you the first who finds that mambo easter egg?
LOL I dunno, first time I posted about it but this is the third time you had me looking for a piston! 
I’m playing with Switch/Case and this test seems pretty simple, I press button 1 but I get the button 3 push.
End Switch is missing?
omg that was too easy
Does it work now?
I’m getting a double push.
Edit: Only getting doubles on 1 and 2, 3 and 4 works. Pushing 1 gives me 1 and 3, pushing 2 gives me 2 and 4.
`
df95b183-8289-43be-9754-eaa4a9cacf6b 6:43:53 PM: trace ╔═══ Task processing took 2898ms
df95b183-8289-43be-9754-eaa4a9cacf6b 6:43:53 PM: trace ║░░░ Removing any existing ST safety nets
df95b183-8289-43be-9754-eaa4a9cacf6b 6:43:53 PM: info ║░░░ Executing virtual command sendPushNotification (384ms)
df95b183-8289-43be-9754-eaa4a9cacf6b 6:43:52 PM: info ║░░░ Executing virtual command sendPushNotification (1249ms)
df95b183-8289-43be-9754-eaa4a9cacf6b 6:43:50 PM: trace ║░░░ Installing ST safety net
df95b183-8289-43be-9754-eaa4a9cacf6b 6:43:50 PM: trace ║░░░ Rescheduling time triggers
df95b183-8289-43be-9754-eaa4a9cacf6b 6:43:50 PM: trace ╚═══ Processing tasks (v0.2.140.20160817)
df95b183-8289-43be-9754-eaa4a9cacf6b 6:43:50 PM: trace ╔═══ Event processing took 681ms
df95b183-8289-43be-9754-eaa4a9cacf6b 6:43:50 PM: trace ╚═══ Processing event button for device Oenz Minimote with id d31f7f2b-0902-4cbf-9274-e9423cade004, value pushed, generated on Sat Aug 20 01:43:49 UTC 2016, about 1056ms ago (v0.2.140.20160817)
df95b183-8289-43be-9754-eaa4a9cacf6b 6:46:26 PM: debug ╔═══ Done in 1322ms
df95b183-8289-43be-9754-eaa4a9cacf6b 6:46:26 PM: info ║░░░ Executing virtual command sendPushNotification (190ms)
df95b183-8289-43be-9754-eaa4a9cacf6b 6:46:26 PM: debug ║░░░ Processing command task [taskId:7, time:1471657585745, idx:2, created:1471657586195, marker:1471657586227, ownerId:1, data:[p:[[d:Button 3, t:text, i:0], [d:false, t:bool, i:1]]], type:cmd]
df95b183-8289-43be-9754-eaa4a9cacf6b 6:46:26 PM: info ║░░░ Executing virtual command sendPushNotification (306ms)
df95b183-8289-43be-9754-eaa4a9cacf6b 6:46:26 PM: debug ║░░░ Processing command task [taskId:3, time:1471657585745, idx:1, marker:1471657586227, created:1471657586136, ownerId:1, data:[p:[[d:Buttton 1, t:text, i:0], [d:false, t:bool, i:1]]], type:cmd]
df95b183-8289-43be-9754-eaa4a9cacf6b 6:46:26 PM: debug ║░░░ Found 2 tasks due at this time
df95b183-8289-43be-9754-eaa4a9cacf6b 6:46:25 PM: debug ║░░░ Primary IF block evaluation result is true
df95b183-8289-43be-9754-eaa4a9cacf6b 6:46:25 PM: debug ║░░░ ♣ Function eval_cond_is for Oenz Minimote's button [pushed] is 'pushed' returned true
df95b183-8289-43be-9754-eaa4a9cacf6b 6:46:25 PM: debug ║░░░ Event eligibility for the primary IF block is 1 - ELIGIBLE (triggers not required, event is a condition)
df95b183-8289-43be-9754-eaa4a9cacf6b 6:46:25 PM: debug ╚═══ Received a primary block device eventCan u please check events for the minimote? Any doubles there? I only have a virtual minimote and gotta say, it works flawlessly. Except it’s virtual, that’s all 
I did check that earlier to see if it was a hardware issue. Could this be related to the fix for the random case?
2016-08-19 7:00:36.426 PM MST
35 minutes ago DEVICE button pushed Oenz Minimote button 1 was pushed
2016-08-19 7:00:12.395 PM MST
36 minutes ago DEVICE button pushed Oenz Minimote button 2 was pushed
2016-08-19 6:59:37.862 PM MST
36 minutes ago DEVICE button pushed Oenz Minimote button 3 was pushed
2016-08-19 6:59:05.839 PM MST
37 minutes ago DEVICE button pushed Oenz Minimote button 4 was pushedI will try it with another minimote.
Edit: Same behavior on a different minimote.
Yeah I can replicate it. Will issue a fix, thank you for finding a bug
Do the letters and colors in the experimental theme mean anything? If so, what?
The letter represents the type of piston (piston mode)
Blue means its state is currently true, red is false.
In piston view, blue and red show the state the last time the piston was evaluated. It does not reflect the current state of each condition or device.
@eibyer I don’t know why, but mine works after upgrading to v0.2.141.20160820 - Beta M2 - Fixed a problem with SWITCH-CASE which would, upon the end of a matching case, send the flow to the second following case’s start, executing two cases
Maybe your minimotes are junk?! bwahahahahahahahahahahahahahahaha argh argh argh cough cough cough cough (vile laugh followed by coughing) … (after a while) … cough cough cough…
3 Likes