Piston is skipping 2 steps in the middle - Solved

[Cael]

1) Give a description of the problem
I have a piston to start my Eight mattress to warm the bed and its half working, but skipping some steps in the middle.

2) What is the expected behavior?
It should turn on the mattress to level 5 during certain conditions (working)
It should then wait until 10:59 (working)
It should then set level to 3 (not working)
It should then wait until 3:00 (not working)
It should turn off (working, but at wrong time)

3) What is happening/not happening?
It is skipping 2 steps in the middle and just shutting off at 10:59 pm.

**4) Post a Green Snapshot of the piston!

5) Attach any logs (From ST IDE and by turning logging level to Full)
10/15/2017, 7:54:59 PM +158ms +1ms ╔Received event [Home].time = 1508118900000 with a delay of -843ms +240ms ║RunTime Analysis CS > 27ms > PS > 143ms > PE > 70ms > CE +252ms ║Runtime (38616 bytes) successfully initialized in 143ms (v0.2.0fa.20171011) (250ms) +253ms ║╔Execution stage started +273ms ║║Comparison (enum) present is (string) present = true (2ms) +274ms ║║Condition #9 evaluated true (12ms) +287ms ║║Comparison (time) 71699434 is_between (time) 71700000 .. (time) 73800000 = true (8ms) +288ms ║║Time restriction check passed +290ms ║║Cancelling condition #10's schedules... +291ms ║║Condition #10 evaluated true (16ms) +292ms ║║Cancelling statement #10's schedules... +297ms ║║Requesting time schedule wake up at Sun, Oct 15 2017 @ 8:30:00 PM MDT +301ms ║║Cancelling condition #1's schedules... +302ms ║║Condition group #1 evaluated true (state changed) (41ms) +305ms ║║Cancelling statement #2's schedules... +1416ms ║║Executed physical command [Eight Sleep Jackie].setLevel([50]) (1103ms) +1419ms ║║Executed [Eight Sleep Jackie].setLevel (1107ms) +1443ms ║║Executed virtual command [Eight Sleep Jackie].waitForTime (18ms) +1445ms ║║Requesting a wake up for Sun, Oct 15 2017 @ 10:59:00 PM MDT (in 11039.401s) +1453ms ║╚Execution stage complete. (1200ms) +1456ms ║Setting up scheduled job for Sun, Oct 15 2017 @ 8:30:00 PM MDT (in 2099.387s), with 1 more job pending +1740ms ╚Event processed successfully (1739ms)

Thanks!

Turns out it was an error with the Device Handler and not the piston. When that was upgraded, the piston worked correctly.

[Eric182]

Is not doing those actions because 10:59 PM and 3 AM are not between 7:55 PM and 8 PM. Try clicking the with and change the TCP to never cancel tasks

[Cael]

I will give that a try. But it is doing something at 10:59. Its just not doing the right thing. Its supposed to change the level and then wait again. But instead, its skipping the level change and going right to the last step of turn Off.

I’ve made this change and will see what happens tonight. Thanks

[Cael]

Is not doing those actions because 10:59 PM and 3 AM are not between 7:55 PM and 8 PM. Try clicking the with and change the TCP to never cancel tasks

I will give that a try. But it is doing something at 10:59. Its just not doing the right thing. Its supposed to change the level and then wait again. But instead, its skipping the level change and going right to the last step of turn Off.

So I gave it a try and no effect. It still recognizes the event needed at 10:59, but jumps 2 steps and shuts it off. So any other thoughts would be great.