Robot Vacuum App Not Connecting? Work Out Which Link Is Broken

Why won't my robot vacuum connect to the app?

A robot vacuum won't connect to the app because one of three links has failed: the direct phone-to-robot link used during setup, the robot-to-router Wi-Fi link that carries everything afterwards, or the internet link between your router and the manufacturer's servers that the app relies on. Owners tend to treat these as one problem called "the app", and so they reinstall the app when the robot has simply parked itself in a Wi-Fi dead spot, or factory-reset the robot when the brand's cloud is having an outage. The robot's own behavior tells you which link is down, and the table below reads that behavior back to you.

Why does setup fail at the Wi-Fi step?

Setup fails at the Wi-Fi step because the robot only speaks 2.4GHz and your phone is handing it a 5GHz network, or a combined network that the robot cannot separate. Almost every robot vacuum sold today, including flagships costing over a thousand dollars, has a 2.4GHz-only radio, because it reaches further through walls and the robot never needs bandwidth. Modern routers, meanwhile, default to a single network name that covers both bands and steer devices to 5GHz whenever they can. During pairing the app copies whatever network your phone is on, and if that is the combined name, the robot may get the 5GHz credentials or fail to negotiate the band at all. Our Wi-Fi guide explains the radio side in detail; here is the practical sequence.

Log in to your router and give the 2.4GHz band its own network name, something like "Home-2G". Connect your phone to that network, run the pairing again, and switch your phone back afterwards. The robot keeps the 2.4GHz credentials permanently. If your router or mesh system does not allow separate names, most have a temporary option to pause 5GHz for a few minutes for exactly this purpose; eero, Google Wifi and Deco all do. Failing that, stand the robot and your phone within two or three meters of the router during setup, since a strong signal makes the negotiation more forgiving.

Two smaller causes catch people at this step. The first is the password: robots are strict about case and special characters, and a password with a space or an emoji in it will fail on some models. Type it into a note first and paste it. The second is the network name itself: hidden networks, names with unusual characters, and enterprise-style WPA3-only security all block older robot radios. Setting the router to WPA2/WPA3 mixed mode fixes the last one without weakening anything.

Why can't the app find the robot during pairing?

The app can't find the robot during pairing because the direct phone-to-robot link never opens, and that link needs three things on the phone side that people rarely think about. The robot must be in pairing mode, which on most brands means holding two buttons until the Wi-Fi light blinks and the robot says so; a robot that has previously been paired will not advertise itself again until you do this. The app must have Bluetooth permission and, on both iOS and Android, location permission, because the operating systems treat scanning for nearby devices as a location function and silently return nothing without it. And any VPN or private DNS on the phone must be off, because the app is trying to reach a device on your local network and the VPN routes that request elsewhere.

Check those three, restart the app, and try again with the phone held close to the robot. If the app still sees nothing, the robot may be using a temporary hotspot rather than Bluetooth for pairing, which older Roborock, Xiaomi and eufy models do. In that case open the phone's Wi-Fi list, look for a network named after the robot, join it, and return to the app. Our setup guide covers the hotspot flow step by step for each brand.

Why does the app say the robot is offline?

The app says the robot is offline because the robot has lost its connection to your router, and that almost always comes down to where the dock sits. A robot spends its life parked on the dock, so the dock's location decides its signal. A station tucked behind a sofa in the far corner of a flat, or in a utility room with a metal door, can sit at the very edge of the router's 2.4GHz range and drop off every few hours. The give-away is that the robot still runs its scheduled cleans, because the schedule is stored on the robot, but the app shows it offline between them and remote commands fail. Watch the robot's Wi-Fi indicator: blinking means it is trying to reconnect, solid means it is connected and the problem is upstream.

Move the dock, or move the signal. Even a couple of meters can take the robot from a marginal signal to a solid one; our dock placement guide puts Wi-Fi reach alongside the other siting rules. If the dock cannot move, a mesh node or extender near it fixes it, with one caveat covered below. Also log in to the router and look at the device list. Some routers have a cap on connected devices, some apply parental-control schedules to unknown devices, and some quietly assign a new address that the robot does not pick up until a restart. If the robot appears in the list but the app still says offline, restart the robot itself by holding the power button for ten seconds; it forces a fresh connection and clears a stuck state more often than any other single step.

Persistent drops after you changed anything on the network mean the robot has stale credentials. New router, new password, a mesh upgrade that changed the network name, even a firmware update on the router that toggled a security mode: all of these leave the robot trying to join a network that no longer exists as it knew it. The fix is to re-pair the robot through the app, not to factory-reset it. Re-pairing keeps your map, rooms and schedules; a factory reset throws them away, and if the map has taken weeks to get right, that is a real cost. Our lost map guide is where people end up after an unnecessary reset.

Is it my network or the brand's servers?

It is the brand's servers when every device from that brand goes offline at the same moment while everything else in the house works, and there is nothing you can do about it except wait. Robot vacuums do not talk to your phone directly once setup is done. The app sends a command to the manufacturer's cloud, and the cloud passes it to the robot, even when you are sitting next to it. That is why the robot still cleans on schedule during a cloud outage but ignores the app, and why the app sometimes works for a friend across town and not for you when your home internet is down. Before you touch a single setting, check whether other apps on your phone load, whether other smart devices respond, and whether the brand has posted an outage; iRobot, Roborock and Ecovacs have all had multi-hour cloud incidents in the past two years.

A more permanent version of this problem is the brand shutting down or changing its cloud, which has happened to a handful of smaller vacuum brands. If you own a robot from a company that no longer updates its app, the robot will keep cleaning on its stored schedule and its physical buttons, but the app features are gone for good. Our privacy and data guide discusses which brands offer local control as a fallback, and our smart home guide covers Matter, which promises to make the cloud optional for basic commands but is still uneven in practice.

Why does it work at home but not when I'm out?

It works at home but not when you are out because the app is being restricted by your phone, not because the robot has changed. When you are on home Wi-Fi some apps use a faster local path to the robot; on mobile data they must go through the cloud and the phone's background-data and battery rules apply. Android's battery optimisation is the usual culprit: it puts the vacuum app to sleep, notifications stop, and commands time out. Exempt the app from battery optimisation and allow background data. On iOS check that Background App Refresh and Cellular Data are both on for the app. A logged-out account produces the same symptom, so if the app shows a generic error rather than "offline", sign out and back in.

What about mesh networks and extenders?

Mesh networks and extenders solve the range problem and occasionally create a new one, because the robot connects to whichever node it hears best and does not always follow when a better one appears. A robot that pairs beside the router and is then parked next to a satellite node may cling to the distant router with a weak signal, dropping offline exactly as if the mesh were not there. Pair the robot while it sits on its dock, so it latches on to the nearest node from the start. Cheap plug-in extenders add a second problem: many of them create a network with a different name or a duplicated name on a different subnet, and the app on your phone cannot see a robot on the other side of that boundary. If you use an extender, make sure it is in access-point mode and shares the router's network, not repeating it under a new name. The Wi-Fi guide has a section on mesh quirks by brand.

Should I factory reset the robot?

Factory reset the robot only after re-pairing has failed, because a reset erases maps, room names, no-go zones and schedules and fixes nothing that re-pairing would not. The order that gets most robots back online without losing anything is short. Restart the app. Restart the phone. Restart the robot with a ten-second power hold. Restart the router. Re-pair the robot through the app's add-device flow. Only if the robot still refuses after all five, or if the app shows it as belonging to another account, does a reset make sense, and even then take screenshots of your room layout and schedules first. Our troubleshooting hub lists the reset button combination for each brand, and the error code guide covers the network-related codes that sometimes appear alongside a connection failure.