Pool Robot App Keeps Disconnecting: Staying Paired

Denise reset her pool robot’s Wi-Fi eight times over one summer, every Sunday like clockwork, because the app lost it by Wednesday without fail. Eight factory resets, eight re-pairings, eight trips back through the setup screen on her phone.

The actual fix took four minutes in her router’s settings page once she finally called instead of resetting again: a reserved address for the robot so it stopped losing its spot on the network every time the router rebooted overnight. She had spent a season fixing the symptom and never once touched the cause.

That mistake is common enough that it deserves its own diagnostic path, separate from a robot that never paired in the first place. If yours paired fine once and now will not stay put, work through the causes below in order rather than reaching for another reset.

Two different problems that both look like disconnecting

Before chasing a fix, figure out which of two things is actually happening. The first is a real network drop: commands stop reaching the robot, and status genuinely goes stale.

The second is a cloud or session glitch: the app shows offline, but the robot is still running its saved schedule on its own internal clock, cleaning right on time with nobody watching. These look identical from the couch and have completely different fixes, so the first job is telling them apart.

Symptom: disconnects a few minutes after every reconnect

If reconnecting works but the pairing dies again shortly after, almost every time, work through these in order of likelihood.

1. DHCP reassigning a new IP address to the robot after a router reboot, breaking the app’s saved connection to the old one.
2. Weak signal at the edge of range, causing the link to connect, wobble, and drop in a repeating cycle.
3. An overnight router auto-restart, common on ISP-supplied hardware, that briefly drops every device on the network on a fixed schedule.
4. Interference from a nearby pump motor or other equipment sharing the same electrical run as the router.

Notice that none of these four is the robot’s own hardware. A pattern this regular is almost always something on the network side repeating itself on a schedule.

The DHCP fix that solves most recurring drops

Most home routers hand out temporary addresses through DHCP, a lease system that can quietly reassign a different address to the same device after a reboot or a long enough gap offline. The app, meanwhile, may have cached the old address, and the handshake fails until something re-syncs.

A DHCP reservation fixes this permanently by locking one specific address to the robot’s hardware ID, so it gets the identical address every single time, reboot after reboot.

Symptom: disconnects randomly, hours or days apart

A looser, less predictable pattern points to a different set of causes, ranked by how often they turn out to be the culprit.

1. A mesh Wi-Fi system handing the robot between nodes as it hunts for the strongest signal, briefly dropping the session during the handoff.
2. Router firmware updating itself overnight and rebooting without warning.
3. A brief ISP outage that never quite counts as a full internet blackout but still knocks devices loose.
4. Another device on the network hogging bandwidth during the exact window the robot tries to check in.

Mesh systems deserve a specific note. They are genuinely good at range, but node roaming can behave like a small network event every time it happens, and a robot mid-cycle underwater is a bad moment for that handoff to land. Some mesh apps let you pin a device to one node instead of letting it roam, which is worth doing for anything as connection-sensitive as a pool robot.

Symptom: the app says offline, but the robot keeps cleaning on schedule

This is the good version of the problem, and it is worth recognizing so you stop worrying about it. The cleaning schedule lives on the robot itself, not in the cloud, so a lost app connection does not pause a single cycle.

What is actually broken here is usually the phone side: a stale app cache, an expired login session, or a background process that quietly stopped refreshing. Clearing it is simple.

• Force-quit the app completely, not just switch away from it, then reopen it.
• Log out and log back into the account rather than trusting a saved session.
• On Android, clear the app’s cache specifically, which is gentler than a full data wipe or reinstall.
• On iPhone, offload the app through settings, which clears its cache while keeping your login.
• If none of that helps within a few minutes, a full reinstall resets everything cleanly.

When it is the robot’s firmware, not your network

Occasionally a firmware update genuinely regresses connection behavior, and every owner on that version starts seeing drops around the same time. This is less common than router causes but worth ruling out, especially if the disconnects started right after an update notification.

Check the app’s changelog or support page for anything mentioning connectivity or pairing fixes in a more recent release. If one exists, updating is the fix; if your version is already current, the firmware is probably not the source this time.

Matching symptom to fix, at a glance

The permanent fixes worth setting up once

A handful of small, one-time changes prevent most of this from ever recurring. None of them take longer than a few minutes each.

• Set a DHCP reservation for the robot’s address in your router settings.
• Check for and disable an inconvenient overnight auto-reboot schedule, or move it to a time the robot never runs.
• Pin the robot to a single node if you run a mesh network rather than letting it roam.
• Keep both the app and the robot’s firmware reasonably current, without skipping more than a version or two.
• Rename your Wi-Fi bands separately so future troubleshooting never has to guess which one the robot actually joined.

Where to go from here

A robot that paired once and now will not stay connected is a network puzzle far more often than a hardware failure. Work the symptom, not the panic: match the pattern, try the ranked cause in order, and resist the urge to factory reset before you have ruled out a DHCP reservation.

Fix the actual cause once, the way Denise eventually did, and the app stops being something you have to fight with every few days. It goes back to being a status screen you check out of habit, not necessity.

Frequently asked questions

Will factory-resetting the robot fix a recurring disconnect?

Usually only temporarily. A factory reset clears the robot's saved credentials and forces a fresh pairing, which often works again for a while, but if the root cause is a router setting like DHCP reassignment or an overnight reboot schedule, the same disconnect returns days later. Fix the network-side cause first and save the reset for when nothing else has worked.

Would switching to a mesh Wi-Fi system fix constant disconnects?

Sometimes, and sometimes it trades one problem for another. Mesh systems genuinely improve range and can solve a weak-signal cause, but node roaming introduces its own brief handoffs that can look identical to a dropped connection. If you already run mesh, pinning the robot to a single node usually helps more than adding another one.

Can my internet provider's router cause this on its own?

Yes, more often than owners expect. ISP-supplied routers frequently auto-update firmware or reboot on a fixed overnight schedule that briefly drops every connected device, robot included. Log into the router's admin page and check for a scheduled maintenance window; moving or disabling it, where the ISP allows changes, removes a genuine and common cause.

If my phone keeps losing the robot but another phone on the same network does not, is that the robot's fault?

No, that points at your phone. Devices sometimes switch between Wi-Fi bands or fall back to cellular data when a signal dips slightly, which breaks a local app session without the robot doing anything differently. Forcing your phone onto the 2.4GHz band and disabling Wi-Fi assist or similar cellular fallback features usually resolves it.

How often should a normally paired robot briefly drop connection?

Rarely enough that you barely notice, maybe a momentary blip during a router hiccup once every few weeks. A robot that loses connection daily, or that needs a manual reconnect more than once a week, has crossed from normal radio behavior into an actual problem worth diagnosing with the steps above rather than living with.