iRobot · Wi-Fi

iRobot Roomba i5/i5+ will not connect to Wi-Fi or the app

iRobot Roomba i5/i5+ will not connect to Wi-Fi or the app: confirm supported Wi-Fi band/security, account and pairing mode before deleting maps. Scoped to i5, i5+, with the model boundary and safe stop points made explicit.

Direct answer

For the iRobot Roomba i5/i5+, confirm supported Wi-Fi band/security, account and pairing mode before deleting maps. First, place phone/robot near the router on the supported network.

What this covers

  • iRobot Roomba i5/i5+ (i5, i5+)
  • iRobot Roomba; mapping, obstacle avoidance, self-emptying and mop functions vary.
  • The specific fault this record addresses: will not connect to Wi-Fi or the app

What it does not cover

  • ×The same symptom on a different iRobot product line, which has its own record and its own cited source
  • ×An on-screen error code whose meaning has not been checked against this exact model's manual
  • ×Live electrical, gas, sealed-system, internal battery-cell or structural repair — a technician boundary, not a self-service step

Differential

What actually causes this, and how to tell them apart

These are ordered by how often each one is the answer, not by how easy it is to try. The point of the middle column is that two causes producing the same headline symptom rarely produce the same detail — that detail is what tells you which one you have before you change anything.

  1. 1

    The phone is on a 5GHz-only network the vacuum's radio can't join

    What separates it The app finds no device during setup, or setup fails specifically at credential entry.

    How to confirm Join the phone to the 2.4GHz network explicitly, since most vacuum Wi-Fi radios are 2.4GHz-only.

  2. 2

    Guest network isolation or a VPN is blocking discovery

    What separates it Setup appears to complete but the device never shows online, or previously worked and stopped after a router or network change.

    How to confirm Disable guest isolation and any VPN for one setup attempt on the main home network.

  3. 3

    The device is still claimed by a previous account

    What separates it Setup finds the device but fails at the account-claim step, common on a second-hand unit.

    How to confirm The previous owner needs to remove it from their account, or a support case with the serial number is the documented path to release it.

  4. 4

    The device isn't in its documented pairing mode

    What separates it The app never finds the device at all, even close by.

    How to confirm Check the manual for the exact button press or reset sequence that puts this specific model into pairing mode.

Before you touch a setting

Record this first — changing settings destroys the evidence

Every item below stops existing the moment a reset, re-pair or settings change is made. Written down first, they are what separates the causes above; recovered afterwards, they are guesswork.

  • Which network band the phone is joined to during setup.
  • Whether this is a new setup or a previously working connection that stopped after a network or router change.
  • Whether the device is new, second-hand, or being re-added after a factory reset.
Try in this order0 of 4 completed
  1. Place phone and robot near the router on the supported 2.4GHz network

    Reversible

    Disable guest isolation and VPN for one setup attempt.

  2. Confirm the device is in its documented pairing mode

    Reversible

    Use the exact sequence from the manual for this model.

  3. Correct account ownership or permission issues before repeating setup

    Reversible

    A second-hand device needs release from the previous account first.

  4. Confirm map and status sync and one harmless command after setup

    Reversible

    Verifies the connection is stable, not just that pairing completed.

Model-specific

What is true of this model and not of its siblings

Generic advice for the product line fails here. Each item below is a property of this specific model family that changes which of the steps above apply to you.

Model scope
i5, i5+. iRobot Roomba; mapping, obstacle avoidance, self-emptying and mop functions vary.
Type — ROBOT vacuum
A ROBOT vacuum with navigation and app control — symptoms are navigation, docking and brushes. The i5+ adds a Clean Base self-empty dock; the plain i5 empties its onboard bin.
Docking & (on +) self-empty
'Won't dock/charge' is dirty contacts, a moved/unplugged dock, or blocked clearance. On the i5+, 'won't empty' is a full Clean Base bag or clogged path.
Brushes, wheels & sensors
Two rubber brushrolls, side brush, wheels and sensors — clear hair and wipe sensors if it gets stuck, circles or misses areas.
Symptom boundary
This record covers iRobot Roomba i5/i5+ when it will not connect to Wi-Fi or the app. A different symptom on the same hardware, or this symptom on a different iRobot product line, has its own record with its own causes and its own cited source.

Stop boundary

When this stops being a self-service repair

Continuing past any one of these costs more than the repair saves — in safety, in warranty, or in evidence a technician needs.

  • !Do not delete existing maps or weaken router security to work around a persistent connection failure until the actual cause is isolated.

Evidence ledger

Sources behind this answer

Visible sources support the visible claims. Home Product Support records the publisher, the fact used and the review date; community reports can suggest an issue but do not become a published fact on their own.

Where the manufacturer's article stops. iRobot Support publishes this as "Cloud and Wi-Fi Connectivity Troubleshooting Guide". iRobot's own general/device-agnostic Wi-Fi and app connectivity article. Verified reachable and content-matched via the Browser tool 2026-08-28 after direct fetch was refused. What that article does not carry is the model boundary — it is written for a product line, and i5, i5+ is the scope applied here. Where a control label, terminal, indicator pattern or reset sequence differs on your unit, the manual for that exact model is the authority, not this page and not the article.

Exact questions

Common follow-ups

My Roomba i5 gets stuck under the same furniture.+

Robots wedge under low furniture that is just tall enough to enter but too low to exit. Use the app's keep-out zones (where supported) or a physical barrier to block that spot, or add small risers to the furniture. Also clear hair from the wheels and brushes, since a hair-bound wheel makes it lose traction and strand itself. Wiping the cliff sensors underneath helps if it also stops near thresholds or dark floors.

The app can't find my robot vacuum during setup.+

Join your phone to the 2.4GHz network explicitly — most robot vacuum Wi-Fi radios can't see a 5GHz-only connection even if your router broadcasts both bands under the same name. Then confirm the robot is actually in its pairing mode using the exact sequence in the manual.

It was connected fine but stopped working after I got a new router.+

This is almost always a network-side setup issue, not a device fault — re-pair it on the new network, confirming the band and disabling guest isolation for that attempt.

Does this answer apply to every iRobot model?+

No. It is scoped to i5, i5+. iRobot Roomba; mapping, obstacle avoidance, self-emptying and mop functions vary.

What should I record before troubleshooting Wi-Fi or app?+

Record the complete model identifier, exact message or indicator, software/firmware where visible, the operating stage and what still works.

Why is a factory reset not the first step?+

A reset can erase accounts, networks, maps, schedules or preferences without distinguishing Wi-Fi, app. The ordered checks preserve that evidence.

When should I stop and use qualified service?+

Do not delete maps or weaken security until the fault is isolated.

Change recordSept. 1, 2026 — Built out with researched, cross-checked per-model specifications and model-specific guidance. Aug. 17, 2026 — Published with explicit i5, i5+ applicability, a app-wifi diagnostic boundary and first-party support provenance.
Report a correction
Wrong device or version?

Match the path before repeating the steps.

Match another device