Wi-Fi, App or Update Problems
Use the manufacturer’s network reset or pairing flow before a full system reset. Network recovery should not automatically erase maps and schedules.
Confirm the robot is in the documented pairing state and that the phone/app can discover it before changing router settings or deleting saved robot data.
What the symptom points to
Network/app/account path rather than motor or navigation hardware.
Pairing mode, phone permissions, band/security compatibility or credentials.
Update recovery path; repeated resets can make evidence harder to preserve.
Do not erase the evidence
- Factory reset as the first networking step
- Changing multiple router settings at once
- Deleting the robot from the app before noting firmware and map state
Record app version, robot firmware, router band/security mode, the exact pairing stage that fails and a screenshot of the message. This makes escalation actionable.
Matching model-specific guides
11 diagnosticsWi-Fi won't connect / offline
If a Roborock Qrevo will not connect to Wi-Fi, disappears from the Roborock app, or stalls during pairing, treat it as a network-stage problem before resetting the whole robot. Roborock’s Qrevo support says the robot uses 2.4 GHz Wi-Fi, the password must be correct, phone permissions can matter, the home Wi-Fi must be selected instead of the temporary robot network, WEP is not supported, and VPN or cellular routing can interfere. The Qrevo manual also gives a dedicated Wi-Fi reset: open the top cover, locate the Wi-Fi indicator, hold the documented button combination until the robot announces “Resetting WiFi,” then wait for the indicator to flash slowly before adding the robot again. A Wi-Fi reset is different from a factory reset and is the safer recovery step when the robot itself still cleans normally.
Wi-Fi won't connect
For X10 Pro Omni Wi-Fi setup, do not jump straight to factory reset. Confirm the network name/password, move the phone and robot closer to the router, allow eufy Clean location/precise-location and local-network permissions, pair on 2.4 GHz with Bluetooth enabled, then reset only the robot’s Wi-Fi by holding Home + Spot Cleaning for three seconds. If setup still fails, a phone-hotspot test can separate router configuration from robot/app problems.
Error 29 / update interruption
Error 29 on the Roomba Max 705 is a software-update interruption, not a motor, brush or dock-mechanism code. iRobot’s Max 700 release notes explicitly say version 7.5.2 included further improvements for update interruptions reported as Error 29. Recovery should therefore preserve the conditions needed for a clean software delivery: keep the robot on reliable dock power, confirm the Roomba Home App can reach it, keep Wi-Fi stable, and check the installed software version before attempting destructive resets. New Max 700 robots are especially dependent on successful provisioning: iRobot says units shipping with factory version 7.2.3 or later must connect to the cloud before their first cleaning mission, although they can later be used offline after setup. Because iRobot rolls releases out over several weeks, an update not appearing immediately is not proof that the robot is stuck. The useful question is whether the same Error 29 repeats while the robot is powered, provisioned and online.
Won't connect to Wi-Fi
Qrevo Curv does not need a map or system reset just because app connectivity fails. Roborock documents a dedicated Wi-Fi reset, and its current Qrevo Curv support page says the robot connects on 2.4 GHz rather than 5 GHz. Prove that a usable 2.4 GHz network exists, reset only the robot's Wi-Fi, pair near strong coverage, and only then work on router band settings. A successful Wi-Fi reset followed by repeated failure on one router points away from the map and toward network configuration.
Won't connect to Wi-Fi
Follow the X8’s connection sequence before changing router settings: keep the robot near the station, sign in to ECOVACS HOME, scan the robot QR code, power the robot on, briefly press Reset and wait for the network-setup/Bluetooth-hotspot voice prompt, then let the app complete the join in strong Wi-Fi coverage. The X8 manual adds the useful compatibility boundaries: a 2.4 GHz or mixed 2.4/5 GHz network, 802.11b/g/n with IPv4, no VPN/proxy or hidden SSID, WPA/WPA2 rather than enterprise authentication, and matching SSID/password on an extender. If pairing fails, first identify whether discovery fails before credentials are sent or whether the robot is discovered but cannot join the home network. Those are different failures and should not be “fixed” by deleting maps or factory-resetting the robot.
Wi-Fi / app connection failure
Narwal Flow is an exception to the older Narwal “2.4 GHz only” rule: Narwal’s Flow-specific FAQ says this model supports both 2.4 GHz and 5 GHz Wi-Fi. Start with the Flow pairing path in the Freo App, confirm the robot and base are powered, enable Bluetooth and the phone permissions Narwal requires, and keep the robot near a strong signal. If setup fails, compare the two supported bands or a simple phone hotspot without changing several variables at once. Narwal’s general network guide is still useful for permissions, hotspot and router isolation, but its 2.4-GHz-only sentence is not the correct compatibility rule for Flow. If the failure persists, send Narwal the robot SN, App ID and a screen recording or clear record of the failed setup stage.
Wi-Fi setup / connection
Do not force a Roomba Max 705 onto 2.4 GHz just because older Roomba advice says to. iRobot’s current Roomba Home App setup table lists the Max 705 Series as supporting both 2.4 GHz and 5 GHz. Start by keeping the robot charging on a powered dock near good Wi-Fi coverage, then verify Bluetooth, precise location and local-network access on the phone. The most useful branch is where setup stops: if the app never discovers the robot, work the phone-to-robot discovery path; if discovery succeeds but Wi-Fi provisioning fails, test the exact home network and, when practical, a phone hotspot. A successful hotspot setup points away from a dead robot radio and toward the home router, firewall, VPN, ad blocker or network configuration.
Wi-Fi setup / connection failure
For a DEEBOT T80 OMNI that will not connect to Wi-Fi, use the T80 onboarding sequence before changing router settings: keep the robot near the station, use ECOVACS HOME, scan the robot QR code, enter the home Wi-Fi password, switch the robot on, briefly press the network/reset button when the app asks, and confirm the voice prompt that the Bluetooth hotspot has been released. ECOVACS’ T80 network guidance also calls for a 2.4 GHz-capable home network, Bluetooth enabled on the phone, strong Wi-Fi coverage, a current ECOVACS HOME app, and no VPN/proxy or captive-portal style network during pairing. The key diagnostic is the stage: QR recognition, Bluetooth discovery, home-Wi-Fi authentication, or final cloud connection. Do not factory-reset simply because the final screen says connection failed.
Wi-Fi / Offline
Treat Omni S2 Wi-Fi as a pairing-path problem, not a reason to factory-reset the robot. eufy says S2 supports 2.4 GHz Wi-Fi only: verify the SSID/password, keep Bluetooth on, confirm the circular light is fast-flashing white, then reset only Wi-Fi by holding CLEAN + Return to Base for 3 seconds. A mobile-hotspot test is the clean discriminator before escalation.
Wi-Fi setup
The Omni E28 uses a 2.4 GHz Wi-Fi connection. Before resetting anything, confirm the password and test whether the robot can join a phone hotspot. For a clean pairing test, keep the robot, router and phone close together. If setup still fails, eufy says to hold the Power and Recharge buttons together for 3 seconds until the network-reset voice prompt, then reconnect. A hotspot that works while home Wi-Fi fails points away from a dead robot radio and toward the home network or credentials.
Wi-Fi setup failure
For first-time X50 network configuration, start with the hard compatibility rule: Dreame says the robot supports 2.4 GHz Wi-Fi and does not support a 5 GHz Wi-Fi connection. Then keep the robot/phone in strong Wi-Fi coverage, allow phone location permission for the Dreamehome app, and complete the handoff from the robot’s temporary hotspot back to the app after the voice prompt. Dreame also recommends simple letters/numbers in the Wi-Fi name and password for troubleshooting and suggests testing a different phone or a second phone’s hotspot if pairing still fails. The X50 manual adds two useful checks: verify the Wi-Fi password and, if the robot is not ready to be configured, exit and re-enter the app before retrying. This page is for configuration failure, not a robot that was paired successfully and later went offline.