authentication Error with my ecovacs integration after update

[juergenweidinger]

The problem

Hey there!
I have an authentication Error with my ecovacs integration after updated my HA-Core. Im already installed the latest version of integration, and it worked until update.

Core
2026.7.4
Supervisor
2026.07.3
Operating System
18.1

URL

https://www.home-assistant.io/integrations/ecovacs/

Version

2026.7.4

What version of Home Assistant Core has the issue?

2026.7.4

What was the last working version of Home Assistant Core?

2026.7.2

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Ecovacs integration

Link to integration documentation on our website

No response

Diagnostics information

Logger: deebot_client.authentication
Quelle: runner.py:289
Erstmals aufgetreten: 17:35:36 (12 Vorkommnisse)
Zuletzt protokolliert: 17:42:40

call to https://gl-at-api.ecovacs.com/v1/private/at/EN/J0RA342H/global_e/1.6.3/google_play/1/user/login failed with {'code': '1013', 'msg': 'Please update to the latest version to continue.', 'time': 1785253208278, 'data': None, 'success': False}
call to https://gl-at-api.ecovacs.com/v1/private/at/EN/POIZXG3M/global_e/1.6.3/google_play/1/user/login failed with {'code': '1013', 'msg': 'Please update to the latest version to continue.', 'time': 1785253218869, 'data': None, 'success': False}
call to https://gl-at-api.ecovacs.com/v1/private/at/EN/W8EENUOH/global_e/1.6.3/google_play/1/user/login failed with {'code': '1013', 'msg': 'Please update to the latest version to continue.', 'time': 1785253239261, 'data': None, 'success': False}
call to https://gl-at-api.ecovacs.com/v1/private/at/EN/F79S9UU6/global_e/1.6.3/google_play/1/user/login failed with {'code': '1013', 'msg': 'Please update to the latest version to continue.', 'time': 1785253279587, 'data': None, 'success': False}
call to https://gl-at-api.ecovacs.com/v1/private/at/EN/R9OX7H5U/global_e/1.6.3/google_play/1/user/login failed with {'code': '1013', 'msg': 'Please update to the latest version to continue.', 'time': 1785253360078, 'data': None, 'success': False}

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

No response

[home-assistant]

Hey there @mib1185, @edenhaus, @Augar, mind taking a look at this issue as it has been labeled with an integration (ecovacs) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of ecovacs can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign ecovacs Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component, problem in config, problem in device, feature-request) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component, problem in config, problem in device, feature-request) on the issue.

_{^{(message by CodeOwnersMention)}}

---

@juergenweidinger Thanks for reporting this issue!

Before we dive in, please make sure this isn't a duplicate by searching through existing issues. Also check recently closed issues, as your problem might already be fixed but not yet released.

https://github.com/home-assistant/core/issues?q=%20label%3A%22integration%3A%20ecovacs%22%20
_{^{(message by IssueContext)}}

---

ecovacs documentation
ecovacs source
_{^{(message by IssueLinks)}}

[dedmen]

Duplicates #176484