Home Assistant Ecovacs integration stopped working: login fails with code 1013

Second half of this that is worth knowing before you count it as solved: a smaller group is still reporting that on 2026.8.0 the verification succeeds, the entry is created, and then it immediately asks to verify again. Delete and re-add lands in the same loop.

So if you update and the login works, you are done. If you update and get stuck on repeating verification, that is a separate open problem and not something you misconfigured.

Resolution, since this one has a clean answer: the fix went into the 2026.8.0 beta and shipped in stable 2026.8.0. Update the core and set the integration up again.

While it was unfixed there was a community custom component doing the new login flow. It worked for a lot of people and it is now unnecessary. If you installed it, take it out before you update, because a custom component with the same domain shadows the built in one and you will be running the old workaround on a fixed core without realising.

The message is not about your version of anything. It is the vendor's login endpoint refusing the client it thinks is calling it.

Ecovacs changed how authentication works on their side. The integration was still logging in the old way, so the API answered with 1013 and a string aimed at phone app users. Nothing on your system is out of date in the way the text implies, and updating the phone app cannot help, because the phone app is already speaking the new protocol.

That is also why removing and re-adding fails: re-adding runs the same login.

One practical thing while you are in there: log out of the manufacturer app on every other device that shares the account before you set the integration up again. Some of these clouds allow one active session per account and they will quietly evict each other, which looks exactly like an authentication bug.

The vacuum was working the whole time. Only the part that tells you it is working stopped.