Piston only completing one part of task


(UltraVegas) #1

Having an issue I can’t seem to figure out.

I have piston set to set the levels of 3 lights when a contact opens. First it well set the level to 100% and then it’s supposed to wait 30 minutes then set the to 50% and then wait another 15 minutes and set the level to 10%.

When the contact opens it will set the level to 100% and schedule the timer but when the timer runs down it doesn’t do the set level 50%?

What am I missing? I had this set-up on another set-up but had to start fresh again and now it’s not working correctly…!

download|690x329

Here is the most recent log:

Logs
8/7/2018, 1:17:48 PM +57ms
+1ms ╔Received event [Home].time = 1533673069743 with a delay of -1687ms
+159ms ║RunTime Analysis CS > 38ms > PS > 60ms > PE > 61ms > CE
+161ms ║Runtime (38244 bytes) successfully initialized in 60ms (v0.3.106.20180731) (159ms)
+162ms ║╔Execution stage started
+163ms ║╚Execution stage complete. (1ms)
+164ms ╚Event processed successfully (164ms)

8/7/2018, 12:47:53 PM +210ms
+1ms ╔Received event [Front Door].contact = closed with a delay of 361ms
+140ms ║RunTime Analysis CS > 24ms > PS > 68ms > PE > 48ms > CE
+142ms ║Runtime (38237 bytes) successfully initialized in 68ms (v0.3.106.20180731) (140ms)
+143ms ║╔Execution stage started
+152ms ║║Comparison (string) :fcbe69a89a7885db0af0df65673d7500: is_any_of (string) :4cfad1470a3a40f39be1cdd774879ec1:,:fcbe69a89a7885db0af0df65673d7500: = true (2ms)
+153ms ║║Condition #9 evaluated true (5ms)
+154ms ║║Condition group #1 evaluated true (state did not change) (6ms)
+158ms ║║Comparison (enum) closed changes_to (string) open = false (0ms)
+159ms ║║Cancelling condition #8’s schedules…
+160ms ║║Condition #8 evaluated false (4ms)
+160ms ║║Cancelling condition #1’s schedules…
+161ms ║║Condition group #1 evaluated false (state changed) (7ms)
+163ms ║╚Execution stage complete. (21ms)
+164ms ╚Event processed successfully (165ms)


(Bob) #2

Can you post the green anonymised snapshot. Your link doesn’t work for me.


(UltraVegas) #3


(UltraVegas) #4

Don’t know why it didn’t post the first time… sorry


(Bob) #5

In your WITH set TCP to ‘Never’.
When you do this you will see a small red ‘N’ next to it.


(UltraVegas) #6

Okay I will try that. Thanks.


(Bob) #7

The default is ‘Cancel Tasks on Condition state change’.
This means that after around 10 seconds the ‘Changes to Active’ becomes false and all tasks will now be cancelled.
With TCP set to never the tasks will not cancel and continue to run when the condition changes to false.
Hope that all makes sense. :wink:


(UltraVegas) #8

I will wait until it runs again to see if it works again as I am away right now.

I don’t remember ever having to do that, is it something new? It’s been quite a few months since I had messed with anything in Webcore… then Samsung migrated my account and screwed it all up so I started out fresh again. … my system needed a bit of TLC anyway :unamused::wink:


(Bob) #9

No. This is something that has been there from the start. Perhaps you copied someone elses’ rule.
Just for information there is a dedicated webCoRE forum that you might want to look at in future. Here it is.


( Cosmo) #10

thanks @bobbles


(UltraVegas) #11

Thanks @bobbles that did the trick! I just signed up on the Webcore forums too :wink: