Arlo Pro camera disconnects with battery change

[mookie60]

Is there a way to replace the battery in an arlo pro camera WITHOUT needing to disconnect/reconnect the camera to the base station?

Just did my first Arlo Pro battery change.   For the first camera, I just did what the instructions said - just swap the batteries. The camera disconnected from the base station and would not reconnect.   I needed to go to that camera (in the app) and select "remove device", physicall bring the camera to the base station, take out the battery for 10+ seconds, and re-add the device using the normal method.    For the second camera, I tried disabling the camera first (in the app), then swapping with a fresh battery - the same thing happened.

Surely there must be a way to change a battery without needing to disconnect/reconnect the camera with the base station, each and every time.  In my case, the base station is located up and out of the way, so changing a battery now becomes a two ladder job.

[Matchpoint]

I just replaced the battery of my 3 cameras yesterday and I did not have to do what you were saying. Just removed the discharged battery pop the charged one in and focus the camera to the right direction and that's it. This is the second time I have done this and I never had any problem. I think you are probably accidentally pressing the off-line button that causes the camera to be disconnected, you just have to press that button again and it should go on-line.

[Streak2]

I can confirm that after a battery change the camera will automatically reconnect.

I have done this countless times across all version of Arlo cameras and they always reconnect without having to resync.

[mookie60 · Accepted solution]

Well on the next two cameras, all worked exactly as it should:  just took out the existing battery and replaced with a fully charged one.   And it automatically reconnected.

I see where I did anything different, or that I had mistakenly touched the sync buttons on the first 2 cameras; yet I can't conclusively say that didn't happen.   So I'll happily chalk it up as some kind of user error, and hope it always works as it should.

Thanks for the quick replies