Camera Won’t Reconnect After a Router or ISP Change

A WiFi camera usually stops working after a router or ISP change for one boring reason: it still holds the old network name, password, band, or address scheme. The camera itself is usually fine. It’s looking for a network that no longer exists the way it used to. Either re-add it to the new WiFi, or make the new gear impersonate the old network so you don’t have to touch every device in the house.

If your cameras are wired into an NVR or a PoE switch, you’re in a different situation — those often keep recording locally while only remote access breaks. This article is for cameras that reach the house network over wireless.

What actually broke

A camera that was solid for two years does not suddenly hate the new router. It was provisioned once — SSID, password, sometimes a band, sometimes a fixed address expectation — and that memory did not update when the box in the closet changed.

Common causes, roughly in the order we see them:

• New SSID or password. ISP techs and new routers ship with their own network name. The camera keeps trying to associate with the old one.
• A band split you didn’t have before. Old gear may have presented one combined network. New gear shows “Home” and “Home-5G,” or steers your phone to 5 GHz while the camera is 2.4 GHz only.
• New gateway, new LAN range. The old network was 192.168.1.x; the new one is 192.168.0.x or 10.0.0.x. Cameras with a static IP — and apps caching the old address — stop finding anything.
• Guest network or AP isolation. Some ISP gateways park IoT devices on a “smart home” SSID that can’t talk to phones on the main network. The camera has internet; the app never sees it on the LAN.
• Mesh or extender handoff. After a swap a camera may latch onto a weak node, or join before the backhaul is settled.

In the app the symptom always looks the same — offline, “last seen yesterday,” “device not found.” The cause is almost always credentials, band, or addressing, not dead hardware.

Quick triage table

The cleanest fix: keep the same SSID and password

If the swap isn’t finished — or you can still edit the new router’s WiFi settings — do this first. Set the new router’s primary WiFi name and password to exactly what the old network used: same spelling, same capitalization, same password. If any of your cameras is 2.4 GHz-only (check the spec), prefer a single SSID serving both 2.4 GHz and 5 GHz, because a 2.4 GHz-only camera will never see a 5 GHz-only name.

Then power-cycle the cameras once the router is up: pull power for roughly 30–60 seconds (that window assumes a typical plug-in or PoE camera; it’s just long enough to clear the radio state, not a magic number), and give them a few minutes to rejoin. A surprising number come back without your opening an app at all.

The trade-off, said plainly: matching the old SSID and password saves hours of re-adding every bulb, lock, plug, and camera. The cost is that you’re carrying forward a password you may have wanted to retire. If it was weak or widely shared, change it on a weekend when you can re-provision on purpose — not the night the ISP truck leaves. And if the gateway is locked down so you can’t match the old name, you’ll re-add. That’s normal. Plan for it instead of fighting it at 10 p.m.

Step by step: re-adding a WiFi camera

Button names differ by brand; the sequence doesn’t.

• Start with the phone on the right WiFi. The same 2.4 GHz or combined network the camera will use — not cellular, not a guest SSID, not the 5 GHz-only name. Turn off VPNs for setup.
• Next, remove the stale device entry if the app offers delete/remove on the offline camera. A ghost entry can block a clean re-pair. Removing it from the app is not the same as factory-resetting the camera; you often need both.
• Then factory-reset the camera the way that model expects — usually a pin or button held until a voice prompt, LED pattern, or pan/tilt sweep says it’s ready. Wait for that ready state. Resetting mid-boot causes half the “app can’t find it” complaints.
• With that done, add the device in the app and follow the QR code, blink pattern, or temporary camera hotspot. When it asks for WiFi, pick the 2.4 GHz or combined network and type the password carefully — correct case, no trailing space.
• Stay close while pairing. Setup is far less forgiving than day-to-day streaming. Work within a few feet of the camera — call it roughly 3–10 ft as a working range, and closer still for QR-scan models that want the code nearly against the lens. A camera on a far eave that “worked fine before” may need to come inside for pairing, then go back up.
• Once it connects, let the firmware check finish. Don’t yank power mid-update.
• Finally, verify live view twice — once with the phone on the same WiFi, once on cellular. Local working but remote failing (or the reverse) points at different problems, per the table above.

With several cameras, finish one completely before starting the next. Parallel resets with one phone produce crossed QR scans and wrong SSIDs more often than people expect.

When the app still won’t find the camera

Work this in order; skipping around wastes time.

Ready state. No setup LED or voice cue means the app has nothing to discover. Reset again and wait for it.

Phone quirks. iOS and Android both love auto-joining the 5 GHz name. Some phones also need “private WiFi address” / MAC randomization disabled for that SSID during setup, so the router stops treating the phone as a brand-new device each session.

Router features that block setup. Temporarily disable AP/client isolation, guest mode on the main SSID, and Smart Connect if it’s steering phone and camera different directions. Pause or whitelist MAC filtering. Security appliances doing deep packet inspection sometimes break the brief hotspot or P2P handshake — relax it for ten minutes if setup keeps dying at “connecting to device.”

Band and channel width. A 2.4 GHz-only camera fails on a 5 GHz-only SSID, and can also struggle when the 2.4 GHz radio is pinned to 40 MHz in a crowded neighborhood. 20 MHz on 2.4 GHz is the boring setting that usually works. Auto channel is fine to start; if joins keep failing, fix a quieter 2.4 GHz channel.

Old static IP or reservations. A factory reset returns the camera to DHCP. On the router side, delete stale DHCP reservations tied to the camera’s MAC on the old subnet so you’re not fighting ghosts.

App and account. Force-close, update, try a second phone on the same WiFi. Confirm you’re logged into the account that owns the device — shared-home and co-admin setups sometimes need the primary account to release the camera first.

If live view flakes after a successful re-add, stop treating it as a router-swap mystery and work it as a disconnect pattern: signal, interference, power, and band steering. That’s the WiFi camera disconnecting diagnostic.

ISP swap specifics

• Bridge vs router mode. Double NAT — ISP modem-router plus your own router — can break discovery and remote access even when WiFi credentials are perfect. Have one device doing NAT: bridge the ISP box and use your router, or use the ISP gateway alone.
• CGNAT. Some ISPs put homes behind carrier-grade NAT. Local viewing on the same WiFi still works, and brand apps using their own relay usually still connect; port forwards and DIY remote paths won’t. That’s an ISP routing issue, not a bad camera.
• The “upgrade” that renamed your WiFi. Ask the tech what SSID they left. Match it back if you can; otherwise budget re-add time.
• “IoT network” toggles. Read what they isolate before parking cameras there. Isolation is sensible for untrusted gadgets and a poor fit for an app that expects LAN discovery.

Mistakes we see

• Buying replacement cameras. Hardware that worked yesterday is rarely the failure the afternoon an ISP swap finished.
• Pairing on 5 GHz because the phone shows better bars. Your phone’s bars aren’t the camera’s radio.
• Renaming the SSID “for security” the same night as the hardware swap. Now you have two problems. Stabilize with the old name, rename later.
• Skipping the factory reset and wondering why the camera is still hunting for SmithHome_old.
• Updating firmware over a marginal link mid-move. Finish the join, confirm stable power and signal, then update.

After it’s working

Give it a week that includes evening congestion and some weather. Confirm recordings and event history still land where you expect — a clean re-join is not the same as a durable design. If you lean on cloud features, know what happens when the WAN drops; some cameras buffer little or nothing without internet.

Then write down the SSID, the password, and which band each camera uses. Future you, or whoever maintains the house next, shouldn’t have to reverse-engineer it from a ladder.

We haven’t personally walked every brand’s latest app flow, and button labels move. The underlying failure mode doesn’t: the camera trusts the old network story until you hand it a new one, cleanly, on a band it can actually use.

FAQ

Why did all my cameras die after the new router when phones were fine?

Phones prompt you for the new password and happily join either band. Cameras hold silent credentials until you reset and re-add them — or until the new router impersonates the old network with the same SSID and password.

Should I use the ISP’s “smart home” or guest WiFi for cameras?

Only if you understand its isolation. If that SSID blocks client-to-client traffic, setup and local app discovery often fail even though the camera has internet. A dedicated IoT SSID without isolation, or the main LAN with strong passwords, is usually less painful for cameras you view from your phone at home.

2.4 GHz or 5 GHz after a router change?

Use what the camera supports; some models are 2.4 GHz-only, so check the spec. As a qualitative guide rather than a promise: 2.4 GHz typically holds a usable camera link farther indoors through one or two interior drywall walls than 5 GHz does under those same conditions. Reach varies widely and assumes a single decent access point, ordinary residential construction, and moderate neighbor congestion. Masonry, foil-backed insulation, metal siding, or a busy apartment band pushes you toward marginal or unusable. Wall count and AP placement matter more than any number on the box.

I matched the old SSID and password; one camera still won’t come back.

Factory-reset that unit and re-add just that one. It may be holding a static IP, a corrupted network profile, or a mesh node preference that didn’t survive the swap. One stubborn camera is a reset job, not a reason to re-provision the whole house.

Will a router change delete my recordings?

Local microSD footage normally stays on the card. Cloud history depends on the account and service, not the router. Verify retention in the app once the camera is back rather than assuming.

How is this different for wired cameras?

PoE cameras recording to an NVR on the LAN usually keep recording while you sort out remote access, so the fix order is different.

Do I need a new camera?

Rarely, if it was reliable before the swap. Full reset, correct band, close pairing. Replace only after the network side is boring and stable and the same unit still fails in a known-good location on known-good power.