If the Roborock app cannot find the vacuum, the issue usually comes down to pairing mode, Wi-Fi setup, account region, or device-side network settings.
This guide walks through the most common causes and the fastest fixes so you can get the robot back online with less guesswork.
Why the Roborock app cannot find the vacuum
Roborock robot vacuums depend on a stable connection between the vacuum, the mobile app, and your home network.
If any link in that chain breaks, the app may fail to discover the device during setup or show it as offline after it was previously connected.
The problem is often not a hardware failure.
In many cases, discovery fails because the vacuum is on the wrong Wi-Fi band, Bluetooth is disabled on the phone, the robot is not in pairing mode, or the app region does not match the account and device ecosystem.
Common causes of discovery failure
- Wi-Fi compatibility issues: Many Roborock models require a 2.4 GHz network during setup.
- Bluetooth permission problems: The app may need Bluetooth and nearby-device permissions to detect the vacuum.
- Incorrect pairing mode: The vacuum must be actively waiting to pair.
- Router security settings: WPA3-only networks, guest networks, or enterprise settings can block discovery.
- Account region mismatch: Some models and app regions are tied to specific market versions.
- App cache or outdated firmware: An old app build or buggy firmware can interrupt onboarding.
Start with the basics
Before changing router settings, confirm the vacuum itself is ready to pair.
Place the robot near the router, charge it above the minimum battery level, and make sure it is not already bound to another account.
On many Roborock models, pairing mode is indicated by a voice prompt, flashing Wi-Fi indicator, or an app-facing setup screen.
If the vacuum was previously configured, remove it from the old account first if possible, because a device can usually be tied to only one primary account at a time.
Check your phone permissions and app access
The Roborock app uses local discovery methods that can depend on phone permissions.
On iPhone, confirm that the app has permission for Bluetooth, Local Network, and Notifications if prompted.
On Android, check Bluetooth, Location, and Nearby Devices permissions, since discovery may fail if any of these are denied.
Also make sure Wi-Fi is enabled on the phone during setup.
Some phones will not fully discover smart-home devices if Wi-Fi is turned off, even when mobile data is active.
Quick phone-side checks
- Turn Bluetooth on.
- Allow the Roborock app to access Bluetooth and nearby devices.
- Enable Location services on Android if the app requests it.
- Disable VPN temporarily.
- Close and reopen the app after changing permissions.
Verify the Wi-Fi network
One of the most common reasons the Roborock app cannot find the vacuum is that the robot is attempting to join a network it cannot use.
Many Roborock vacuums only support 2.4 GHz Wi-Fi during setup, even if they later operate in a dual-band environment.
If your router combines 2.4 GHz and 5 GHz under the same SSID, the vacuum may still connect if the router handles band steering well, but setup is more reliable when the 2.4 GHz network is clearly available.
If needed, temporarily split the bands into separate network names and try again.
You should also verify:
- The SSID is visible and not hidden.
- The Wi-Fi password is correct.
- The router is using a supported security mode, ideally WPA2-PSK or WPA2/WPA3 mixed mode.
- The network does not require a captive portal, login page, or enterprise authentication.
- Guest network isolation is not blocking the vacuum from the phone.
Restart the vacuum, app, and router in the right order
A simple restart often clears stale connection data.
Power-cycle the robot vacuum first, then restart the router, and finally relaunch the app.
This sequence helps rebuild the local network path from the device outward.
If the app has cached a failed pairing attempt, force close it before reopening.
On Android, clearing the app cache can also help if the discovery screen keeps failing without producing a useful error message.
Re-add the vacuum as a new device
If the vacuum was previously connected and now appears missing, remove it from the Roborock app if the option is still available.
Then start a fresh pairing process instead of trying to revive the old device entry.
A fresh pairing may resolve issues caused by outdated device metadata, changed Wi-Fi credentials, or a stale cloud association.
Make sure you are signed into the correct Roborock account before pairing, especially if you use multiple email addresses or regional app versions.
Look at app region and firmware compatibility
Roborock has historically segmented some products by region, and the app experience can vary depending on whether your account is set to China, Europe, North America, or another supported region.
If discovery fails immediately or the device type never appears, the account region may not match the model’s intended ecosystem.
Firmware can also matter.
If the vacuum was updated recently or was reset after a partial update, it may need another attempt at onboarding.
When possible, ensure both the app and the robot firmware are current before repeating setup.
Router settings that often block Roborock discovery
Some home networks are technically connected but still unsuitable for smart-device onboarding.
Router hardening features can interfere with the local handshake needed during setup.
Settings to review on the router
- AP isolation: Turn this off so the phone and vacuum can communicate locally.
- MAC filtering: Disable or add the vacuum to the allow list.
- Firewall restrictions: Avoid rules that block local IoT traffic.
- WPA3-only mode: Try mixed WPA2/WPA3 if supported.
- SSID hiding: Keep the network broadcast visible during pairing.
If your router supports an IoT network profile, use it only if it still provides standard local access and does not isolate devices from your phone.
Some “smart home” modes are convenient, but others reduce discovery reliability.
Model-specific signs the vacuum is not discoverable
Different Roborock models use different indicators, but the failure pattern is similar.
If the app keeps searching without finding the robot, and the Wi-Fi light on the vacuum never enters pairing behavior, the robot may not actually be in setup mode.
Common signs include a spinning discovery screen, repeated “device not found” messages, or a vacuum that briefly appears and then disappears before binding completes.
These symptoms usually point to network compatibility, permissions, or a partial reset rather than a broken robot.
When to factory reset the vacuum
A factory reset is worth trying when the device will not pair after you have confirmed permissions, network compatibility, and account region.
Resetting clears local configuration and can remove corrupted pairing records.
Use the reset method recommended in your model’s manual, since button combinations differ across Roborock generations.
After the reset, wait for the pairing indicator, then restart the app setup from scratch.
When the problem may be hardware-related
If the Roborock app cannot find the vacuum on multiple phones, on multiple networks, and after a factory reset, the issue may involve the robot’s Wi-Fi module or internal firmware.
This is less common than setup-related causes, but it does happen.
At that point, contact Roborock support or the retailer’s service team with your model number, firmware version, app version, and a summary of the troubleshooting steps you already tried.
That information speeds up diagnostics and helps determine whether the unit needs repair or replacement.
Checklist for fixing discovery issues fast
- Confirm the vacuum is in pairing mode.
- Use a 2.4 GHz Wi-Fi network.
- Allow Bluetooth, Local Network, and Nearby Devices permissions.
- Disable VPN, AP isolation, and MAC filtering.
- Check that the app region matches the device version.
- Restart the vacuum, router, and app.
- Remove and re-add the device if it was previously bound.
- Factory reset the robot if setup still fails.
By working through these checks in order, you can usually identify why the Roborock app cannot find the vacuum and restore setup without replacing the device.
