Auto shut and open garage door opener problems

coops8d · 2018-09-01 08:47:47 UTC

1) Give a description of the problem
This is my first real piston and having trouble getting it to work… I don’t know sometimes it seems to work and other times nothing. Really not sure if I have done something odd here or not. I am using Life360 as presence sensor as I do not have a ST hub, using Hubitat for the hub and the code I found for the Webcore said was for ST.

2) What is the expected behavior?
I leave the house the door should close and when I return it should open and then shut a few minutes after I get home.

3) What is happening/not happening?
Not consistent and most times just does not work.

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

**5) Attach any logs
9/1/2018, 4:31:47 PM +953ms
+1ms ╔Received event [ASHLEY].presence = present with a delay of 100ms
+91ms ║RunTime Analysis CS > 43ms > PS > 21ms > PE > 27ms > CE
+129ms ║Runtime (48957 bytes) successfully initialized in 21ms (v0.3.107.20180806) (127ms)
+130ms ║╔Execution stage started
+136ms ║║Comparison (enum) present changes_to (string) present = true (1ms)
+137ms ║║Cancelling condition #2’s schedules…
+138ms ║║Condition #2 evaluated true (4ms)
+143ms ║║Comparison (enum) open is (string) closed = false (0ms)
+143ms ║║Cancelling condition #18’s schedules…
+144ms ║║Condition #18 evaluated false (6ms)
+145ms ║║Condition group #1 evaluated false (state did not change) (12ms)
+147ms ║║Comparison (enum) present changes_to (string) not present = false (0ms)
+148ms ║║Cancelling condition #13’s schedules…
+149ms ║║Condition #13 evaluated false (3ms)
+150ms ║║Cancelling condition #12’s schedules…
+150ms ║║Condition group #12 evaluated false (state changed) (4ms)
+152ms ║║Comparison (enum) open is (string) open = true (0ms)
+153ms ║║Cancelling condition #21’s schedules…
+154ms ║║Condition #21 evaluated true (3ms)
+155ms ║║Cancelling condition #20’s schedules…
+155ms ║║Condition group #20 evaluated true (state changed) (4ms)
+156ms ║║Cancelling statement #22’s schedules…
+162ms ║║Executed virtual command [Garage Door Controller ].wait (0ms)
+170ms ║║Requesting a wake up for Sat, Sep 1 2018 @ 4:33:48 PM AWST (in 120.0s)
+180ms ║╚Execution stage complete. (51ms)
+184ms ║Setting up scheduled job for Sat, Sep 1 2018 @ 4:33:48 PM AWST (in 119.987s)
+218ms ╚Event processed successfully (218ms)

michicago · 2018-09-01 15:20:36 UTC

Nothing jumps out about your piston design that makes me think it’d behave intermittent, except possibly that ‘wait’ command you have nested. We can deal with that bit later though, if necessary.

When you are arriving or leaving home, does your cell phone have a good signal? Does your phone minimize data usage when the batter is low? I use Life360 as my presence sensor as well, and sometimes I have to move the phone in my truck or take it out of my pocket for it to update my location and trigger actions. Usually not though… so I know it can be pretty reliable (I’d say it works for me more than 95% of the time).

coops8d · 2018-09-01 15:35:08 UTC

Mmmm should have pretty good reception. If all looks good in the piston I will do some more tests tomorrow and see if I can pick up when it works and does not.

coops8d · 2018-09-08 06:02:29 UTC

So I sort have got this working well, but seems to be only working if we are both out. It is not opening if one of us is home and the other is returning. This is what I have atm

Is it the part where says if sensor changes to present then do this, but if one is already present it is throwing it off?

michicago · 2018-09-08 20:23:34 UTC

Interesting. Can you post a webCoRE log of one presence sensor arriving when the other is already present?

coops8d · 2018-09-09 04:19:11 UTC

9/9/2018, 12:14:53 PM +43ms
+0ms ╔Received event [Rosie].presence = present with a delay of 76ms
+113ms ║RunTime Analysis CS &gt; 61ms &gt; PS &gt; 32ms &gt; PE &gt; 20ms &gt; CE
+131ms ║Runtime (49246 bytes) successfully initialized in 32ms (v0.3.107.20180806) (128ms)
+132ms ║╔Execution stage started
+140ms ║║Comparison (enum) present changes_to (string) present = true (0ms)
+141ms ║║Cancelling condition #2's schedules...
+142ms ║║Condition #2 evaluated true (7ms)
+183ms ║║Comparison (enum) closed is (string) closed = true (1ms)
+185ms ║║Cancelling condition #18's schedules...
+186ms ║║Condition #18 evaluated true (42ms)
+187ms ║║Cancelling condition #1's schedules...
+188ms ║║Condition group #1 evaluated true (state changed) (53ms)
+190ms ║║Cancelling statement #3's schedules...
+205ms ║║Executed physical command [Garage Door Controller ].open() (11ms)
+206ms ║║Executed [Garage Door Controller ].open (13ms)
+210ms ║║Executed virtual command [Garage Door Controller ].setState (0ms)
+213ms ║║Cancelling statement #8's schedules...
+300ms ║║Executed physical command [Garage Light].on() (84ms)
+302ms ║║Executed [Garage Light].on (85ms)
+307ms ║║Comparison (enum) not present is (string) not present = true (1ms)
+309ms ║║Condition #20 evaluated true (4ms)
+312ms ║║Comparison (enum) closed is (string) open = false (1ms)
+314ms ║║Condition #21 evaluated false (3ms)
+315ms ║║Condition group #19 evaluated false (state did not change) (11ms)
+317ms ║╚Execution stage complete. (185ms)

It’s odd, though as from this unless I am reading it wrong it looks as if it says it did open the door when it did not do that.

michicago · 2018-09-10 00:37:06 UTC

That’s certainly how it reads. Do you know if the light turned on when the piston ran? Shows it did on the +300ms line - wondering if you have an intermittent behavior with your garage door opener or if it’s something else.

coops8d · 2018-09-10 02:33:56 UTC

Not 100% sure. I will have to do some more tests and record it all. I have feeling something to do with controller not always working.