Recent firmware updates make my camera batteries die in 24 hrs

[TisTheMc]

I recently updated to the latest firmware and app. Now my camera batteries drain in 24hrs or less. Charging timeline:

• Friday 07/12/24 8am - full charge

• Saturday 07/13/24 4:32 am - receive an email notification that my Arlo camera batteries are low

• Saturday 07/13/24 8am - fully charged

• Saturday 07/13/24 6:23pm - receive an email notification that my Arlo camera batteries are low

I regret updating and wish I knew how to roll back to the previous version. Everything was running fine on that version. Now I’m ready to move to Ring or Eufy. Anyone know how to roll back your versioning or resolve this issue in the update?

*Side note to the product team for Arlo: who’s writing this trash code and what’s your QA team doing? This is a critical bug that’s costing you money and ultimately making you guys/girls look like amateurs. @Vp of product - do better!!

[DannyBearAgain · Accepted solution]

What app display type do you have? Do you have a library or a feed?

If you have upgraded to the app with the feed page your stuck unfortunately.

All I can suggest is the scorched earth approach to remove cameras and base from the arlo account, factory reset the base, remove the camera batteries for 10sec and start adding the devices back as new.

[TisTheMc]

Thanks for the reply!!

Unfortunately, I updated to the version with the feed. Looks like it’s scorched earth time. By scorched earth I mean burning my Arlo system and moving onto a much better camera system; unless there’s an easier fix.

[DannyBearAgain]

There has been mentioned recently that arlo can perform a back end sync action but unable to determine if this fix will work for you.

I can flag a forum moderator to chime in to make them aware.

@ShayneS , @JamesC, @BrookeN 

[ShayneS]

Hi @TisTheMc 

Are you still experiencing this battery drain? Is it occurring on all your devices?

[TisTheMc]

I was able to resolve the issue last night by using the scorched earth method Danny mentioned. It seems to have resolved the issue. Thanks to you and @DannyBearAgain for the help!