Presence sensor bearing built in functionality?

#1

I have this piston. But was wondering if it is already built into webcore and I am just missing it… if not then this does work nicely rather than getting the degrees that you are heading using the [presence sensor:bearing] attribute

63C6CAFC-5213-4543-B375-79528D025D4D
63C6CAFC-5213-4543-B375-79528D025D4D.jpeg2012×1600 671 KB

#2

63B1D7DC-BA8A-49C7-9EDE-6C8913F27427
63B1D7DC-BA8A-49C7-9EDE-6C8913F27427.jpeg750×353 83.8 KB

Like this?

#3

Yes I see that. But how do I call that from a piston to send as a text message?

#4

Ok. Off on mini vacation, going to be traveling 300 miles. Time to see if this presence thing works as expected. I have Setup “waypoints” along the way to text myself and wife my progress to the destination. Keep fingers crossed I wrote it correctly. Let you know the results when I get there…

#5

On mobile so I can’t really play with the expression editor. But I would look through the attribute options of [webcore presence: attributes] and see what pops up. Your piston looks like it should work. Good luck

#6

Well. I can safely say that if cell service is spotty, so is presence. 3G connection is unreliable. Second thing, if you are on a highway and you have a way point Setup make sure your arriving circle is “LARGE”. It seems that either the iPhone or webcore only checks for presence every 5 minutes or so. With that being said, if you are flying down the road, you will blow right through the geofence before the presence even updates.

#7

Presence should be updating every 5 minutes OR significant change in location (Apple specifies this as greater than 500 meters) OR you enter/exit a geofence.

If your circles were on the highway then you might have gone through them too fast to have the updated location. When a geofence triggers it doesnt necessarily mean there will be an update to the GPS location.

#8

I had the, set just off the highway, as I didn’t actually want to arrive. I just wanted to trip the arivingat fence. Like I said I may need to broaden the fence, in order for it to register it correctly

#9

You could be right and just need to make the fence bigger. You were triggering off of the arrivingAt data point in your piston i presume?

#10

No I was not I was bowin through them. I’m not sure what happened . I am on iOS 11.03. Just updated to that. But what I did notice is that my phone for some reason at some point got stuck on a gps location and never left it. I rebooted my phone and reinstalled webcore beta app and things “seem” ok now. Will be traveling home today and will check my locations again. I did some tinkering with the piston while I have been gone. So that may throw a we]reach into it. Time will tell. I will post my findings when I get home.

#11

Good luck and safe travels

#12

Ok. Home. Thanks for safe travel wishes. Pistons fired off without a hiccup, except where cell coverage is spotty. Weird thing is google maps could find me, and not webcore mobile.

On bug I did find was the speed attribute, reports incorrectly @ady624 It seems to be reporting metric speed not mph. I was driving 70mph and reported 106. I know there is an option fro either speed or speed(metric)Didn’t try imperial.

Here is my expression for setting the speed variable to pass via args

floor([Tom :speed]) ‘ Mph’

#13

You are correct. I set default fences and worked ok. Problem I had was I dropped pin in wrong location and it never entere the fence

Thank you