- Home
- Robot vacuums
- Ecovacs
Does the Ecovacs DEEBOT T20 OMNI work without internet?
Still checking this one. 6 of 7 criteria ticked so far for the Ecovacs DEEBOT T20 OMNI.
Verdict · as sold
UnverifiedNot checked enough to say yet. What is known is shown, with sources.
- Checked
- 6/7 checked
- Brand
- Ecovacs · CN
- Model
- DEEBOT T20 OMNI
- Home Assistant
ecovacs· vendor cloud: always- Track record
- Not reviewed yet
Seven questions, as sold.
6 of 7 checked. Every yes or no links to its source and the date it was checked. Nothing here assumes a flash: that’s the next section.
- Works with the internet cut 01 · Yes
Does the main function survive with the WAN cable pulled?
Ecovacs says the robot's button starts and pauses a cleaning cycle without Wi-Fi, but "without a connection, you must manually start the vacuum each time"; generic to DEEBOTs, no T20-specific statement on schedules surviving a WAN cut was found.
- No vendor account needed 02 · No
Can it be set up without creating an account with the manufacturer?
Ecovacs' app-connection FAQ: "enter your email address and password to create an ECOVACS account" before the robot can be added.
- Documented local API 03 · Not checked
Is there a publicly documented local protocol: HTTP, MQTT, ONVIF, RTSP, Zigbee, Z-Wave, Matter, Modbus?
- Can be firewalled off for good 04 · No
Can it be cut off from the internet permanently without anything breaking?
"Without internet, there's no app-based control or remote scheduling". Only the button remains.
- Firmware updates without the cloud 05 · No
Can it be updated by hand, with no forced auto-update?
The T20 OMNI firmware FAQ requires the robot to be connected to the ECOVACS HOME app with good Wi-Fi, and "if automatic update is enabled, DEEBOT will automatically update".
- Runs alternative firmware 06 · No
Can it run ESPHome, Tasmota, OpenBeken, Valetudo or OpenIPC?
No Ecovacs model appears on Valetudo's supported-robots list.
- Home Assistant talks to it locally 07 · No
Is the Home Assistant integration local_push or local_polling?
iot_class: cloud_push
Already own one? Into Home Assistant, then.
A different question from the verdict. Home Assistant can talk to a device locally and still need Ecovacs’s servers to get started, or for good. This is what the integration itself needs.
Yes, but through Ecovacs. The integration talks to Ecovacs's servers rather than to the Ecovacs DEEBOT T20 OMNI itself, so it only works while Ecovacs keeps those servers up.
- Route
- Built-in integration
- Integration
ecovacs- Vendor cloud
- Always
- Verified
- 2026-09-22
Home Assistant logs in with your Ecovacs account and talks to Ecovacs' servers (cloud_push). The docs offer a self-hosted alternative, Bumper, which impersonates Ecovacs' cloud on your LAN; the T20 OMNI is not on Bumper's tested list.
Question 08 · the company
Ecovacs’s track record.
Nothing on record. That isn’t a clean bill yet: it takes a proper look through the vendor’s changelog, and that hasn’t been done for Ecovacs. No documented removal found. The Home Assistant integration is cloud_push; local operation is only possible by self-hosting a replacement server, which the HA docs describe as coming "with some requirements and limitations" (home-assistant.io). Ecovacs never offered a local API, and never having had it is not the same as having removed it.
Editor’s note
In plain words.
Everything beyond the button on top goes through Ecovacs' servers: the app, schedules, maps and the Home Assistant integration all stop the day those servers do. There is no supported flashing route. The only escape is Bumper, a community reimplementation of Ecovacs' cloud that you run at home and redirect the robot to by DNS, and this model has not been reported working on it.
Wrong? Probably somewhere.
Say where. A link and a sentence is enough. Every claim above carries its source so it can be checked.