topic Re: Arlo Local storage with Hub 4540 - User Experience needs an update in Arlo Video Doorbell 2nd Gen

Arlo Local storage with Hub 4540 - User Experience needs an update

Noswalz87 — Wed, 15 Jan 2025 14:24:03 GMT

I have a second Gen Doorbell and plan on getting some essential cameras as well. While the local storage settings work with the hub I have 4540, the app experience needs some basic/simple updates to ease the access to local storage events.

When an event happens and you go to the "Feed" tab, No local storage option initially shows up. You have to refresh it a few times to even see "Local" storage versus "Cloud".

Once you are under the "Local" storage, no videos show up after an event. You have to actually go over to the devices tab and select your hub and then "storage settings" to see the recordings. Once you do that you can actually go back to your "feed" and they will now show up under local, but only after you've gone all the way through storage settings first. This seems pretty inefficient and a simple app update to the UI to fix the bug here would be great. When does Arlo plan on updating this?

Re: Arlo Local storage with Hub 4540 - User Experience needs an update

jguerdat — Wed, 15 Jan 2025 14:59:39 GMT

Edit: and now it's working...

I'll go you one better - I just tried this on Android and can't see local recordings under Local at all (There are no events for this day). Going to the hub's Storage Settings displays all videos properly but going back to Feed/Local still results in no videos (and no calendar icon).

@JamesC , @ShayneS , @BrookeN can you tell us what's up?

Re: Arlo Local storage with Hub 4540 - User Experience needs an update

Noswalz87 — Wed, 15 Jan 2025 15:42:12 GMT

Yeah while buggy, eventually the local storage tab shows up but after multiple refreshes. There is never any new videos there until first going to storage settings to see them. Arlo needs to fix this asap. It is a simple fix and I actually saw a topic from 6 months ago or so with an arlo support person replying with this work around. Clearly Arlo knows about it but has not fixed it yet. Is there just no incentive to update this to keep people subscribed to the monthly cloud service?