I hear you — when a camera starts rebooting right after a router change, it feels like something is “broken,” but it’s often one setting mismatch.

Before we try anything risky, let’s do the safest checks first. I don’t want you to factory-reset the camera or change a bunch of settings if we can avoid it.

A few quick details help narrow this down:
• Is it a Wi-Fi camera (no base station), or does it connect through a hub/NVR?
• What changed: brand-new router, new mesh system, or just a new Wi-Fi name/password?
• When it reboots, do you see a repeating pattern (every few minutes), or only when it tries to reconnect?
• Do other smart devices stay stable on the new network?

That’s completely fair — we’ll keep this gentle and reversible. We’ll focus on checks that won’t disrupt your whole network.

Two common “after a new router” triggers for cameras are:
1) Wi-Fi compatibility (camera prefers 2.4 GHz, WPA2, and can get upset by WPA3-only or band steering).
2) Network handoff issues (the camera keeps getting a new IP address, or it can’t reliably reach the gateway/DNS, so it restarts while trying to reconnect).

First question: on your router, do you have one combined Wi-Fi name for 2.4 and 5 GHz, or are they separate?

Got it. With a single Wi-Fi name, some cameras “bounce” between bands or struggle when the router tries to push them to 5 GHz. That can look like random restarts, especially in a back room where 5 GHz is weaker.

Let’s confirm what the camera is actually doing without changing anything yet:
• In the camera app, does it show offline before the reboot, or does it just suddenly restart?
• If you can, look at the router’s device list: does the camera appear and disappear frequently, or does it stay listed but with changing details?

Trust moment: we’re not touching your internet settings yet — we’re just observing the pattern.

That helps a lot. Two things stand out:

• Changing address numbers can mean the camera keeps getting a new IP lease (not always a problem, but it can be if the camera is picky).
• WPA3 can be great, but some older IoT cameras behave poorly if the network is WPA3-only or if “WPA3 transition” is buggy on certain routers.

We can check this safely:
1) See whether your Wi-Fi security mode is WPA2, WPA2/WPA3 mixed, or WPA3 only.
2) Confirm the camera is on 2.4 GHz (most Wi-Fi cameras strongly prefer it).

I’m not asking you to switch anything permanently right now — just tell me what your router shows for the Wi-Fi security setting.

That “stable before, unstable after” strongly points to an environment change rather than camera hardware failing overnight.

Three safe suspects after a router swap:
A) WPA3-only security (camera can’t maintain a clean handshake).
B) Band steering / Smart Connect (camera keeps getting nudged away from 2.4 GHz).
C) Weak signal in that back room (the camera drops, retries, and some models reboot when connection fails repeatedly).

Quick safety check: is the camera powered by a wall adapter, USB, or PoE? And is it plugged into the same outlet/adapter as before?

Power absolutely can be part of this — and it’s a safe thing to rule out. Longer USB cables and weaker adapters can cause brief voltage drops. Some cameras respond to that by rebooting, which looks exactly like a network issue.

Another trust moment: I don’t want you to climb ladders or do anything unsafe. Simple, at-home checks only.

Two gentle tests (no “big changes”):
• If possible, try the original shorter cable/adapter for a while, just to see if reboots reduce.
• Keep the camera close to the router temporarily (even for one hour) to see if stronger signal changes the behavior.

If reboots stop near the router, that points to Wi-Fi coverage or band steering. If reboots continue even with strong signal, power or security mode becomes more likely.

Not dangerous — it’s just the router handing out “local addresses” to devices. But frequent changes can confuse some cameras, especially right after a new router install.

Here’s what we look for (still safe):
• Does the camera get a normal local IP (often starts with 192.168.x.x or 10.x.x.x)?
• Does it keep switching between two addresses (possible conflict), or does it change after each reconnect (short lease time)?

If your router offers it, an IP reservation for the camera can make behavior more predictable. You don’t need to do it right now — I just want to confirm whether your router has that option.

It can matter, yes — but in a “rules and access” way, not in a scary way.

Some IoT/Guest networks use client isolation or stricter firewall rules. That can interfere with setup, app discovery, or cloud handshakes on certain camera models. It can also behave differently with band steering.

A safe way to think about it:
• If the camera is stable on your main 2.4 GHz network, then we know isolation rules were part of the issue.
• If it’s unstable everywhere, we focus back on WPA3-only, weak signal, or power.

One more key question: did you reuse the same Wi-Fi name/password from the old router, or is this a new network name?

Yes, repeated setup attempts can leave a camera in a “half-provisioned” state — it keeps trying to join, fails, reboots, and repeats. That’s especially common right after a router change when security mode/band choice isn’t what the camera expects.

We’re still staying Google-safe here: no risky hacks, no hidden menus, no tearing anything open.

The clean diagnostic approach is to confirm these basics first:
• 2.4 GHz available and strong where the camera sits (not just where the phone is).
• Wi-Fi security compatible (many cameras prefer WPA2 or WPA2/WPA3 mixed).
• No isolation rules blocking the camera’s normal connection behavior.
• Power stable (shorter cable / known-good adapter as a test).

If those look good and the reboot loop persists, then a careful “remove from app and re-add” becomes the least messy next step — but only after we rule out the simple causes.

Totally reasonable. Here’s a “look-first” checklist — no changes required unless you choose to:

1) Wi-Fi bands: confirm your router actually broadcasts 2.4 GHz (some setups hide it under Smart Connect).
2) Security mode: see if WPA3 is set to “only.” If there’s a mixed WPA2/WPA3 option, that’s often more camera-friendly.
3) IoT/Guest rules: check whether “isolation” is on for the network the camera uses.
4) Device list: note if the camera’s IP keeps changing after every drop.

If you tell me the router brand/model (and whether it’s mesh), I can point to the exact screen names to look for — without you changing anything blindly.