Created my first piston to monitor my garage door and garage heater to pause/resume heating if the door is opened.
Only if the heater is/was on, the heat should pause or resume if the garage door opens or closes. Also send me a PUSH or SMS until debugging is complete.
Doesn’t appear anything is being triggered at all.
@travsav
Hi Travis,
before getting into your piston, I would HIGHLY recommend change the picture. Your phone number is visible (unless you used a fake number) use the green camera icon and always POST that picture… This forum is very safe so no one is going to start trolling you but this post is also open to public…which is the whole world :))))))
I will take a look at the piston later on…
Oops, thank you for that. Updated. I’ve noticed the piston state is showing false as well.
I got it working partially finally… changed my IF statements to “changes to” instead and it’s doing some of the things properly.
Another confusing question… how can i distinguish between a user mode change and the piston changing the mode?
When I open the garage door, I get the PUSH notification that the heat is paused, and the thermostat is changed to off… Then I get a PUSH notification that the heat has been disabled. Not sure why it’d be doing that, I set variable values to prevent it.
1/6/2019, 5:15:56 PM +78ms
+1ms ╔Received event [Garage Thermostat].thermostatMode = off with a delay of 43ms
+8602ms ║RunTime Analysis CS > 15ms > PS > 8550ms > PE > 37ms > CE
+8604ms ║Piston waited at a semaphore for 8518ms
+8607ms ║Runtime (43054 bytes) successfully initialized in 8550ms (v0.3.109.20181207) (8605ms)
+8609ms ║╔Execution stage started
+8624ms ║║Comparison (enum) off changes = true (1ms)
+8627ms ║║Cancelling condition #2’s schedules…
+8628ms ║║Condition #2 evaluated true (9ms)
+8630ms ║║Cancelling condition #1’s schedules…
+8631ms ║║Condition group #1 evaluated true (state changed) (13ms)
+8641ms ║║Comparison (enum) off is (string) heat = false (2ms)
+8643ms ║║Cancelling condition #4’s schedules…
+8644ms ║║Condition #4 evaluated false (10ms)
+8646ms ║║Cancelling condition #3’s schedules…
+8647ms ║║Condition group #3 evaluated false (state changed) (12ms)
+8656ms ║║Comparison (boolean) true is (boolean) true = true (3ms)
+8658ms ║║Cancelling condition #6’s schedules…
+8659ms ║║Condition #6 evaluated true (9ms)
+8666ms ║║Comparison (boolean) false is (boolean) false = true (2ms)
+8668ms ║║Condition #27 evaluated true (7ms)
+8670ms ║║Cancelling condition #5’s schedules…
+8671ms ║║Condition group #5 evaluated true (state changed) (21ms)
+8675ms ║║Cancelling statement #7’s schedules…
+8681ms ║║Executed virtual command setVariable (1ms)
+8700ms ║║Executed virtual command sendPushNotification (13ms)
+8713ms ║║Cancelling condition #14’s schedules…
+8714ms ║║Condition #14 evaluated false (9ms)
+8716ms ║║Cancelling condition #13’s schedules…
+8717ms ║║Condition group #13 evaluated false (state changed) (12ms)
+8728ms ║║Condition #21 evaluated false (6ms)
+8729ms ║║Condition group #20 evaluated false (state did not change) (9ms)
+8733ms ║╚Execution stage complete. (123ms)
+8734ms ╚Event processed successfully (8734ms)
1/6/2019, 5:15:54 PM +589ms
+1ms ╔Received event [Garage Door Sensor].contact = open with a delay of 727ms
+70ms ║RunTime Analysis CS > 15ms > PS > 31ms > PE > 24ms > CE
+73ms ║Runtime (42977 bytes) successfully initialized in 31ms (v0.3.109.20181207) (71ms)
+74ms ║╔Execution stage started
+88ms ║║Cancelling condition #2’s schedules…
+89ms ║║Condition #2 evaluated false (8ms)
+91ms ║║Cancelling condition #1’s schedules…
+92ms ║║Condition group #1 evaluated false (state changed) (12ms)
+101ms ║║Comparison (enum) open changes_to (string) open = true (1ms)
+103ms ║║Cancelling condition #14’s schedules…
+104ms ║║Condition #14 evaluated true (8ms)
+113ms ║║Comparison (enum) heat is (string) heat = true (2ms)
+115ms ║║Cancelling condition #15’s schedules…
+116ms ║║Condition #15 evaluated true (11ms)
+118ms ║║Cancelling condition #13’s schedules…
+119ms ║║Condition group #13 evaluated true (state changed) (24ms)
+122ms ║║Cancelling statement #18’s schedules…
+143ms ║║Executed virtual command sendPushNotification (14ms)
+149ms ║║Executed virtual command setVariable (1ms)
+153ms ║║Cancelling statement #16’s schedules…
+1522ms ║║Executed physical command [Garage Thermostat].off() (1365ms)
+1523ms ║║Executed [Garage Thermostat].off (1367ms)
+1532ms ║║Comparison (enum) open changes_to (string) closed = false (1ms)
+1534ms ║║Condition #21 evaluated false (7ms)
+1536ms ║║Condition group #20 evaluated false (state did not change) (8ms)
+1539ms ║╚Execution stage complete. (1465ms)
+1540ms ╚Event processed successfully (1540ms)
1/6/2019, 5:13:53 PM +132ms
+2ms ╔Received event [Garage Thermostat].thermostatMode = heat with a delay of 61ms
+105ms ║RunTime Analysis CS > 24ms > PS > 55ms > PE > 26ms > CE
+108ms ║Runtime (42986 bytes) successfully initialized in 55ms (v0.3.109.20181207) (105ms)
+109ms ║╔Execution stage started
+118ms ║║Comparison (enum) heat changes = true (1ms)
+120ms ║║Condition #2 evaluated true (5ms)
+121ms ║║Condition group #1 evaluated true (state did not change) (7ms)
+129ms ║║Comparison (enum) heat is (string) heat = true (2ms)
+131ms ║║Cancelling condition #4’s schedules…
+132ms ║║Condition #4 evaluated true (8ms)
+138ms ║║Comparison (boolean) false is (boolean) false = true (2ms)
+140ms ║║Condition #31 evaluated true (7ms)
+142ms ║║Cancelling condition #3’s schedules…
+143ms ║║Condition group #3 evaluated true (state changed) (19ms)
+146ms ║║Cancelling statement #10’s schedules…
+151ms ║║Executed virtual command setVariable (1ms)
+172ms ║║Executed virtual command sendPushNotification (15ms)
+185ms ║║Condition #14 evaluated false (9ms)
+186ms ║║Condition group #13 evaluated false (state did not change) (10ms)
+197ms ║║Condition #21 evaluated false (6ms)
+198ms ║║Condition group #20 evaluated false (state did not change) (9ms)
+201ms ║╚Execution stage complete. (92ms)
+202ms ╚Event processed successfully (202ms)
Hmm… someone must be trying out the first image i posted… I’m getting SMS alerts of their heat being enabled and disabled. lol…
I changed it to PUSH.
LOL that’s funny 
I should’ve written the number down…
“smart home alert… self destruction starts in…10…9…8…”
