webCoRE Presence Sensor - Approaching Places

[GRClark]

Here’s what I got now and still no luck. I’m going to clear the logs and post after the next time I go home.

[c1arkbar]

The distances shouldn’t be the same number

[GRClark]

They’re not the same number, but it was a boneheaded move on my part because I’d forgotten about the restrictions. So I removed that and it works fine however is there a way to make it so it doesn’t keep triggering repeatedly? Right now I’ve got notifications for testing purposes and must’ve gotten 20+ text messages before getting home! I’m just not sure how - thought maybe only once within a certain period of time, but what if I got home and then left again? What would you suggest?

[c1arkbar]

Both are saying 2 miles. Unless you have changed that?

So I removed that and it works fine however is there a way to make it so it doesn’t keep triggering repeatedly? Right now I’ve got notifications for testing purposes and must’ve gotten 20+ text messages before getting home! I’m just not sure how - thought maybe only once within a certain period of time, but what if I got home and then left again? What would you suggest?

And presence is not present

[GRClark]

Corrected the mileage, but what do you mean presence is not present?

[pcgirl65]

Add the conditions Presence Sensor is not present in your If Statement.

[c1arkbar]

Yea, what @pcgirl65 said. Just adding the condition

[GRClark]

Believe this is what you suggested but now the piston doesn’t run.

[c1arkbar]

You don’t want that in the followed by condition. It should be a separate condition. You might need to group the followed by commands so you can have an and between them

[GRClark]

Ok how’s this? It works but again it’s giving multiple repeat notifications - is there a way to limit so that the piston only runs once at a time, but still be able to run other times if I leave and come back? Or at least make it so I only get one notification?

[c1arkbar]

Yup that is what I was talking about!!

[GRClark]

And how do I limit the number of notifications?

[c1arkbar]

My apologies. In your places setup. Is your outter circle large enough that upon entering it that would accomplish your goals with this piston?

I do believe I might have been steering you in the wrong direction. If you answered yes to the above then you can simply use the following

If webcore presence arriving at place changes to “Home”
Then
Your actions
End if

[GRClark]

No need for apologies - I just appreciate your help! So I’ve got it down to two messages.

[c1arkbar]

Can you set logging to full and next time it happens paste the logs here please?

[GRClark]

This last time I came home only one notification came through, but here are the logs as you requested…

[GRClark]

‎‎12‎/‎9‎/‎2017‎ ‎12‎:‎53‎:‎07‎ ‎PM +732ms
+2ms
╔Received event [Tall Pines].test = 1512841987721 with a delay of 7ms
+109ms
║RunTime Analysis CS > 22ms > PS > 64ms > PE > 26ms > CE
+121ms
║Runtime (37725 bytes) successfully initialized in 64ms (v0.2.0ff.20171129) (116ms)
+123ms
║╔Execution stage started
+167ms
║║Condition #5 evaluated false (24ms)
+168ms
║║Condition group #1 evaluated false (state did not change) (28ms)
+176ms
║╚Execution stage complete. (54ms)
+187ms
╚Event processed successfully (189ms)
‎12‎/‎9‎/‎2017‎ ‎10‎:‎47‎:‎42‎ ‎AM +657ms
+1ms
╔Received event [Gigantes].arrivingAtPlace = with a delay of 71ms
+124ms
║RunTime Analysis CS > 22ms > PS > 83ms > PE > 19ms > CE
+132ms
║Runtime (37718 bytes) successfully initialized in 83ms (v0.2.0ff.20171129) (130ms)
+133ms
║╔Execution stage started
+140ms
║║Comparison (string) changes_to (string) Home = false (0ms)
+141ms
║║Condition #5 evaluated false (4ms)
+142ms
║║Condition group #1 evaluated false (state did not change) (5ms)
+144ms
║╚Execution stage complete. (12ms)
+151ms
╚Event processed successfully (151ms)
‎12‎/‎9‎/‎2017‎ ‎10‎:‎47‎:‎24‎ ‎AM +541ms
+1ms
╔Received event [Gigantes].arrivingAtPlace = with a delay of 57ms
+708ms
║RunTime Analysis CS > 315ms > PS > 365ms > PE > 28ms > CE
+714ms
║Piston waited at a semaphore for 260ms
+716ms
║Runtime (37791 bytes) successfully initialized in 365ms (v0.2.0ff.20171129) (714ms)
+717ms
║╔Execution stage started
+725ms
║║Comparison (string) changes_to (string) Home = false (1ms)
+726ms
║║Condition #5 evaluated false (4ms)
+727ms
║║Condition group #1 evaluated false (state did not change) (5ms)
+729ms
║╚Execution stage complete. (12ms)
+736ms
╚Event processed successfully (736ms)

‎12‎/‎9‎/‎2017‎ ‎10‎:‎47‎:‎24‎ ‎AM +873ms
+1ms
╔Received event [Gigantes].arrivingAtPlace = Home with a delay of 48ms
+140ms
║RunTime Analysis CS > 11ms > PS > 105ms > PE > 24ms > CE
+148ms
║Runtime (37726 bytes) successfully initialized in 105ms (v0.2.0ff.20171129) (146ms)
+149ms
║╔Execution stage started
+157ms
║║Comparison (string) Home changes_to (string) Home = false (1ms)
+158ms
║║Cancelling condition #5’s schedules…
+159ms
║║Condition #5 evaluated false (5ms)
+160ms
║║Cancelling condition #1’s schedules…
+161ms
║║Condition group #1 evaluated false (state changed) (7ms)
+164ms
║╚Execution stage complete. (14ms)
+171ms
╚Event processed successfully (171ms)

12‎/‎9‎/‎2017‎ ‎10‎:‎47‎:‎24‎ ‎AM +249ms
+4ms
╔Received event [Gigantes].arrivingAtPlace = Home with a delay of 131ms
+134ms
║RunTime Analysis CS > 17ms > PS > 83ms > PE > 33ms > CE
+142ms
║Runtime (37727 bytes) successfully initialized in 83ms (v0.2.0ff.20171129) (137ms)
+143ms
║╔Execution stage started
+151ms
║║Comparison (string) Home changes_to (string) Home = true (0ms)
+153ms
║║Cancelling condition #5’s schedules…
+154ms
║║Condition #5 evaluated true (5ms)
+155ms
║║Cancelling condition #1’s schedules…
+155ms
║║Condition group #1 evaluated true (state changed) (7ms)
+158ms
║║Cancelling statement #2’s schedules…
+164ms
║║Skipped execution of physical command [Lamp].on([]) because it would make no change to the device. (3ms)
+165ms
║║Executed [Lamp].on (5ms)
+360ms
║║Executed physical command [Lamp].setColor([[hex: #006400, hue:33, saturation:100, level:20]]) (192ms)
+361ms
║║Executed [Lamp].setColor (193ms)
+376ms
║║Executed virtual command [Lamp].sendSMSNotification (9ms)
+379ms
║╚Execution stage complete. (236ms)
+388ms
╚Event processed successfully (388ms)

[wgmcg]

I just tried this syntax and it doesn’t work at all.

It doesn’t even generate an event. The first event I get is from the “present” event.

[GRClark]

My final pistons got a bit more in there then when I started - basically it’s setup so that when arriving at home my porch light turns on and the last part is to turn it off upon entering front door.

One thing to note is I’m using webCoRE presence sensor that gives extra options that an arrival sensor will not give so I’m not sure what you’re using.

[kxavier_23]

Not sure if this helps, but I have been watching my presence sensor in debug and driving outside, but near my geofences, I get “false” arrivingAt and departing notifications. It has been causing all kinds of piston issues as these events are coming so close that pistons that I use the arrivingAt/departing are cancelling.

I have another thread going where I am trying to filter out these false notifications based on GPS accuracy. Currently I have changed the DTH for presence sensor to give info if the GPS horizontalAccuracy is lower than 15 m (50ft). Watching my logs, my phone will give horizontalAccuracy of less than 10 when I am actually close to my house.

Until the app will actually filter out the low horizontalAaccuracy properly, I don’t know how to resolve these issues.

[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…