Ecovacs DEEBOT · Ecovacs DEEBOT T80 OMNI · Wi-Fi setup / connection failure

DEEBOT T80 Wi-Fi Won’t Connect: QR, Bluetooth & 2.4 GHz Fix

Fix DEEBOT T80 OMNI Wi-Fi setup failures with ECOVACS HOME, QR scan, Bluetooth hotspot, 2.4 GHz, app version, permissions, VPN and reset-stage checks.

Official model supportEditorially reviewed September 5, 2026Connectivity / software
Quick answer

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.

First discriminator

Which T80 onboarding checkpoint fails?

If: QR/model discovery failsThen: Fix ECOVACS HOME, camera/Bluetooth permissions and the correct robot QR before Wi-Fi troubleshooting.
If: No Bluetooth-hotspot voice prompt after the network buttonThen: Confirm robot power and the T80 network/reset-button step; Wi-Fi credentials have not been reached yet.
If: Hotspot is released but Wi-Fi authentication failsThen: Test a visible, strong 2.4 GHz home SSID with correct password and no VPN/proxy/web-auth path.
If: Wi-Fi indicator reaches connected but app setup does not finishThen: Treat Wi-Fi association and app/account registration as separate stages instead of repeating network reset.
01Match

Confirm the exact model and exact code, light pattern or symptom.

02Isolate

Run the lowest-risk physical or software check first.

03Prove

Use each pass condition to decide what the result actually narrows down.

Does this match your problem?

  • You are setting up a DEEBOT T80 OMNI in ECOVACS HOME for the first time and the QR or Bluetooth-hotspot step does not complete.
  • The T80 was connected before but now appears offline after router, Wi-Fi password, app, phone, or network changes.
  • The robot says its Bluetooth hotspot is released, but the app never finishes connecting to the home Wi-Fi.
  • You are searching for T80 2.4 GHz requirements, Wi-Fi indicator meaning, reset/network button timing, ECOVACS HOME permissions, VPN, hidden SSID, or pairing failures.
  • You want to identify the failed network stage before using the T80 factory-reset function and losing unrelated settings.

Most likely causes

01

The T80 is not powered on, not in network-setup mode, or the brief network/reset-button press was skipped before the app tried Bluetooth discovery.

02

Bluetooth, local-network/location permission, or the current ECOVACS HOME app is not ready for the local discovery stage.

03

The router’s 2.4 GHz service is disabled, the SSID is hidden, the signal is weak, or the phone is not actually connected to the intended home network.

04

The Wi-Fi password is wrong, the wrong SSID was selected, or a dual-band network is steering the setup away from a stable 2.4 GHz path.

05

A VPN, proxy, captive portal, enterprise authentication, or other network policy is incompatible with the ordinary ECOVACS onboarding flow.

06

The robot has stale network state after a router/credential change and needs the network-setup reset sequence, while a full factory reset is still unnecessary.

What your test result means

What you observeWhat it narrows downNext move
App cannot scan or recognize the robot QR codeThe failure is still before Wi-Fi authentication.Use the current ECOVACS HOME app, verify camera permission, or search the T80 model manually instead of changing the router.
No “Bluetooth hotspot released” voice prompt after the button stepThe robot may not be in the expected local pairing state.Confirm power switch I, wait for startup, then repeat the brief network/reset-button press exactly when prompted.
Bluetooth discovery succeeds but home Wi-Fi connection failsThe robot/phone can see each other; credentials, 2.4 GHz, signal, VPN/proxy, or router conditions become the stronger branch.Verify the intended 2.4 GHz-capable SSID/password and remove VPN/proxy or hidden-network complications.
T80 connects near the router but fails at the normal station locationCoverage/interference is more likely than a pairing-state fault.Improve 2.4 GHz coverage or station/router placement; do not keep resetting the robot.
Multiple phones and a simple compatible network fail at the same stageOrdinary phone/router causes have been reduced.Save the exact voice prompt, Wi-Fi indicator, app screen and logs for ECOVACS support before factory reset.
Before you reset anything

Reset can erase maps/settings on this path. Use lower-risk checks first and document the current state before resetting.

Run these checks in order

1

Start with the exact T80 ECOVACS HOME onboarding path

Place the T80 near its station and begin in ECOVACS HOME rather than following a generic DEEBOT video for another model. ECOVACS’ T80 guide says to scan the robot’s QR code, install or open ECOVACS HOME, sign in, and continue from the app’s main interface. If scanning fails, use the app’s device search/model-selection route instead of assuming Wi-Fi is already the problem. The Chinese T80 support page also states that T80 network setup requires a current ECOVACS HOME release; its published guidance specifies version 3.0.0 or newer. Because app screens can change, use the current app wording while preserving the same sequence: identify the T80 first, then move into network setup.

Pass condition: ECOVACS HOME identifies the T80 and advances to the robot power/network-setup instructions rather than failing at QR or model discovery.
2

Prove robot power and the Bluetooth-hotspot pairing state

Open the T80 top cover and set the physical power switch to I. Wait until the startup sound finishes. When ECOVACS HOME instructs you to continue, briefly press the network/reset button and listen for the voice confirmation that the Bluetooth hotspot has been released. The exact US T80 Wi-Fi guide uses that prompt as the checkpoint before the app begins the local hotspot connection. Keep phone Bluetooth on and grant the app the nearby-device/location/local-network permissions requested by your operating system. If the prompt never occurs, stay on this branch; changing the router cannot fix a robot that never entered pairing mode.

Pass condition: The T80 is on, the phone Bluetooth path is available, and the robot announces the expected Bluetooth-hotspot state at the correct point in the app flow.
3

Use a strong 2.4 GHz-capable home network for the proof test

ECOVACS’ official Wi-Fi troubleshooting guidance tells users to keep the phone on the home Wi-Fi during setup, use a compatible 2.4 GHz or 2.4/5 GHz mixed network, and pair where signal strength is good. On a router that broadcasts separate 2.4 and 5 GHz SSIDs, choose the compatible 2.4 GHz network for the controlled setup test. On a combined dual-band SSID, the manual indicates a 2.4/5 GHz mixed network can be used, but if band steering causes repeated onboarding failure, temporarily exposing a clear 2.4 GHz SSID is a useful diagnostic. Keep the robot, phone and access point close enough that weak coverage is not mixed into the first result.

Pass condition: The phone has normal internet on the intended home SSID, the 2.4 GHz service is active, and the T80 pairing attempt runs in a strong-signal area.
4

Remove hidden-SSID, VPN, proxy, and credential variables

Enter the home Wi-Fi password from a known working phone rather than from memory. ECOVACS’ T80 network instructions caution that the Wi-Fi signal should not be hidden during setup and state that VPN/proxy or web-authentication networks are not supported for the normal pairing flow. For one clean test, turn off phone VPN/proxy services and avoid hotel, campus, enterprise, guest-isolated, or captive-portal networks that require a browser sign-in. If the router broadcasts two similar SSIDs, confirm the app is using the same household network you just tested on the phone. Change only one variable at a time so you can tell whether the failure follows credentials, network policy, or local discovery.

Pass condition: The T80 receives the correct password for a visible, ordinary home Wi-Fi network with VPN/proxy/captive-portal complications removed from the test.
5

Read the T80 Wi-Fi indicator and repeat only the failed stage

The T80 manual describes the Wi-Fi indicator states: slow white flashing means disconnected, fast white flashing means connecting, and solid white means connected. Use that state together with the app screen. If the robot remains in slow flashing, return to network setup rather than debugging cloud login. If it fast-flashes and then fails after credentials are entered, focus on the home network and authentication branch. If it becomes solid white but the app later reports offline, the initial Wi-Fi join succeeded and the next question is account/cloud/app state, not whether the robot can see Wi-Fi. Avoid repeated factory resets because they erase context without telling you which stage failed.

Pass condition: You can match the visible indicator/app state to discovery, connecting, or connected and repeat only the relevant branch instead of restarting the entire process blindly.
6

Escalate with a reproducible pairing stage, not “Wi-Fi broken”

If the T80 still fails, repeat one final controlled attempt with the current ECOVACS HOME app, robot powered on, Bluetooth enabled, the hotspot voice prompt confirmed, strong 2.4 GHz-capable Wi-Fi, correct password, and VPN/proxy removed. A second phone can help separate phone-permission/app issues from robot/network issues. If the failure reproduces at the same point on a simple compatible network, record the Wi-Fi indicator pattern, exact voice prompt, app screen, phone/OS, app version, router model and whether the SSID is split or combined. That package is more useful to ECOVACS than a factory reset performed before the network stage is known.

Pass condition: The failure is reproducible at one documented stage across a clean setup attempt, or the T80 successfully joins ECOVACS HOME and remains online.
!
When to stop DIY

Contact ECOVACS when the T80 repeatedly fails the same setup stage after the current ECOVACS HOME app, correct power state, confirmed Bluetooth-hotspot prompt, strong compatible Wi-Fi, correct credentials, required phone permissions, and a VPN/proxy-free test. Send screenshots/video of the stage, the robot’s Wi-Fi-indicator pattern, app version, phone/OS and router/SSID details. Use factory reset only if ECOVACS directs it or if the documented network reset path cannot restore pairing, because a reset performed too early hides whether the original problem was QR discovery, Bluetooth pairing, Wi-Fi authentication or the cloud/app layer.

What to collect before contacting support

Give support a reproducible case instead of “it doesn’t work.” That reduces repeated basic troubleshooting and preserves the clues from your tests.

  • Exact model name and the error code / voice prompt exactly as shown
  • A photo or screenshot of the app error and the time it occurred
  • A short list of the checks already completed and what happened after each one
  • Map/station screenshot when the problem involves return-to-station or mapping

Manufacturer evidence

Official model support

ECOVACS T80 OMNI — Wi-Fi connection guide

ECOVACS’ US T80 guide documents the QR-code flow, physical power switch, brief network-button press and the “Bluetooth hotspot released” checkpoint. ECOVACS’ official Wi-Fi troubleshooting page adds the 2.4 GHz/mixed-network, credential and no-VPN/proxy requirements, while the T80 manual documents the Wi-Fi indicator states and mixed-network context. Together, those model-specific facts separate QR discovery, Bluetooth pairing, home-Wi-Fi authentication and post-connection app status instead of treating every failure as one generic Wi-Fi error.

Additional official source: ECOVACS US — home Wi-Fi connection troubleshootingAdditional official source: ECOVACS T80 OMNI product support hubAdditional official source: ECOVACS T80 Family — official English instruction manualLast editorial review: September 5, 2026

Regional note: manufacturer help centers, model suffixes, mains-power requirements and warranty procedures can differ by country. If the source redirects to a local support site, confirm that the model/hardware scope still matches before following a region-sensitive step.

Open manufacturer source ↗
How to read the evidence label

Official model support means the manufacturer page explicitly covers this model. Official series support means the manufacturer explicitly groups the model with a documented series path. Official manual means the diagnostic comes from the exact-model owner manual. Manufacturer-general means the source is an official brand-wide troubleshooting path and the page avoids presenting it as model-exclusive.

FAQ

Does DEEBOT T80 need 2.4 GHz Wi-Fi?

ECOVACS’ exact T80 network guidance instructs users to confirm that the router’s 2.4 GHz signal is enabled for setup. The T80 manual also describes use with a 2.4/5 GHz mixed network. For troubleshooting, a clearly available 2.4 GHz path is the best controlled test because it removes band-steering ambiguity.

What does “Bluetooth hotspot released” mean on the T80?

It is the voice checkpoint ECOVACS uses after the brief network/reset-button press during onboarding. Hearing it means the robot has entered the local pairing state expected by ECOVACS HOME. If you never hear it, stay on the robot power/pairing-state branch rather than changing Wi-Fi passwords or router settings.

What do the T80 Wi-Fi indicator flashes mean?

The T80 manual describes slow white flashing as disconnected, fast white flashing as connecting and solid white as connected. That makes the indicator useful when the symptom is “T80 Wi-Fi blinking,” “T80 stuck connecting,” or “T80 connected but offline in app,” because each visible state points to a different stage.

Can a VPN, proxy or hidden Wi-Fi name make DEEBOT T80 setup fail?

Yes. ECOVACS’ T80 network guidance says the Wi-Fi signal should not be hidden during setup and does not support normal pairing through VPN/proxy or browser-authentication network flows. Disable those variables for one controlled attempt and expose the SSID temporarily if needed. If pairing then works, the robot radio was not the root cause; the original network configuration was blocking onboarding.

Should I factory-reset the DEEBOT T80 when Wi-Fi setup fails?

Not as the first step. First identify whether failure occurs at QR recognition, Bluetooth-hotspot release, home-Wi-Fi authentication or after the Wi-Fi indicator becomes connected. A factory reset can erase useful state without proving which network layer failed. Escalate with the exact stage if a simple compatible test network also fails.

Reader feedback

Did this diagnostic narrow the fault?

Use this as an editorial signal, not a popularity counter. If a feedback address is configured you can email the note; otherwise you can copy it for your own support record.

More Ecovacs DEEBOT T80 OMNI diagnostics

See full model desk →

Compare the same failure family

Connectivity / software