Arlo Go + New App + Enabling Geofencing: HOW?

[er-minio]

After many years, my app has been updated to the new system/design.

My setup is a single Arlo Go (1st gen) that is armed when I am away from "home" location.

Switching to the new version of the app messed up all the settings. 

The way you have to select the location is now only by address (putting a pin on a map would be WAY more accurate in a lot of locations, but I digress).

Issue I have is that, now, my camera is triggered every time.

I tried both modes:

- Custom Mode selecting the camera from the dropdown and putting it on "geofencing"

- Arm Away Mode, but there is no devices associated and no way to add any (see screenshot)

I appreciate that a major app version change like this would disrupt user habits a bit, and that is ok, but I am really struggling to make sense of the current UI.

The geofencing area is correctly set. The device is listed (under the settings) within the location. The app has location services permissions on iOS set to "Always".

I want the camera to be disabled when I am inside the geofencing area.

System is set to "Arm Away" currently, to no avail.

HOW.

Thanks.

[BrookeN]

Geofencing is not compatible with the Arlo Go at this time. If you wanted to use Geofencing with the Arlo Go it would need to be Arlo Go 2. 

[er-minio]

Really?

But Geofencing is managed on the device (phone) side Vs a fixed location triggering a change of status in the system. Camera model should have absolutely nothing to do with it.

[BrookeN]

Unfortunately, the Arlo GO does not support Geofencing. It can be used with custom modes but not Geofencing. 

[er-minio]

It would have been useful if this information was relayed to the user when prompting for the app update.
I would have kept the old app/account version as everything worked correctly.

[StephenB]

---

@er-minio wrote:

I would have kept the old app/account version as everything worked correctly.

---

Not for long, since Arlo is rapidly phasing out the old interface.

[er-minio · Accepted solution]

Update: I was able to make this work. I have no idea why it has been said that the first gen Arlo Go doesn't work with Geofencing.

I did set up routines that arm/disarm the system as I approach the location and it now seems to work correctly.
The camera is armed/disarmed automatically as I approach or leave the geofencing area, I can see all the activity in the feed. So far it seems to be good.

Took me a while to understand how to set it all up because the app is, frankly, poorly designed. At least around the routines, and it's not very clear how to set them up at first, you get a lot of (inexplicable) empty states for cards/lists and items that seem to be "tappable" (clickable) but unresponsive. Margin for improvement over the routines/modes section.

[jguerdat]

---

@er-minio wrote:

Update: I was able to make this work. I have no idea why it has been said that the first gen Arlo Go doesn't work with Geofencing.

---

I suspect you did this using the standard modes and Automations. It's the custom modes and Automations that don't work for the Go, Q, etc.

[er-minio]

Ah yes. It is using standard modes (the top three choices).

Again: fairly complex to understand how to set it up, so I decided to completely ignore the custom modes options.

The camera is still going strong after several years in operation and very happy with the hardware, but as soon as the hardware fails I'll move away from the Arlo ecosystem to be fair. But I suspect it won't be anytime soon. 🙂

[StephenB]

---

@er-minio wrote:

I decided to completely ignore the custom modes options.

Well, you need to use custom modes with the original Go.  So maybe ignore the three standard modes instead.

[er-minio]

It is working with the standard modes and the automations I set up.

---

@StephenB wrote:

---

I suspect you did this using the standard modes and Automations. It's the custom modes and Automations that don't work for the Go, Q, etc.

---

---

@StephenB wrote:

---

@er-minio wrote:

I decided to completely ignore the custom modes options.

Well, you need to use custom modes with the original Go.  So maybe ignore the three standard modes instead.

---

Do custom modes work or not with the original Go?
I am confused now.

But, again: the set-up is working at the moment using the standard modes and making them switch through the geofence (arrive/leave action).

[StephenB]

---

@er-minio wrote:

But, again: the set-up is working at the moment using the standard modes and making them switch through the geofence (arrive/leave action).

---

Sorry for posting contradictory info.  Some cameras aren't supported at all in custom modes (and don't appear in the custom modes camera list).  Others have limitations in the standard mode.  I think this is a bit of a moving target though.

If the system is working for you now, then leave well enough alone.

[er-minio]

No problem Stephen! Thanks for the help.

Yes, I'll test it a bit more, but the setup seems stable for now.
I can see what you mean: with multiple cameras it could be a bit of an issue (what the ArloGo is compatible with and what not) but in my single camera set-up we should be ok.

Fingers crossed 🙂