Arlo|Smart Home Security|Wireless HD Security Cameras

Reply
Discussion stats
  • 5 Replies
  • 1036 Views
  • 0 Likes
  • 5 In Conversation
AdamZuck
Aspirant
Aspirant
The Arlo app and the website portal are both telling me to update the firmare on my Arlo Pro 3 Floodlight.
 
Here's the message: "The update process can take up to five minutes. Make sure your device is uninterrupted during the update process. Do you want to update your Back Yard to 1.080.27.0_25_82bc6f2?"
 
When I click continue on the app, it says "Firmware Update in progress" and that it may take up to 5 minutes. It then spins back to the regular screen where it say an update is available.
 
Endless loop. Any ideas? I've tried removing and resetting the camera. Same challenge on repeat.
5 REPLIES 5
jguerdat
Guru Guru
Guru

Are you in field trials (kinda like the beta program but not really) that would get firmware updates before anyone else? The latest released firmware for the floodlight is 1.080.26.5_58_3b3ef75 (see https://community.arlo.com/t5/Firmware-Release-Notes/bd-p/arlo-release-notes and look for the Pro 3 floodlight) - is that what version is already installed?

Kproto
Aspirant
Aspirant

This is happening to me as well on my Arlo Pro 4 … not sure what to do.

 

jguerdat
Guru Guru
Guru

Try rebooting the router and/or hub (if so connected). Reboot the camera if connected to WiFi or reinsert the battery to get to known settings. Worst case, remove the camera from your account and add it back in.

StephenB
Guru Guru
Guru

You could also just wait a day or so, and see if the firmware updates on its own.

hisen22
Aspirant
Aspirant

Yes I spent several days trying repeatedly to update the firmware on one of my three cameras. Turns out while it was showing 85% battery it was actually totally dead. When I brought it in (after restarting the base station to be sure), plugged it in, charged it fully, and tried again it finally worked. First time this has ever happened and my bf was about to throw the whole kit in the fire after so many failed attempts. Seems to be working after this “fix” though. Not sure if that will help, just wanted to let you know I did have a similar issue recently.

Discussion stats
  • 5 Replies
  • 1037 Views
  • 0 Likes
  • 5 In Conversation