- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
after installing the new app on both devices, and set to Geofencing, even when both devices are stated as being "in zone", it sets to Away mode and starts triggering motion detection alerts. With old app use to be able to toggle to Disarm then back to Geofencing and would stay in Home mode. Now not the case. Always in Away mode. Very frustrating and you'd think with how much these Arlo setups cost they could get this fundamental issue correctly operating.
Have looked at the previous "solutions" of reserving Home address, but that hasn't worked.
Solved! Go to Solution.
- Related Labels:
-
Online and Mobile Apps
-
Troubleshooting
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Geofencing issue solved - at least for me ....
I had to go into the map where you set the geofencing zone, moved position to an entirely different random address and then saved. Then repoint to my actual address and saved again. This worked, and has continued to work for a week no problems. The problem before was that it just didn't recognise whatever address was there at the time of the app upgrade.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Just when things had settled down and started working again, this latest app update 2.9.1 has broken geofencing yet again. The system sees my phone as "in the zone" and ARMS itself. I have changed mode to disarm and then Geofencing and every time, it ARMS itself. I have removed the address and phone and set up from scratch, same result.
ARLO, YOU NOW HAVE IT WORKING BACKWARDS..... DO YOU EVER TEST YOUR SOFTWARE EXTENSIVELY BEFORE YOU RELEASE IT? OBVIOUSLY NOT.
SHAME SHAME SHAME.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi WAJ_oz and bmwdriver7175,
What phone device are you using? Have you updated to the latest version for the Arlo app? Have you tried rebooting your phone device? You can also look at this article to see if this article can help: Why isn't the Geofencing mode working?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Same issue here, phone is detected as in the zone and the system arms itself. Wow! Simply WOW, how many more times is this going be broken. You had just fixed it and now with 2.9.1 for IOS, it's broken yet again.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If you still have problems with your Geofencing not working properly, please contact the Support Team to further investigate this issue. You will find several options for contacting support in the provided link.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Afraid I have to agree with all the sentiments about. I have had Alro cameras for about a year and would say about 50% of that time geo fencing has worked reliably. One update fixes it, another breaks it. I mean there are free throwaway apps out there that do it better, and this is a very expensive camera system. Get it together devs. My recommendations have certainly stopped for now.
My exact scenario for debug is very basic - two phones with geo fencing AWAY=Arm and HOME=Schedule where it is armed 12-6am, disarmed all other times. Issues are same as above, when both phones actually show ON THE MAP IN THE APP they are in the zone it still goes into AWAY mode. iOS13 - but if that is offered as an excuse it is pathetic, been beta for 6 months.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Here's something that worked. After I updated the latest app and removed phone(s) from geofencing and set the address again and then added the phones back in, it still detected the phone in the zone and ARMED the system. I wasn't until I actually left the zone and let arlo detect that I truly was out of the zone and then came back into the zone ( i ran to the grocery store and back), all of a sudden it started working correctly again. Not sure why that is, but hey if it will others, give it a try. Hope it helps.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks. I actually removed everything and setup the system completely fresh on both phones and it did actually work for a day or two. Then it just gets patchy again. I feel there may be an iOS13 issue, which is not excuse as it's beta has been available for 6 months. But may point to the cause better - iOS13 does seem to have a heavier privacy focus. Perhaps the Arlo app is not doing something it needs to for long term stability. As an aside it is hilarious when companies try and blame a new OS for their poor software performance when the beta programs are as extensive as Apples.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Maybe a hint. Starting getting this message from the app after switching to the new version and iOS 13. It is nonsense, the Internet is never out on the hub or phone but perhaps it is linked to this latest failure of geo fencing. It still updates my location so no sure what the message means.
https://imgur.com/a/oqCeM3I
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Jessica, the whole point was that I/we had downloaded and installed the latest app and that the problem was occurring. Its not the other devices at fault, its Arlo's app.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Geofencing issue solved - at least for me ....
I had to go into the map where you set the geofencing zone, moved position to an entirely different random address and then saved. Then repoint to my actual address and saved again. This worked, and has continued to work for a week no problems. The problem before was that it just didn't recognise whatever address was there at the time of the app upgrade.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
-
Arlo Mobile App
564 -
Arlo Pro 2
11 -
Arlo Smart
167 -
Before You Buy
972 -
Features
409 -
Firmware Release Notes
57 -
Google Assistant
1 -
IFTTT (If This Then That)
24 -
Installation
1,122 -
Online and Mobile Apps
865 -
Service and Storage
317 -
SmartThings
37 -
Troubleshooting
6,122