WebCoRE Presence quickly changing present/absent/present

[robinogi]

I’ve noticed for some reason that my wife’s webCoRE Presence device is quickly changing from present to absent then back to present again when she returns home.

Log from my Presence piston is below, WC Presence is bolded:
2/13/2018, 5:23:17 PM +461ms
+1ms ╔Received event [Kery-Ann - WC Presence].presence = present with a delay of 95ms
+10029ms ║Piston waited at a semaphore for 9844ms
+10032ms ║Runtime (52636 bytes) successfully initialized in 9906ms (v0.2.102.20180116) (10030ms)
+10032ms ║╔Execution stage started
+10152ms ║║Executed virtual command setVariable (0ms)
+10154ms ║╚Execution stage complete. (122ms)
+10155ms ╚Event processed successfully (10155ms)
2/13/2018, 5:23:17 PM +233ms
+1ms ╔Received event [Guest Arrival].presence = present with a delay of 104ms
+136ms ║Runtime (52568 bytes) successfully initialized in 43ms (v0.2.102.20180116) (134ms)
+137ms ║╔Execution stage started
+225ms ║║Executed virtual command setVariable (1ms)
+231ms ║║Executed [Kery-Ann].on (3ms)
+304ms ║║Executed virtual command sendPushNotification (19ms)
+313ms ║║Executed virtual command setVariable (1ms)
+315ms ║╚Execution stage complete. (179ms)
+316ms ╚Event processed successfully (316ms)
2/13/2018, 5:20:29 PM +473ms
+1ms ╔Received event [Kery-Ann - WC Presence].presence = not present with a delay of 98ms
+10333ms ║Piston waited at a semaphore for 10018ms
+10335ms ║Runtime (52651 bytes) successfully initialized in 10206ms (v0.2.102.20180116) (10326ms)
+10336ms ║╔Execution stage started
+10452ms ║║Executed virtual command setVariable (1ms)
+10454ms ║╚Execution stage complete. (118ms)
+10545ms ╚Event processed successfully (10545ms)
2/13/2018, 5:20:29 PM +109ms
+0ms ╔Received event [Kery-Ann’s iPhone (L360)].presence = present with a delay of 91ms
+9908ms ║Piston waited at a semaphore for 9768ms
+9911ms ║Runtime (52647 bytes) successfully initialized in 9811ms (v0.2.102.20180116) (9910ms)
+9912ms ║╔Execution stage started
+10039ms ║║Executed virtual command sendPushNotification (9ms)
+10050ms ║║Executed virtual command setVariable (0ms)
+10052ms ║╚Execution stage complete. (141ms)
+10053ms ╚Event processed successfully (10054ms)
2/13/2018, 5:20:29 PM +228ms
+0ms ╔Received event [Kery-Ann].switch = on with a delay of 190ms
+9681ms ║Piston waited at a semaphore for 9523ms
+9683ms ║Runtime (52625 bytes) successfully initialized in 9571ms (v0.2.102.20180116) (9682ms)
+9684ms ║╔Execution stage started
+9821ms ║║Executed virtual command sendPushNotification (8ms)
+9833ms ║║Executed virtual command setVariable (1ms)
+9835ms ║╚Execution stage complete. (151ms)
+9836ms ╚Event processed successfully (9837ms)
2/13/2018, 5:20:31 PM +720ms
+0ms ╔Received event [Home].mode = Home with a delay of 93ms
+140ms ║Runtime (52546 bytes) successfully initialized in 43ms (v0.2.102.20180116) (139ms)
+141ms ║╔Execution stage started
+273ms ║║Executed virtual command sendPushNotification (7ms)
+281ms ║║Executed virtual command setVariable (0ms)
+284ms ║╚Execution stage complete. (142ms)
+284ms ╚Event processed successfully (284ms)
2/13/2018, 5:20:29 PM +458ms
+0ms ╔Received event [Kery-Ann’s iPhone (ST)].presence = present with a delay of 92ms
+135ms ║Runtime (52578 bytes) successfully initialized in 44ms (v0.2.102.20180116) (134ms)
+136ms ║╔Execution stage started
+410ms ║║Executed virtual command setVariable (0ms)
+416ms ║║Executed [Kery-Ann].on (4ms)
+471ms ║║Executed virtual command setVariable (0ms)
+473ms ║╚Execution stage complete. (338ms)
+474ms ╚Event processed successfully (474ms)
2/13/2018, 5:20:28 PM +636ms
+1ms ╔Received event [Kery-Ann - WC Presence].presence = present with a delay of 222ms
+165ms ║Runtime (52583 bytes) successfully initialized in 64ms (v0.2.102.20180116) (163ms)
+166ms ║╔Execution stage started
+255ms ║║Executed virtual command setVariable (1ms)
+526ms ║║Executed [Kery-Ann].on (268ms)
+581ms ║║Executed virtual command setVariable (1ms)
+583ms ║╚Execution stage complete. (418ms)
+584ms ╚Event processed successfully (584ms)

Any idea what might be going on? It switches from Present then to Away within 1 second of each other (at the same time that the Life360 and SmartThings presence sensors report her as “arrived”) then WC Presence changes back to “present” 3 minutes later.

[salieri]

Same here, I noticed this happening yesterday evening and was scratching my head (screenshot taken from the Smartthings iOS app):

[ptdalen]

I had similar behavior with my wife’s presence but not mine. It was consitent too. We take slightly different routes to where we park. I come in a back way, and she comes in the front way. We both end up at the same place. Best I could figure was that the slight difference had her entering the inner circle and then leaving (maybe just right on the edge. ) before getting home. Thats basically what the image above seems to show.

If you have pistons based on arrival, you could put in a lockdown timer or something similar to keep it from firing twice. I added a 1 minute delay in one of my pistons, to keep it from firing twice and so far its been working quite well

[salieri]

I played around with this, and it appears my arrival circle was too small. After fixing this, the issue stopped.

EDIT: Scratch that, the problem still exists.

[kxavier_23]

I have the same issue. The prescense app is taking updates to the app when I believe it shouldn’t. I have asked for help on this.

[Install Instructions] webCoRE Presence Sensor on your iPhone (beta)

Maybe this will help. I went ahead and made a copy of @ady624 DH and changed if the horizontalAccuracy was > 10, then drove around where I have been getting false arrival/departure triggers. Regardless of the change above, the arrivingAt and presence are still being update. I can see the info message I stated above, but things just keep getting updated anyway. Here are the logs I captured: [image] There are no horizontalAccuracy updates lower than 10 until I am actually at my house. Can s…

[steinauf]

If you have pistons based on arrival, you could put in a lockdown timer or something similar to keep it from firing twice. I added a 1 minute delay in one of my pistons, to keep it from firing twice and so far its been working quite well

i had this issue too, so i set a check to not run issue a notice for at least 30 seconds.

i just modified that use a “stays” trigger for 15 seconds. we’ll see how well that works. i’m hopeful that since the rapidfire changes were so close together, a 15 second delay will minimize the issue.

[flyize]

Good Lord would I do anything for good presence detection (outside of Life360, which seems uber creepy).

[steinauf]

stays didn’t really work. i drove past the location, and was well down the road before i got a notification that i had arrived, then 15 seconds later got a notification that i had left.

so i upped it to 25 seconds and tried again. i drove past, got a notification a bit later, but this time (due to the way my notifications and variables are set), my notification did not include the variable for my current place. and then even farther away i got the notification that i had left, again with a blank value for current place variable. not the behavior i was expecting, but i’ll dig into it some more