Jump to content

Force GeoFence Status Check


PB11

Recommended Posts

Posted

Greetings All

I've had Occupancy setup for a year or so(can't remember which version i.e. Occupancy, Occupancy 2(Mobile Device), Occupancy 2(Geofence) and uncertain how to confirm this), and on the most part has been pretty solid.

Once in a while, today being one of those times, the status of our 2 iphones is not accurate.

What I'm wondering is if there is a way to force a status check?

I've attempted to run the "If" component of my geofence program but I think its really only checking on the existing status not actually confirming the status

I've used the "Query" button on the Admin Console Main Page for the iphone Geofence node, but nothing seems to happen with status or in the Event Viewer.

Would anyone be able to shed some light on this one?

Thanks very much

Peter

 

Posted (edited)

Are you using Locative app on iOS with Occupancy?   or Occupancy 2 with UDI Mobile?   

I can answer the iOS with Occupancy...

To update your location manually open the locative app and long press the "Location" in the "locations" screen in the app.  (if "Edit GeoFence" pops up you tapped, you need to long press.) On long press you'll see a context menu popup with the items Trigger "Enter" Event and Trigger "Exit" Event.  Use those to manually get your phone back on the correct side of the fence.

Also there seems to be a problem with Locative and being upgraded to iOS 15.  The developer still hasn't answered my email, but the solution seems to be "After upgrading to IOS 15, uninstall Locative, restart the phone, reinstall Locative."  Other variations of those steps might work, I haven't tested.  Those worked on mine and my wifes phones.  The symptom that caused me to uninstall, restart reinstall was that "Exit" events were mostly not working.  It's worked correctly since uninstall/reinstall tho.

To save time and frustration be sure to tap the "location" then copy and paste your 2 webhook URLS to a NOTE on your iPhone, so that you can reverse that and paste them back into the app on reinstall.

Edited by MrBill
Posted

Same situation has happened to me as well. Appears to be a problem with Locative.  Thanks for the good advice Mr. Bill!

 

Posted
22 hours ago, MrBill said:

Are you using Locative app on iOS with Occupancy?   or Occupancy 2 with UDI Mobile?   

@MrBillThat is a good question. Here's a dumb one, how would i know? I have attempted a few ways until i got it working.

I believe its Geofence as the (Mobile Device) which I assume refers to the app wasn't available for iphones when I originally set it up. 

Is there a benefit to either?

 

Side note: Do I need to @ someone when quoting them or are they notified simply because they are quoted?

Posted
Just now, PB11 said:

@MrBillThat is a good question. Here's a dumb one, how would i know? I have attempted a few ways until i got it working.

I believe its Geofence as the (Mobile Device) which I assume refers to the app wasn't available for iphones when I originally set it up. 

Is there a benefit to either?

 

Side note: Do I need to @ someone when quoting them or are they notified simply because they are quoted?

Quoting notifies.....

Occupancy only works with the app Locative and Locative is only available on the iOS platform (they dropped the android version).

Occupancy V2 only works with UD mobile and not locative.  I also think UD mobile and Occupancy V2 is only supported on the Andriod version and not iOS, but personally I'm confused looking at the Occupancy V2 wiki page because it's last edit was in August 2018 and I wasn't aware UDI mobile was around in August of 2018.   Paging @Javi because he knows this answer.

  • Thanks 1
Posted
6 hours ago, MrBill said:

only works with UD mobile and not locative.  I also think UD mobile and Occupancy V2 is only supported on the Andriod version and not iOS, but personally I'm confused looking at the Occupancy V2 wiki page because it's last edit was in August 2018 and I wasn't aware UDI mobile was around in August of 2018.   Paging @Javi because he knows this answer.

It is a little confusing as only the prefixed abbreviation is different.

"UDI Mobile" a 3rd party Android app for Geofencing. This is the reference in the Occupancy V2  instructions. 

"UD Mobile" In house Android and iOS app for Control and Configuration of ISY which currently does not have geofence implemented.

  • Like 2
  • Thanks 2
Posted
1 minute ago, Javi said:

It is a little confusing as only the prefixed abbreviation is different.

"UDI Mobile" a 3rd party Android app for Geofencing. This is the reference in the Occupancy V2  instructions. 

"UD Mobile" In house Android and iOS app for Control and Configuration of ISY which currently does not have geofence implemented.

Thanks!  that is confusing! 

So @PB11 it boils down to whether you have iOS or Android.   If you have iOS, you are using it Locative app and using Occupancy.  If you have Android, you are using with UDI Mobile (which is 3rd party) and using Occupancy V2.

  • Thanks 1
Posted (edited)

Ok, so I am using locative with Occupancy.

On 10/29/2021 at 4:27 PM, Javi said:

"UDI Mobile" a 3rd party Android app for Geofencing. This is the reference in the Occupancy V2  instructions. 

"UD Mobile" In house Android and iOS app for Control and Configuration of ISY which currently does not have geofence implemented.

Its all in the details. :) Completely overlooked this one.

@MrBillOccupancy it is. I'm an IOS guy. Thanks for clarifying that .

 

Also took the steps of running the long hold arrival as suggested above but did not see any status change.

Yesterday I went for a drive with my UD app open to my geofence nodes and watched as both my neighbor hood and ios device node status changed.

So its not locative, but MyQ that is having issues.

Working on that from previous string here.

 

 

Edited by PB11
Posted

Wondering if anyone knows if the long hold “trigger event” feature on Locative should be functional on all iPhones?

it seems to be working on my XR but not working on my wife’s XS. 

Posted
13 hours ago, PB11 said:

Wondering if anyone knows if the long hold “trigger event” feature on Locative should be functional on all iPhones?

it seems to be working on my XR but not working on my wife’s XS. 

Is your wife's App up to date?  That was added to the app in version 5.2.0 of locative about 6 months ago.  (it was added as a direct result of an email I sent to the developer.)

Posted

Ya it’s all up to date. 
First notice wife’s IOS was out of date so uninstalled Locative, did IOS update to 15 then reinstalled and reconfigured Locative. 
when I long press it takes me Into location settings. 
have tried long press, short press, hard press. No joy. 

Posted

There are apparently Geofencing issues in iOS 15 https://discussions.apple.com/thread/253247480

Until this morning I thought this was a Locative issue, but it looks like Apple broke it.

that said... that doesn't explain why long press to reach the manual triggers isn't working for you.  Obviously since it works for you on one, you know what to do and should be able to do it on the other.  I would expect the XR to be the odd man out tho...

Posted

Ya, it actually seems like the XS may have a different touch capability compared to the XR.

I wasn't able to see anything online.

  • 2 weeks later...
Posted

I too have been plagued with the Geofence breaking in IOS 15 starting with Mobilinc so I switched my phone to Locative and it seemed to work initially so I set up my wife's phone which she is still on 14.XX IOS and it worked initially as well. 

Today the first test for both phones on a Monday leaving the home failed on both not updating proper status & running my programs. Not sure if the best thing is to wait for IOS to get fixed or try to work with the devs. I sent a message to Mobilinc support and so far no response. 

 Have already spent so much time just to figure out what was broken (geofence) so getting exhausting but it would be nice to keep my system running where I use it. 

Posted
2 hours ago, sdynak said:

Locative and it seemed to work initially so I set up my wife's phone which she is still on 14.XX IOS and it worked initially as well. 

I can echo this, is true and I don't know why.   I had re-installed Locative on both our phones, initially after re-install the geofence worked correctly on both.  My wife's was first to stop working on Exit's but If I manually triggered the Exit it would then detect when she returned.  Then it would do neither.  All the while my phone was working correctly (for weeks now), until today, now my phone has no detected me leaving or returning.

Hope Apple fixes iOS 15 soon.

  • Like 1
Posted
3 hours ago, MrBill said:

I can echo this, is true and I don't know why.   I had re-installed Locative on both our phones, initially after re-install the geofence worked correctly on both.  My wife's was first to stop working on Exit's but If I manually triggered the Exit it would then detect when she returned.  Then it would do neither.  All the while my phone was working correctly (for weeks now), until today, now my phone has no detected me leaving or returning.

Hope Apple fixes iOS 15 soon.

Yes please :) .. At least her Mobilinc was still working on 14.XX .. With Locative it did not work today when she left so I think something with Locative is still not perfect even on earlier versions. I can try reinstalling but knowing what is happening on 15.1 I'm thinking just to let hers go back to Mobilinc for now.

I had hopes for Locative as Mobilinc has not been updated in years and figure it was just a matter of time. Fingers crossed :).  

Posted

@sdynak I don't think you'll have luck with either until Apple does something.  Is apple still signing the last version of 14.x?   if they are it's still possible to revert to iOS 14 and that would fix both. 

Posted
2 hours ago, MrBill said:

@sdynak I don't think you'll have luck with either until Apple does something.

@MrBill I think you are right. I just got this response from Mobilinc:

Apple broke geofencing in iOS 15.0. It appears to be marginally better in iOS 15.1, but there are still known bugs and reliability issues with iOS informing apps when the boundary is crossed with all 3rd party apps that use geo-fencing. I've been testing this here and while iOS regularly tells MobiLinc that it's left a geo-fence, I rarely see iOS tell MobiLinc that it has "re-entered" a geo-fence.

We're hoping that Apple fixes the issue in an update to iOS 15. Right now there's nothing 3rd party apps can do to work around the iOS reliability part of the geo-fence detection problem.
  • Like 1
Posted

I was having the same issue, but upgraded both my XR and my wife’s XS to the most Current version of iOS which is 15.0.2.

In addition I completely uninstalled and reinstalled locative once the update was done.

Based on a recommendations from another forum user I copied both the enter and exit URLs before deleting Locative

Both seem to be working quite well now.

  

 

Posted
13 minutes ago, PB11 said:

I was having the same issue, but upgraded both my XR and my wife’s XS to the most Current version of iOS which is 15.0.2.

In addition I completely uninstalled and reinstalled locative once the update was done.

Based on a recommendations from another forum user I copied both the enter and exit URLs before deleting Locative

Both seem to be working quite well now.

  

 

 

 I really don't know how to do down in iOS versions.. right now I'm on 15.1 and is is spotty at best. If I have the app open for example Mobilinc open the triggers seem to work but if it has been not opened it defiantly is not working in 15.1 for me and my wife's is on 14.xx and spotty as well. Today it did work when she left home but not yesterday. I think it has something to do with data in the background although I have ensured both Mobilinc and Locative are enabled. It seems to get sleepy for lack of better words. 

 

 

 

Posted (edited)

Fair enough.

Hadn’t realized 15.1 had been released. I’ll make sure I don’t upgrade either of our phones until corrections are made  

The other variable is that I’m using poly cloud. I uninstall the Node server and reinstalled it re-creating my Geo nodes 

not certain this had anything to do with locative coming back online but at the time Michael did say some of the node servers were having issues  

sorry I couldn’t be of more help

 

Edited by PB11
Posted
11 minutes ago, PB11 said:

Fair enough.

Hadn’t realized 15.1 had been released. I’ll make sure I don’t upgrade either of our phones until corrections are made  

The other variable is that I’m using poly cloud. I uninstall the Node server and reinstalled it re-creating my Geo nodes 

not certain this had anything to do with locative coming back online but at the time Michael did say some of the node servers were having issues  

sorry I couldn’t be of more help

 

 

 Thank you..

Any insight is helpful.. I spent a lot of time just getting to this point. Not sure if 15.1 is released to just certain iPhone models but mine is a 12 and so is my wife's (mini) but still on 14.xx. I am having her hold off going to 15.1 but odd thing is Locative was spotty there as well and that was with just put on as I was having issues with Mobilinc. Locative was a fresh install on both phones given Mobilinc issues. 

My thought was Locative resolved the issues thinking it was Mobilinc at first but it was short lived. So guess I just have to wait and see or downgrade iOS somehow and use Mobilinc but I'll likely wait and see if things get better in the next iOS update. 

I am using "Occupancy" through the ISY Portal. I have not wandered into the Poly Cloud world yet. I'm still very green on that. 

 

Posted
2 hours ago, sdynak said:

Locative was spotty there as well and that was with just put on as I was having issues with Mobilinc. Locative was a fresh install on both phones given Mobilinc issues. 

iOS broke geofences.  Period.  When Apple fixes the bug both Locative and Mobilinc will work again.  It's not the fault of either app, the breakage is on Apple's side.  15.2 is in beta and it's reported that there is no fix there either.

Guest
This topic is now closed to further replies.

×
×
  • Create New...