Ecovacs Integration can't login

[michael15831]

The problem

Since this morning my Ecovacs integration can't login any longer
In protocol I found this message:
Logger: deebot_client.authentication
Quelle: runner.py:289
Erstmals aufgetreten: 14:07:15 (12 Vorkommnisse)
Zuletzt protokolliert: 14:17:44

call to https://gl-de-api.ecovacs.com/v1/private/de/EN/SWRMV6WV/global_e/1.6.3/google_play/1/user/login failed with {'code': '1013', 'msg': 'Please update to the latest version to continue.', 'time': 1784376570745, 'data': None, 'success': False}
call to https://gl-de-api.ecovacs.com/v1/private/de/EN/IJZBINHT/global_e/1.6.3/google_play/1/user/login failed with {'code': '1013', 'msg': 'Please update to the latest version to continue.', 'time': 1784376651292, 'data': None, 'success': False}
call to https://gl-de-api.ecovacs.com/v1/private/de/EN/CTCLTRBR/global_e/1.6.3/google_play/1/user/login failed with {'code': '1013', 'msg': 'Please update to the latest version to continue.', 'time': 1784376811675, 'data': None, 'success': False}
call to https://gl-de-api.ecovacs.com/v1/private/de/EN/YXYWN71S/global_e/1.6.3/google_play/1/user/login failed with {'code': '1013', 'msg': 'Please update to the latest version to continue.', 'time': 1784377058533, 'data': None, 'success': False}
call to https://gl-de-api.ecovacs.com/v1/private/de/EN/C5LQ9XY0/global_e/1.6.3/google_play/1/user/login failed with {'code': '1013', 'msg': 'Please update to the latest version to continue.', 'time': 1784377064088, 'data': None, 'success': False}

What version of Home Assistant Core has the issue?

core-2026.7.2

What was the last working version of Home Assistant Core?

core-2026.7.2

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Ecovacs

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

No response

[freeman59]

I have the same here ... cannot login anymore

[hunters-112]

I am experiencing the exact same issue today. My integration dropped after a power outage and I cannot log back in. I am also getting the code 1013.

Here is my Traceback:

'''
Logger: homeassistant.components.ecovacs.config_flow
Source: components/ecovacs/config_flow.py:85
Integration: Ecovacs (dokumentacja, Problemy)
Pierwsze zdarzenie: 11:26:05 (9 wystąpień)
Ostatnio zalogowany: 17:14:04

Unexpected exception during login
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/ecovacs/config_flow.py", line 85, in _validate_input
await authenticator.authenticate()
File "/usr/local/lib/python3.14/site-packages/deebot_client/authentication.py", line 374, in authenticate
self._credentials = await self._auth_client.login()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.14/site-packages/deebot_client/authentication.py", line 115, in login
login_password_resp = await self.__call_login_api(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
self._account_id, self._password_hash
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/usr/local/lib/python3.14/site-packages/deebot_client/authentication.py", line 186, in __call_login_api
return await self.__do_auth_response(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
url, self.__sign(params, self._meta, _CLIENT_KEY, _CLIENT_SECRET)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/usr/local/lib/python3.14/site-packages/deebot_client/authentication.py", line 165, in __do_auth_response
raise AuthenticationError(msg)
deebot_client.exceptions.AuthenticationError: failure code 1013 (Please update to the latest version to continue.) for call https://gl-pl-api.ecovacs.com/v1/private/pl/EN/AGGBZACQ/global_e/1.6.3/google_play/1/user/login
'''

[die-dimitry]

Experiencing the exact same issue on HA OS 2026.7.2 (Deebot N30). The built-in integration is throwing the 1013 API error. I also tried falling back to the DeebotUniverse custom component via HACS, but it's completely incompatible with this version of HA and just throws a 500 Internal Server Error during setup. We are completely locked out until the core integration gets a patch for the new Ecovacs API requirements.

[superzu]

I have the same errore ... cannot login

[Tjerk1973]

Same problem here, stopt suddenly working.
Cant connect with username and password in Home Assistant in the Ecovacs plugging. Before it works great

[Bohemski]

I have the same problem 😢😢🫩 for ecovacs n8 pro +

[ngolf]

Same issue here:

--- error logs ---

Logger: deebot_client.authentication
Source: components/ecovacs/config_flow.py:85
First occurred: 17:33:47 (4 occurrences)
Last logged: 17:34:07

call to https://gl-uk-api.ecovacs.com/v1/private/uk/EN/HREGFPQY/global_e/1.6.3/google_play/1/user/login failed with {'code': '1013', 'msg': 'Please update to the latest version to continue.', 'time': 1784651627431, 'data': None, 'success': False}
call to https://gl-uk-api.ecovacs.com/v1/private/uk/EN/AVAT7OB1/global_e/1.6.3/google_play/1/user/login failed with {'code': '1013', 'msg': 'Please update to the latest version to continue.', 'time': 1784651641687, 'data': None, 'success': False}
call to https://gl-uk-api.ecovacs.com/v1/private/uk/EN/Y7VBLQYM/global_e/1.6.3/google_play/1/user/login failed with {'code': '1013', 'msg': 'Please update to the latest version to continue.', 'time': 1784651643319, 'data': None, 'success': False}
call to https://gl-us-api.ecovacs.com/v1/private/us/EN/R54BI5KM/global_e/1.6.3/google_play/1/user/login failed with {'code': '1013', 'msg': 'Please update to the latest version to continue.', 'time': 1784651647144, 'data': None, 'success': False}

--- after removing and trying to re-add hub ---

Logger: homeassistant.components.ecovacs.config_flow
Source: components/ecovacs/config_flow.py:85
Integration: Ecovacs (documentation, issues)
First occurred: 17:33:47 (4 occurrences)
Last logged: 17:34:07

Unexpected exception during login
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/ecovacs/config_flow.py", line 85, in _validate_input
await authenticator.authenticate()
File "/usr/local/lib/python3.14/site-packages/deebot_client/authentication.py", line 374, in authenticate
self._credentials = await self._auth_client.login()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.14/site-packages/deebot_client/authentication.py", line 115, in login
login_password_resp = await self.__call_login_api(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
self._account_id, self._password_hash
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/usr/local/lib/python3.14/site-packages/deebot_client/authentication.py", line 186, in __call_login_api
return await self.__do_auth_response(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
url, self.__sign(params, self._meta, _CLIENT_KEY, _CLIENT_SECRET)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/usr/local/lib/python3.14/site-packages/deebot_client/authentication.py", line 165, in __do_auth_response
raise AuthenticationError(msg)
deebot_client.exceptions.AuthenticationError: failure code 1013 (Please update to the latest version to continue.) for call https://gl-uk-api.ecovacs.com/v1/private/uk/EN/HREGFPQY/global_e/1.6.3/google_play/1/user/login

[maxiauer95]

Same problem, pretty sure itis because of a new 2FA in ecovacs environment

[die-dimitry]

I was able to get my integration back online by following the discoveries made in issue #176484 regarding the new email device verification.

The Root Cause: The 1013 error happens because Ecovacs now requires devices to be verified via email. The core HA integration generates a random 8-character deviceId every time it sets up. Because it's a random ID every time, Ecovacs sees it as a brand-new, unverified device and rejects the login.

The Fix: You need to verify a static deviceId once via a script, and then patch your local Home Assistant integration to always use that specific ID.

Step 1: Verify a static Device ID out-of-band

Download this Python script provided by the community: https://gist.github.com/christensenjames/eced2d22de70880a90b2c5edf1b51e97
Set your environment variables for your account and choose a fixed 8-character ID:
bash

export ECOVACS_EMAIL="your_email@domain.com"
export ECOVACS_DEVICE_ID="MYHA1234" # Choose any fixed 8-character string
export ECOVACS_COUNTRY="US" # Use your 2-letter country code
Run python script.py key to fetch the public key.
Run python script.py send to trigger the verification email.
Check your email for the 4-digit or 6-digit code, then run python script.py verify to verify your static ID.
Step 2: Patch Home Assistant as a Custom Component Instead of modifying core files directly, the safest way is to override the integration:

Copy the ecovacs folder from the Home Assistant core repository into your config/custom_components/ directory.
Add a version tag (e.g., "version": "1.0.0") to your new custom_components/ecovacs/manifest.json.
Open custom_components/ecovacs/util.py and find the get_client_device_id function.
Hardcode it to return the exact ID you verified in Step 1:
python

def get_client_device_id(hass: HomeAssistant, self_hosted: bool) -> str:
"""Get client device id."""
if self_hosted:
return f"HA-{slugify(hass.config.location_name)}"
# Bypass random generation and use our verified ID
return "MYHA1234"
Step 3: Reload Restart Home Assistant, and add the Ecovacs integration back through the UI. It will now use your verified device ID and instantly log in without the 1013 error!

[nineseven978]

I was able to get my integration back online by following the discoveries made in issue #176484 regarding the new email device verification.

The Root Cause: The 1013 error happens because Ecovacs now requires devices to be verified via email. The core HA integration generates a random 8-character deviceId every time it sets up. Because it's a random ID every time, Ecovacs sees it as a brand-new, unverified device and rejects the login.

The Fix: You need to verify a static deviceId once via a script, and then patch your local Home Assistant integration to always use that specific ID.

Step 1: Verify a static Device ID out-of-band

Download this Python script provided by the community: https://gist.github.com/christensenjames/eced2d22de70880a90b2c5edf1b51e97 Set your environment variables for your account and choose a fixed 8-character ID: bash

export ECOVACS_EMAIL="your_email@domain.com" export ECOVACS_DEVICE_ID="MYHA1234" # Choose any fixed 8-character string export ECOVACS_COUNTRY="US" # Use your 2-letter country code Run python script.py key to fetch the public key. Run python script.py send to trigger the verification email. Check your email for the 4-digit or 6-digit code, then run python script.py verify to verify your static ID. Step 2: Patch Home Assistant as a Custom Component Instead of modifying core files directly, the safest way is to override the integration:
Copy the ecovacs folder from the Home Assistant core repository into your config/custom_components/ directory. Add a version tag (e.g., "version": "1.0.0") to your new custom_components/ecovacs/manifest.json. Open custom_components/ecovacs/util.py and find the get_client_device_id function. Hardcode it to return the exact ID you verified in Step 1: python def get_client_device_id(hass: HomeAssistant, self_hosted: bool) -> str: """Get client device id.""" if self_hosted: return f"HA-{slugify(hass.config.location_name)}" # Bypass random generation and use our verified ID return "MYHA1234" Step 3: Reload Restart Home Assistant, and add the Ecovacs integration back through the UI. It will now use your verified device ID and instantly log in without the 1013 error!

Works like a charm 👍 If it is only this issue, it should be solved "easliy" inside of the code, if only the fixed id is the problem