The integration goes through the Ecovacs cloud, using the Ecovacs Home app account (email, password, country of the account). Ecovacs does not offer a local connection.
The password is never sent in plain text, nor written in the logs.
Account created with Google, Apple, or Facebook: first set a password in the app.
What you get
For each robot:
status (running, paused, returning to base, charging, error…)
start / stop (resume after a pause)
return to base
suction power (vacuum cleaners)
battery and charge
last error (stuck, brush jammed, full bin…)
brush and filter wear, or blades for the mower
a « cloud » or « unreachable » badge on the robot card
Scenes (Gladys 5.1):
triggers: cleaning started, cleaning finished, robot returned to base, robot error, consumable worn out
actions: start, pause, stop, return to base, locate (the robot says « I am here »)
Example: a notification when the robot is stuck, or a cleaning launch when the alarm switches to away mode.
Ecovacs Robot widget: battery, status, error, consumables, and Start / Pause / Stop / Base / Locate buttons.
Testers wanted
I don’t have an Ecovacs robot: the code follows the Ecovacs Home app protocol, already used by Home Assistant and ioBroker, but it hasn’t run on a real robot yet.
@mutmut, the GOAT mower part is for you: all feedback is welcome.
If you have a Deebot, your feedback is also welcome.
Please indicate the model of your robot and what works or doesn’t. For a bug, the best is to open an issue on GitHub or to reply in this topic, with the integration logs.
Isn’t there anything in the SDK that can automatically predict this?
Here are the logs for you:
[2026-10-11T09:50:19.753Z] [INFO] onConfigUpdated -> new configuration received
[2026-10-11T09:50:19.919Z] [ERROR] Ecovacs connection failed for ***@gmail.com: Ecovacs login refused (1013): Please update to the latest version to continue.
[2026-10-11T09:50:24.332Z] [ERROR] Ecovacs connection failed for ***@gmail.com: Ecovacs login refused (1013): Please update to the latest version to continue.
[2026-10-11T09:52:20.809Z] [INFO] onConfigUpdated -> new configuration received
[2026-10-11T09:52:20.950Z] [ERROR] Ecovacs connection failed for ***@gmail.com: Ecovacs login refused (1010): Incorrect account or password
[2026-10-11T09:52:22.826Z] [ERROR] Ecovacs connection failed for ***@gmail.com: Ecovacs login refused (1010): Incorrect account or password
[2026-10-11T09:52:52.451Z] [INFO] onConfigUpdated -> new configuration received
[2026-10-11T09:52:52.620Z] [ERROR] Ecovacs connection failed for ***@gmail.com: Ecovacs login refused (1013): Please update to the latest version to continue.
[2026-10-11T09:52:55.668Z] [ERROR] Ecovacs connection failed for ***@gmail.com: Ecovacs login refused (1013): Please update to the latest version to continue
Thanks @mutmut for the feedback and logs, very helpful!
Error 1013 (« Please update to the latest version ») : this isn’t an issue on your end. Ecovacs changed its connection this summer: it refuses old app versions and now requires confirming each new device with a code received by email (Home Assistant had the same issue).
Version 1.3.0 fixes this. After the update, in the Configuration tab:
« Test the connection » : if Ecovacs requests verification, the message says so.
Click on « Send the verification code » : Ecovacs sends a code to the account email (check spam too).
Enter this code in « Confirm the device » and validate: the robots appear, you just need to add them from the Discovery tab.
Red message : well spotted, it’s done. A « Test the connection » failure now displays as an error. Small SDK limitation: an error is just text, not a translated message, so the message appears in English and French.
Error 1010 (« Incorrect account or password ») : this one comes from Ecovacs which refuses the email or password. Check:
the country chosen in the config (the one used when creating the account);
if your account was created with Google, Apple, or Facebook: you first need to set a password in the Ecovacs Home app.
One last thing: for some Home Assistant users, Ecovacs requests verification again at the next connection. If the code is requested often, let me know, with your GOAT model and the logs.