Garage door not closing at sunset

#1

Im still having trouble with my piston closing the door at sunset if the contact sensor is open.
I have added the second or
Time happens daily at sunset
and
Garage door sensors contact is open
That should take care of closing the door at sunset

Today the garage door was opened late afternoon when the time pasted sunset I don’t understand y the door didn’t close
The piston states
Garage door sensor contact stays open for 10 min
and
Time is not between sunrise and 10 min to sunset
Any pointers

image
image.png1178×745 31.4 KB

.

#2

Did you logs give you any clue as to what is happening?

#3

At 7:36 should there not have being a schedule to start the piston at sunset around 8:22(sunset) as the door was open. Even log for 8:52 why is the schedule for the next day when the garage door sensor is open at the time

4/30/2020, 8:52:11 PM +262ms
+2ms ╔Starting piston… (v0.3.10a.20190223)
+298ms ║╔Subscribing to devices…
+379ms ║║Subscribing to Garage Door Sensor.contact…
+547ms ║║Subscribing to Garage Door…
+548ms ║╚Finished subscribing (262ms)
+583ms ║Comparison (enum) open stays (string) open = true (2ms)
+634ms ║Comparison (time) 75131847 is_not_between (time) 1588241700000 … (time) 1588292460000 = true (14ms)
+636ms ║Time restriction check passed
+638ms ║Cancelling condition #9’s schedules…
+639ms ║Cancelling condition #8’s schedules…
+644ms ║Comparison (time) 75131903 happens_daily_at (time) 1588292460000 = false (1ms)
+654ms ║Cancelling statement #12’s schedules…
+661ms ║Requesting time schedule wake up at Fri, May 1 2020 @ 8:21:00 PM EDT
+678ms ║Comparison (enum) open is (string) open = true (1ms)
+680ms ║Cancelling condition #13’s schedules…
+681ms ║Cancelling condition #1’s schedules…
+730ms ║Setting up scheduled job for Fri, May 1 2020 @ 8:21:00 PM EDT (in 84528.009s)
+741ms ╚Piston successfully started (740ms)

4/30/2020, 7:36:45 PM +65ms
+1ms ╔Received event [Home].time = 1588289806712 with a delay of -1647ms
+91ms ║RunTime Analysis CS > 18ms > PS > 32ms > PE > 41ms > CE
+94ms ║Runtime (38295 bytes) successfully initialized in 32ms (v0.3.10a.20190223) (92ms)
+95ms ║╔Execution stage started
+102ms ║║Cancelling condition #10’s schedules…
+103ms ║║Condition #10 evaluated true (1ms)
+144ms ║║Comparison (time) 70605170 is_not_between (time) 1588241700000 … (time) 1588292460000 = false (11ms)
+146ms ║║Condition #9 evaluated false (42ms)
+147ms ║║Condition group #8 evaluated false (state did not change) (46ms)
+148ms ║║Condition group #1 evaluated false (state did not change) (47ms)
+151ms ║║Condition group #6 evaluated true (state did not change) (0ms)
+163ms ║╚Execution stage complete. (68ms)
+166ms ╚Event processed successfully (166ms)

#4

If you turn on Trace, your log will make more sense…

#5

Doesn’t ‘turn on’ for the garage door mean ‘open’? Not sure what type you have but that is how mine works.

#6

The 7:36 log looks like the wake up from the ‘stays open’. I’m not sure if the scheduled task would necessarily show up there but I’d certainly expect there to be one regardless of anything.

The 8:52 is the piston starting up after being edited or restarted. It is just deciding what device events to subscribe too (the Garage Door Sensor) and whether it needs to schedule any runs immediately (next day at sunset for the happens daily).

I’ve had lots of issues with missed timers of late so am wary that something may have been broken with SmartThings.

#7

Waited for sunset tonight and it didnt work again
This time there is an error in the logs not sure what it means

image
image.png1178×745 34.5 KB

5/1/2020, 8:21:59 PM +62ms
+0ms ╔Received event [Home].time = 1588378920000 with a delay of -939ms
+80ms ║Runtime (39133 bytes) successfully initialized in 33ms (v0.3.10a.20190223) (79ms)
+81ms ║╔Execution stage started
+146ms ║║Error while executing physical command Garage Door.on([]): java.lang.reflect.UndeclaredThrowableException
+147ms ║║Executed [Garage Door].on (17ms)
+156ms ║╚Execution stage complete. (75ms)
+157ms ╚Event processed successfully (157ms)
5/1/2020, 12:26:34 PM +71ms
+1ms ╔Received event [Home].time = 1588350395793 with a delay of -1722ms
+89ms ║Runtime (39134 bytes) successfully initialized in 39ms (v0.3.10a.20190223) (88ms)
+90ms ║╔Execution stage started
+170ms ║╚Execution stage complete. (80ms)
+171ms ║Setting up scheduled job for Fri, May 1 2020 @ 8:22:00 PM EDT (in 28525.758s)
+180ms ╚Event processed successfully (179ms)

#8

Have you tried just making a piston that just executes the commands ‘turn on’ or ‘turn off’ as a test to be sure they work? What device/DTH are you using to control the garage door? It may not support turn on/off. I know for Alexa I have to say ‘turn on’ or ‘turn off’ but both the garage doors I have (which each use different DTH) use open/close.

#9

I can try that. I have other zwave dry contact switches the same that work ok. They come with firmware that is programable I can program them to turn off when turned on from 1 to 60 seconds later. It does work in Smartthings with the shortcut under things

#10

Just first try a short piston like this:

with 
  Garage Door
do
  turn on
end with

Hit test and see what happens. Then edit to make it ‘turn off’. If those don’t work, try open/close.

#11

Thanks. It worked good last night. Ill let it go a couple more times to see. Maybe the error was just a one time thing