Piston not running?


#1

This piston is supposed be be an easy set mode based on time of day and presence. If I “test” it… or execute it the mode is set properly. Other wise it does nothing. What am I missing?

As you can see in the logs “dawn” did not run… nor Morning… nor day as it is presently 8:13 AM.

12/20/2017, 10:51:22 PM +111ms
+1ms ╔Received event [Sleeping].switch = off with a delay of 91ms
+1069ms ╚Event processed successfully (1069ms)
12/20/2017, 10:51:21 PM +782ms
+1ms ╔Received event [Home].time = 1513828282637 with a delay of -855ms
+268ms ╚Event processed successfully (268ms)
12/20/2017, 10:51:17 PM +306ms
+1ms ╔Received event [Sleeping].switch = on with a delay of 90ms
+336ms ║Setting up scheduled job for Wed, Dec 20 2017 @ 10:51:22 PM EST (in 4.996s)
+344ms ╚Event processed successfully (343ms)
12/20/2017, 10:46:28 PM +867ms
+1ms ╔Received event [Home].test = 1513827988864 with a delay of 3ms
+1071ms ╚Event processed successfully (1071ms)
12/20/2017, 10:22:40 PM +918ms
+1ms ╔Starting piston… (v0.2.100.20171211)
+404ms ║Subscribing to Sleeping.switch…
+729ms ╚Piston successfully started (729ms)Logs


#2

I see you have a ‘minus’ next to all of your ‘presence sensor IFS’ .
I believe this means that your IFS are not subscribed and will therefore be ignored. The IF will not be evaluated and therefore cannot do anything.
Try it with auto subscribe.


#3

Hi Bobbles! Thanks for the reply. I’m not seeing a minus? But I might be crosseyed at this point from trying to figure it out… what line number are you seeing a minus?


#4

ohhh I see! How’d that sneaky little booger get there!! Argh!! Thanks so much!


#5

Actually Bobbles… that didn’t fix it… her is an updated copy.


#6

Enable tracing and then push the test button.
Do any of the IFS for time is between turn green.
The one for the current time should.


#7

I imported your piston amended it for testing and it does work for me.


#8

Is there something I could be missing? Do I need to enable it someplace? Turn it on or something?


#9

When you create a piston, as soon as you save it, it becomes active. There is a button at the top which allows you to pause it. Have you paused it by mistake.
When you hit test, does one of the time ‘IFS’ turn green.
As I said above the piston works for me OK.


#10

Weird!

Its not paused.

Interesting… I noticed I dont have a trace button…

image


#11

Before I hit test

Logs
12/21/2017, 11:24:10 AM +436ms
+0ms ╔Starting piston… (v0.2.100.20171211)
+395ms ║Subscribing to Sleeping.switch…
+726ms ╚Piston successfully started (725ms)
12/21/2017, 10:45:07 AM +571ms
+0ms ╔Starting piston… (v0.2.100.20171211)
+530ms ║Subscribing to Sleeping.switch…
+902ms ╚Piston successfully started (902ms)
12/21/2017, 10:28:19 AM +897ms
+1ms ╔Starting piston… (v0.2.100.20171211)
+608ms ║Subscribing to Sleeping.switch…
+1002ms ╚Piston successfully started (1001ms)

image

after I hit test - it ran… mode changed and I got email


image

Logs
12/21/2017, 11:31:00 AM +305ms
+1ms ╔Received event [Home].test = 1513873860305 with a delay of 0ms
+1876ms ╚Event processed successfully (1876ms)
12/21/2017, 11:24:10 AM +436ms
+0ms ╔Starting piston… (v0.2.100.20171211)
+395ms ║Subscribing to Sleeping.switch…
+726ms ╚Piston successfully started (725ms)
12/21/2017, 10:45:07 AM +571ms
+0ms ╔Starting piston… (v0.2.100.20171211)
+530ms ║Subscribing to Sleeping.switch…
+902ms ╚Piston successfully started (902ms)
12/21/2017, 10:28:19 AM +897ms
+1ms ╔Starting piston… (v0.2.100.20171211)
+608ms ║Subscribing to Sleeping.switch…
+1002ms ╚Piston successfully started (1001ms)


#12

The trace button doesn’t appear until the piston has run. I imported your piston and put my devices into it. I pushed test and I got a notification and the trace button then appears. I’m not sure if you need to enable something somewhere to get the trace button. It’s been a while since I first started using this.


#13

So if you import it… edit the last IF (its there for testing) to be 5 minutes in the future… save, test ( it will run)… does it run again in 5?


#14

Well this is strange. It’s stopped working.
Earlier I changed the time for the day part to be in a current time range and it ran.
Changed the time for day again and it doesn’t run.
Also the test day isn’t working.
Will have to play.
Also with logging on full nothing is appearing in the logs when test is pressed.

EDIT : I had left it paused. :smile:


#15

OK. Tested again and got the notification when test button hit for the current time.
Set the day test to 5 min ahead and got that OK.
I’m using push notification not email.


#16

This is gonna drive me crazy… I deleted the piston and reimported it… I get the same results… it only runs when I click test.


#17

I only see one subscription (switch 14) and nothing else is going to trigger the time blocks except when the start time comes? (sorry, just jumping into this)


#18

Im new enough to WC that Im not following about the subscription… but it sounds like you are own to something… What do you mean?


#19

Sorry, just got into this and I’m also trying to import the piston… on a tiny screen


#20

OK. What I had done in all my testing to get this to work was changing things to always subscribe. (Sorry for the late reply but it’s early evening in the UK).
You can see this by the + next to the statements.
You can either import this or just change yours.
If you remember earlier you changed yours from never subscribe to automatic. Change again to always.