topic Re: At a loss, The Request Has Timed Out in Arlo Pro 2

At a loss, The Request Has Timed Out

Spookay — Wed, 18 May 2022 17:20:49 GMT

Hello all,

Today one of my Arlo cameras suddenly stopped recording video and will not live stream. I have attempted to live stream on my iPhone and my laptop, but I receive the message "The Request Has Timed Out." Also, I receive notifications that motion has been detected on the camera, however, there is no video in my library. I have checked the library using both my iPhone and on my laptop, and there is no video recording.

Here is the basic info:

*Camera is an Arlo Pro 2

-- Firmware version 1.125.17.1_11_de8490d

-- Wireless connection is strong

-- Unit is plugged into a power source

-- There is no damage to the camera

-- There has been no adverse weather (sunny and in the 70s)

-- The camera's last recording was approximately 24 hours ago

Here are the troubleshooting steps I have tried so far:

-- I have turned the camera off, removed the battery, waited 5 minutes, powered the camera back on

-- I have removed all of the activity zones

-- I have disarmed the camera

-- I have attempted to live stream using the "Camera Positioning" feature

-- I have attempted to trigger a recording by having this camera record when another camera detects motion

-- I have moved the camera closer and tested in different proximities

I am at a loss. This just started happening today. My last recording was approximately 24 hours ago.

-- I have removed and re-added the camera to the system.

I'm at a loss and any help/suggestions would be greatly appreciated.

Re: At a loss, The Request Has Timed Out

StephenB — Wed, 18 May 2022 19:12:28 GMT

Does anything change if you disconnect the camera from the power source?

Re: At a loss, The Request Has Timed Out

Spookay — Thu, 19 May 2022 14:41:36 GMT

No, nothing changes. I've unplugged, removed the battery, swapped batteries (not sure why that would impact it, but figured why not) and plugged/powered it back on several minutes later.

Re: At a loss, The Request Has Timed Out

StephenB — Thu, 19 May 2022 17:43:39 GMT

Not sure if you've answered this already...

Have you tried livestreaming from the main page (not camera positioning)?

If that works, are you able to save a manual recording during the livestream?

Re: At a loss, The Request Has Timed Out

Spookay — Thu, 19 May 2022 21:07:47 GMT

I have tried this, with no luck.

The only time I am able to catch even a small glimpse of a "live" view is when I add/remove activity zones. When I do this, I'm presented with a snapshot of what is happening on that camera in that moment.

Outside of this, I am not able to view anything. Previously, I was receiving motion notifications, however, those have now ceased.

Re: At a loss, The Request Has Timed Out

Spookay — Thu, 19 May 2022 21:08:46 GMT

UPDATE - For what it's worth, I was previously receiving motion notifications (no video though), however, those have now ceased. Everything else remains the same.

Re: At a loss, The Request Has Timed Out

StephenB — Fri, 20 May 2022 11:39:30 GMT

@Spookay wrote:

UPDATE - For what it's worth, I was previously receiving motion notifications (no video though), however, those have now ceased. Everything else remains the same.

Have you tried restarting the base?

You could also try removing the camera from your account, and then re-adding it. It might fail to onboard, but given that it's not working you don't have much to lose.

Re: At a loss, The Request Has Timed Out

Dannybear — Fri, 20 May 2022 21:10:16 GMT

You should also try plugging the charger into the camera to see if live streaming starts working again.

Re: At a loss, The Request Has Timed Out

Spookay — Sun, 22 May 2022 13:50:30 GMT

After several days of no recordings and no motion alerts, my camera suddenly started working this morning. As I was drinking my morning coffee, I received a motion alert on the camera I was having issues with. I checked the alert and there was also a recording. The camera once again records, live streams, and otherwise functions as it should.

I wish I could pinpoint what caused the issue and what corrected it, but I give up. It is working, for now.

Thank you to everyone for the suggestions and support!