Roomba i5 / i5+ troubleshooting
Series-level error paths with model checks. We route by the exact error or symptom rather than assuming a generic robot-vacuum fix applies.
Roomba i5 / i5+ issue index
3 guides
Won't return home
When a Roomba i5 simply 'won't return home' without a clear Error 18 message, first determine which stage fails. If it cannot dock from a short clear approach, troubleshoot the Home Base, RCON/bumper area, contacts and wheels. If it docks perfectly from about 6 ft but fails after a long cleaning mission, focus on whole-home context: whether the robot or base was moved, how far the return begins from the dock, remaining battery and environmental interference. iRobot notes that physically moving a Roomba during a mission can make Home Base recovery harder and publishes range guidance for the i3/i4/i5 family. This symptom-first page therefore starts with a close test before map deletion or battery replacement.
Error 18
Error 18 on a Roomba i5 means it could not return to the Home Base or starting position. Treat the numbered error as a controlled docking diagnosis: prove dock power, keep the base fixed and clear, inspect the caster and drive wheels, then test the i5 facing the dock from about 6 ft (1.8 m). Unlike j-Series robots, the i Series is among the models iRobot lists with an RCON sensor for dock detection, so the close-range test helps evaluate that homing path. If the i5 docks from close range but fails after long missions, placement, navigation context, remaining battery and area coverage are stronger suspects than the dock itself.
Not charging
For a Roomba i5 that will not charge, first prove the Home Base or Clean Base is powered and that the robot is actually touching both charging contacts. iRobot warns that battery status may not refresh reliably from a remote connection, so check locally and use a timed before/after reading. Clean the contacts, allow a deeply exhausted robot to wake, and separate manual charging from autonomous docking. If the i5 never acknowledges charge, use the supported reboot or battery re-seat path. Only after those controlled checks should battery or robot-side charging hardware become the leading suspect; newer i5 hardware revisions can also be non-modular, which affects the service route.