Roborock error -3005.1: "Device binding unsuccessful" — fix the Wi-Fi setup

Roborock Model: Qrevo C (reported); most Wi-Fi Roborock models · Error: -3005.1 · Updated 2026-10-23

The app refuses to bind the robot even though the Wi-Fi password is right. Work through phone and router settings in cost order, ending with 2.4 GHz at 20 MHz width and 802.11b/g/n mode.

What you see: during setup the Roborock app says something like "Device binding unsuccessful. Check that the Wi-Fi network password is correct. -3005.1" — even though the password is right. It can also appear when re-adding a robot that dropped off the app (for example after a power cut).

Cost of this fix: €0. Every step is a setting on your phone or router. Allow 15–45 minutes.

Changing router settings affects every device on your network. If you are unsure, create a separate 2.4 GHz guest/IoT network for the robot and change settings there instead of on your main network. Write down your current settings before changing anything.

Step 1 — Check the basics Roborock lists (5 min)

Roborock's official checklist for failed Wi-Fi connections:

1. Re-type the Wi-Fi password carefully.
2. Give the Roborock app Location permission; on iOS 14+ also allow Local Network access.
3. When the app asks you to choose a network, pick your home Wi-Fi, not the robot's own hotspot.
4. Remove special characters (like ! @ # $) from the Wi-Fi name and password.
5. Don't use WEP security — use WPA or WPA2.
6. Switch off VPNs on the phone. Roborock also suggests disabling mobile data; note that the owner in the case below finally succeeded with mobile data on, so try both.
7. Reboot the router and the robot, then retry.

Step 2 — Make sure the robot sees a 2.4 GHz network (5 min)

Roborock robots only support 2.4 GHz Wi-Fi. If your router combines 2.4 GHz and 5 GHz under one name ("Smart Connect" / band steering), the robot may struggle.

• Check in the router's admin page that the 2.4 GHz radio is actually enabled (some ISP routers ship with it off).
• Split the bands into separate network names, or temporarily switch 5 GHz off while you pair.

Step 3 — Simplify the phone side (5 min)

• Turn off Auto-Join / auto-reconnect for your home Wi-Fi on the phone, so it doesn't jump back to the home network while the app is talking to the robot's hotspot.
• If one phone keeps failing, try another phone or tablet.

Step 4 — Change the 2.4 GHz radio settings (10–20 min)

This is the fix reported in the source thread, after the owner had already tried factory resets, simple passwords, reinstalling the app, several devices, DNS changes and disabling 5 GHz. On the router's 2.4 GHz settings:

Save, reboot the router, reconnect the phone to the 2.4 GHz network, and run the app's add-device flow again. In the reported case the robot bound straight away after these two changes (channel width and mode).

If 20 MHz doesn't work: a different owner (S8 Pro Ultra on UniFi access points) reported the opposite — the robot only stayed connected after changing 2.4 GHz from 20 MHz to 40 MHz. Router behaviour varies; test one change at a time.

After the robot is online you can try switching the mode back to include ax — but if the robot drops off later, put the 20 MHz / b/g/n settings back.

Step 5 — Reset and retry (10 min)

If nothing has worked, reset the robot's Wi-Fi (see your model's manual for the button combination) and run setup again from scratch with the new router settings. A full factory reset is a last resort, since it clears schedules and settings.

When to contact support

Contact Roborock support (via the app or support.roborock.com) if:

• the robot won't bind on a plain 2.4 GHz WPA2 network at 20 MHz and at 40 MHz, using a phone with VPN off;
• the robot doesn't create its setup hotspot at all, or Wi-Fi reset does nothing;
• the robot was working and now fails on a network that other devices use without problems.

Tell them the error code (-3005.1), your router model, and the settings you already tried — it saves a round of generic replies.

Sources

• Reddit r/Roborock: "Yet another solution for Roborock binding problems with error -3005.1" — owner report (Qrevo C, TP-Link AX3000) of the 20 MHz + 802.11b/g/n fix
• Roborock Support: What should I do when Wi-Fi connection fails or robot shows as offline in app?
• Roborock Support: Our Robot: 2.4G vs 5G Wi-Fi Band Support
• Reddit r/Roborock: S8 Pro Ultra and Wi-Fi 2.4/5/6 GHz access points — counter-example where 40 MHz worked